Readit NewsI'll offer a less charitable framing of the whole topic of immutable / atomic distros: This is pretty much Linux distributors deciding they want to stop doing their job (or redefine what their job is to a much smaller scope). -- I'm not saying it's not justifiable that the ecosystem may need to be reshaped in that way. I'm just cautioning people from drinking the “this is the future and the future looks bright” Kool-Aid all too easily.
The job of making a Linux distribution has always been what, in an old-fashioned term, used to be called “system integration” work. They would start with a bewilderingly huge array of open-source packages, each being developed without any centralized standard or centralized control over what the system actually looks like. Then they would curate a collection of build recipes and patches for those packages.
The value a distro delivers for the user is that, for any package “foo” that their heart desires, a user can just say “apt install foo” and it'll “just work”. There will be default configuration and patches to make foo integrate perfectly with the rest of the system.
The value a distro delivers for package maintainers is: “Don't worry about the packaging. Just put your code out as open source, and we'll take care of the rest.”
The job of a distributor is extremely difficult, because of all the moving parts: People select their hardware, their packages, and they mess with the default configurations. It is no wonder at all that Linux distributions don't always succeed in their mission to truly deliver on this. But it's a huge engineering achievement that they work as well as they do, and I think we shouldn't lightly give up on that achievement.
What we have now is basically distros going: Awwwww. Fuck it. This is too hard. I'm done with this. You know what? Instead of “any package your heart desires”, you get a fixed set of packages. The ones that everyone needs regardless of what they actually do with their computer. Instead of being allowed to mess with your configuration, we'll make your rootfs read-only. (In the case of SteamOS): Instead of doing our best to make it work on your hardware, we'll tell you precisely which piece of hardware you'll need to buy if you want our software to run on it. User: Well, that's additional money I need to spend. And, how do I install my favourite app “foo”? The one I need to actually get useful work out of my computer? Distro: Don't worry, we've got you covered. We'll provide a runtime for distrobox and flatpaks. Package maintainer of “foo”: How do I get my package out in a way that perfectly integrates with distros? Distro: Make a container. Congratulations: This is additional work you have to do now, that you didn't have to do before. And about that idea of perfect integration: You can kiss that goodbye. User: I don't know. I'm also in favour of integration. Distro: That's alright. You can share and unshare stuff between containers and the host system. This, of course, is additional work you didn't have to do before. Less work for me, more work for everyone else. The future looks so bright.
Well, I've been using NixOS for a while now, and it's by far the most "integrated" feeling distro I've ever tried.
Unless the take was "china invented the virus" (which is trivially and googleably false) I don't see how anyone in the west would care given that the we engage in the same (edit: actually, much more reckless and misanthropic) behavior. Unless it's just racism, of course. But then again nobody has ever accused the west of avoiding hypocrisy.
Just pity the terrified-but-patriotic simpletons who buy this shit, mock the evil assholes who start this shit credibility, and move on with your life without nightmares of a boogieman who will drink your blood because... just because, ok!??
I'm not sure what you mean by "invented", but as far as I know the Chinese lab leak theory is still widely accepted as credible and supported by many facts.
hurutparittya commented on Google change is breaking some digital photo frames theverge.com/news/623306/... · Posted by u/tomsonj
Only on TGZ files, not zip, which maxes out at 4GB. (This is not because of a file size limitation. The only way to get 4GB is through zip64, which has a file size limit measured in exabytes.)
Just... get the TGZ then?
hurutparittya commented on Privacy Pass Authentication for Kagi Search blog.kagi.com/kagi-privac... · Posted by u/b3n
> (I don't use Orion, as there's no GNU/Linux version.)
We commenced work on Orion for Linux yesterday.
Any target date for open-sourcing it? :^)
hurutparittya commented on Release Notes for Ghostty 1.1.0 ghostty.org/docs/install/... · Posted by u/ksec
PSA: if you’re on Wayland, Foot starts much faster, uses about 1/4 the memory, and is very fast. Paired it with Niri WM, and <3
Foot would be beyond perfect if it had ligature support.
i tried running a tor relay and all hell broke loose with websites simply refusing to provide service and the such. not good!
Exit node or relay?
hurutparittya commented on An Update on Apple M1/M2 GPU Drivers lwn.net/SubscriberLink/99... · Posted by u/MrBuddyCasino
> there are some issues that should be dealbreakers for tech literate people. (in my own, possibly biased opinion at least)
I know you admit right after that your opinion is biased, but it's almost ludicrous to assert that all the programmers and engineers using Macs and iPhones by choice must just not be tech literate.
> In case of Macbooks, it's the fact that they refuse to provide an official GPU driver for Linux
MBPs are so much better than any other laptop that, with a few caveats[1], running Linux in a VM on a top-of-the-line MBP is a much nicer experience than using Linux natively on any other laptop. So while it'd be nice if there were more first-party support for Linux, it's certainly not a deal-breaker for "tech-literate" people. (Not to mention the fact that there are "tech-literate" people who use macOS and not Linux, so it wouldn't matter to them at all).
> general poor support for things outside the walled garden
macOS isn't a walled garden, so I don't know what you mean. You can download any software you want from anywhere you want and run it on your laptop, and Apple doesn't do anything to try to prevent this.
> The Asahi stuff is cool and all, but come on, is a 3.4 trillion dollar company really going to just stand there and watch some volunteers struggling to provide support for their undocumented hardware without doing anything substantial to help? That sounds straight up insulting to me, especially for such a premium product.
Now it's unclear whether your point is "I don't understand why people use Macs because there are objective drawbacks" or "I don't think people should use Macs because Apple does stuff that I find annoying". You're blending the two here but they are meaningfully separate points. I've discussed the practical point already above, but as for the stuff you subjectively find annoying: surely the only real answer is that lots of other people just subjectively don't care as much as you.
> For iphones, it's the fact that you are not allowed to run your own code on YOUR OWN DEVICE without paying the Apple troll toll and passing the honestly ridiculous Apple Store requirements.
I don't care about this at all. I've never wanted to run my own code on my own iOS device except when I was working on iOS apps and had an Apple developer account through work. I, like the vast majority of people, use my phone as a browsing/messaging/media consumption device, not as a general-purpose computer.
If Apple tried to prevent me from running my own code on my own MacBook, it would be a deal-breaker, but as I already said above, they don't.
In conclusion I think you've confused "tech-literate person" and "geek who wants to be able to tweak/configure everything". Indeed there is a large overlap between those sets, but they're not quite the same thing.
I agree, "tech-literate" was a poor choice of words on my part. Tech enthusiast or tinkerer would have been much better options to convey my opinion.
I feel like there used to be a higher concentration of those people here.
hurutparittya commented on An Update on Apple M1/M2 GPU Drivers lwn.net/SubscriberLink/99... · Posted by u/MrBuddyCasino
One thing I noticed in the M4 macbook announcement comments was how many people were happy with their M1 laptop, and second, how many people kept their Macbooks for nearly a decade; these devices are built to last, and I applaud long-term support from Apple itself and the Linux community.
Second, since it's open source, Apple themselves are probably paying attention; I didn't read the whole thing because it's going over my head, but she discussed missing features in the chip that are being worked around.
I'm always surprised when people speak highly of Apple devices here. While they do have certain advantages, there are some issues that should be dealbreakers for tech literate people. (in my own, possibly biased opinion at least)
In case of Macbooks, it's the fact that they refuse to provide an official GPU driver for Linux and general poor support for things outside the walled garden. The Asahi stuff is cool and all, but come on, is a 3.4 trillion dollar company really going to just stand there and watch some volunteers struggling to provide support for their undocumented hardware without doing anything substantial to help? That sounds straight up insulting to me, especially for such a premium product.
For iphones, it's the fact that you are not allowed to run your own code on YOUR OWN DEVICE without paying the Apple troll toll and passing the honestly ridiculous Apple Store requirements.
And of course, in both cases, they actively sabotage third party repairs of their devices.
It's possible to get unauthenticated streams if you know the media paths. Media collections, at least in my experience, usually adhere to a few common organization schemes. This would allow someone with a list of common titles, which are available in various public databases, to leak data by brute force from a public facing Jellyfin instance quite efficiently.
Discounting this as merely "suboptimal behavior" sounds like a mistake.