https://egorfine.com/en/ me@egorfine.com @egorfine on twitter and the rest.
- It's time for a new, leaner init system. systemd became an os of it's own.
- musl support is excellent. If you were unhappy with transparency, simplicity, maintainability and thinness of Alpine Linux - now you can install systemd and loose all of these disadvantages.
- Until you need to actually dive deep into complicated scenarios. In sysv init you were on your own, which could be for better or for worse. In the world of systemd you either do as LP says or you do not at all.
I vastly prefer #1.
- Yeah, I managed a major service back in the day and I can confirm all you say is absolutely correct (except maybe #3, but that's legal).
One thing I do not understand however is why wouldn't companies offer paid appeal process perhaps with refund in case the termination decision is indeed overturned. I would gladly pay $100 to have my Apple/Google/etc account properly reviewed in order to get it back once it is inevitably flagged by yet another AI. Seems like win-win all around.
- Another walled garden is what we needed, right.
- Who could've thought, really
- They're between a rock and a hard place. Introduce AI and alienate whatever users you have left. Do not introduce AI and alienate whatever investors you have left.
- They can alienate whatever users left by introducing AI or they can alienate whatever investors left by not introducing AI. Sucks to be Mozilla.
- Problem is, varlink has been created to alleviate the pain while what I'm looking for here is even more suffering. Perhaps add AI and MCP into the mix. At kernel level with hard dependency on sudo-rs. And local RPC should be blockchain-based.
- I believe someone from systemd should reimplement d-bus in rust. This way we can have all the things we hate in a single instance.
- Could you imagine a project that is simultaneously:
1. having such a huge local SQLite file that migration to another format is unfeasible;
2. bottlenecking on a single specific metric that happens to be more performant in Turso;
3. ready to introduce another programming language and its build toolchain into the project;
- > it does feel like an overstep on their part.
It's the Rust superiority complex that's subtly speaking thru the Rust "rewrite" projects. Of course rust is better so why would anyone want to stay on the old, C-coded version?
- Note: Budapest memorandum is:
1. Not binding; 2. Non-actionable; 3. Never broken by the western countries.
Budapest memorandum is tiny and clear. Go read it and decide for yourself whether US has broken it or not.
- NATO Art. 5 guarantees are binding for all NATO members, out of which there are multiple that would be willing to engage.
While the proposed replacement, art.5-style guarantees backed by the US alone, is guaranteed to fail, because there is nothing in the whole world that can enforce and bind US to actually act on the signed document. Current administration can just basically say "fuck you lol" once russia attacks again and that would be it.
- systemd sort of did this to certain parts and it's the worst thing that happened to Linux. Standardizing on Rust political rewrites of tar and libmagic is going to be an epic disaster and a decade of never-ending fun for Rust evangelicals.
- > they’ll roll it back.
They will absolutely not roll it back, not matter how broken they are.
The reasons to switch from coreutils to the Rust rewrite are purely political.
- The point is virtue signaling. There is no technical merit to it.
- Correct. It's almost not at all about memory safety.
- Because the reasons to replace coreutils with the Rust rewrite are not technological, they are political. And thus aiming to rewrite something very core and stable is the correct approach to enrage the opposite party.
Don't you personally feel disgust mentioning AI stuff?
Yeah, I realize it is mandatory to mention AI today in every piece of communication of any company; but on a personal level, isn't that something that requires a bit of dying every time?