• 1 Post
  • 10 Comments
Joined 2 years ago
cake
Cake day: July 21st, 2023

help-circle
  • The problem with Linux is that most distributions suck for beginners. People recommend Debian/Ubuntu because they’re stable but that just means they don’t get updated, not that they won’t break. The obvious solution is to use Arch, which has the latest version of software and therefore does not break on new hardware. But that sucks too because Arch’s goal is not that your setup works either, it’s that you have the latest versions of software installed no matter the cost. OK, so I guess Fedora will be good because it’s somewhere in the middle. Fedora is better but their non-free codec stuff is not great for noobs either.

    I think the best recommendation is Pop! OS because it has none of the above issues. You will still have outdated software but at least not outdated drivers. Just use the defaults, don’t change the desktop environment etc. If you install third party software in the .deb format, expect breakage when you eventually upgrade to a new release. Try to use flathub for that. Be aware that software on Flathub is user-submitted and may contain a virus. Check that it’s verified by a trusted source, not just some random person’s github website.

    Then there is OpenSUSE Tumbleweed which I guess is pretty good too but it’s hard to recommend to noobs because it’s sort of esoteric and because you cannot install .deb packages from the internet on it. Finally there are the atomic distros which have the same issues but at least they should break less likely. If you only need software from flathub and what’s available in the app store, they’re fine.

    idk why I wrote this but yes most distros don’t “just work”


  • Thanks for the links! I think their wording on why they don’t want to open source the project is quite slimy when it just requires them to give ship users the source code tarballs alongside the binaries.

    You shouldn’t need to cross compile, as they will provide the binaries for systems they support.

    Well it’s unlikely a company would support every possible system in the world. The best one can do is using something like static linking/flatpak/nix. But that means not using shared libraries which can make software start slower. This would bother me for a daily-driver browser. I guess it does not bother nix users like you but I was thinking they would be potentially missing out on some Linux users. Maybe it isn’t really a significant portion that would care.

    I felt ok with spending $10

    I guess I would be too but in the context of their offerings, it’s kinda off-putting for me.


  • The browser isnt paid though.

    So it’s a closed source browser that relies on donations? Or is it Open Source? I could not find much about it (eg. a git repo or something) and just assumed it would have a similar business model to the search engine.

    why would it have issues with a package manager?

    Depends on the package manager. It’s probably easy on Debian, but more difficult on rolling releases, mostly because of dependency hell. Binary distributed software is also harder to integrate in a build system and cross-compilation to a different architecture is not possible.

    Regarding the cost of the search engine, I don’t care about all the things you get. I just want a search engine and for a reasonable price compared to the price of their “all of them at once, I suppose” bundle.


  • Paid search engine makes sense to me but paid browser does not. The browser’s target audience will have a better experience using a free of charge and Open Source browser than a paid one because the paid browser won’t integrate very well with package managers.

    This is off topic but their search engine pricing is quite scummy. Either you pay $5 for 300 searches per month, which is too little, or you pay $10 for unlimited searches, which is too many for a mere mortal. They are trying to up-sell the $10 subscription.



  • from Arch Wiki FAQ:

    Is Arch Linux a stable distribution? Will I get frequent breakage?

    It is the user who is ultimately responsible for the stability of their own rolling release system. The user decides when to upgrade, and merges necessary changes when required. If the user reaches out to the community, help is often provided in a timely manner. The difference between Arch and other distributions in this regard is that Arch is truly a ‘do-it-yourself’ distribution; complaints of breakage are misguided and unproductive, since upstream changes are not the responsibility of Arch devs.

    It does not explicitly say “maintain” but it has a similar vibe to it.


  • The title is bs. There is no “push by Canonical”. A random person on the internet wrote Uutils in Rust because it’s easy to write fast code in it. Then Canonical wants to package the software but they aren’t “pushing”, they are just packaging software someone else wrote. Canonical’s goal is memory safety but that’s not the author’s goal because Coreutils haven’t got many vulnerabilities anyways.

    The licensing part is sort of sad. The author picked MIT, because he does not care. He also said that he does not want drama. Well he did get the drama. The sad part is that I think that he would be willing to change the license to GPL, had it not been for all the childish drama and “hate”. Communication is difficult for people online, unfortunately.