• 0 Posts
  • 37 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle
  • Bee-link and GMKtec make some tiny computers purposely designed to be home servers. I thankfully got a ME mini NAS before the LLM apocalypse and it is a beast that can expand up to 24TB. It comes with an Intel N150 that runs all my personal services and consumes almost no power at all. But they also make other smaller models (the ME mini is already minuscule for what it does) that can fit 2 M.2 disks and they all have their own power supply and ethernet connection. The only problem is that the prices have skyrocketed because RAM and solid state storage starvation.

    They are still, somehow, cheaper than Raspberry’s post-price hikes while being more powerful.







  • Yeah, you just said the same the same thing I said with different words.

    Java was also based heavily on Pascal at first.

    A Java Application Servers Report (2010) opens with a brief history of Java that says:

    It all started back in 1991 at Sun Microsystems Corporation, […] Patrick Naugthon, […] proposed a project to his friend and CEO Scott McNealy for the development of a small, simple, portable computer environment that could control all types of electronic components.

    The language must use the principle of a virtual machine […] It must also be based on the current object-oriented language, C++, […] The project went ahead under the name “green” and the language was based on an old model of USCD Pascal, which makes it possible to generate interpretive code.

    The Java development team has white papers dissecting Delphi Object Pascal for the discussion and development of Java features. This one is funny in that it discusses and discards a feature of Microsoft’s J++, on which Hejlsberg worked too.







  • Because the pace of code production has officially overwhelmed the human capacity to review it. As it was discussed recently. Linus answer was to use more AI, with the implementation of code review tools that gobble up code and spew out summaries.

    For the time being, humans reading the summaries count as human reviewed. But at some point in time this system will crack. The current zeitgeist is to restrict who can contribute. Which leads to the obvious follow up question of who decides based on what, and how to decide who deserves to contribute.

    You just witnessed the first steps into the philosophical and political erosion of the open source movement. Not just on the kernel but it is also affecting almost all popular FOSS projects.

    But of course, that doesnt matter because Linux is not and has never been political. /s






  • Split versions is usually the first step. Many projects have done so before. Next year there will be some technical reason they can’t keep feature parity with the commercial repository, and it will drift from the OSS repository. Oops, we broke compatibility, sowwy guys. A couple of years later the OSS repository will be closed because it is a security risk. By that point the company and management would’ve drifted so far from the initial values of the project that people won’t notice. Those who cared will have jumped ship to alternatives sooner, those who noticed later will be already too deep into depending on the software that they will keep paying the subscription.

    I have no evidence, but I also don’t have any doubts this is the plan.


  • It currently doesn’t work with Vaultwarden. The Linux client doesn’t accept custom certificates. And the Android client is paid. It is a dead-end for self-hosting.

    The license is also stupidly a single sentence. Which means that use could be nuked at any minute, and any money you use to pay the developer means nothing. If they wanted to kill the project today and nuke the repo, you have no legal rights, the project dies and fuck you and your passwords. That doesn’t exactly inspires confidence.


  • dustyData@lemmy.worldtoLinux@programming.dev•Bitwarden Switches to Commercial License
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 month ago

    KeyGuard is proprietary on Android. Certain features are locked behind a subscription or one time purchase.

    I’m starting to also hate on this model. People who claim to be open source but still throw hurdles and obstacles at anyone trying to either use or contribute to the project. I understand people need to support themselves financially, but I have donated to many free projects and open projects in my life. Whenever I see a paywall it makes me not want to use the project, however interesting it might be. It sucks they are usually the only almost decent android clients. (Looking at Symphonium and their developer’s shit ass attitude too)

    EDIT: Just tried it and it seems like vaultwarden login and custom certificates on linux have been fried since December. It is currently a dead-end for selfhosters.