Classful IPv4 was obsoleted 32 years ago. Only 8 years left before it’s literally older than a standard career.

It’s fascinating the sheer inertia that leads formally-trained IT professionals to use and perpetuate such profoundly useless and obsolete nomenclature. You’d think that having an incorrect use of the term “class A” and not having any use for classes B and C would tip off academia that they should cordon off classful networking to the “History of Computing” course next to ARPANET.

Maybe next time someone refers to 10.0.0.0/8 as a Class A network I’ll refer to it as the ARPANET Network. That’s only very slightly more anachronistic (3 years).

Last time around Asahi Lina (major contributor to the Apple Silicon GPU driver) made a very nice writeup on mastodon about her attempts to mainline her work.

Part of the problem was that the C interface was straight-up broken; not only were a bunch of lifetimes undocumented, but freeing the kernel objects properly was impossible, but GCC doesn’t care and neither did anyone because GPU drivers are expected to just… never exit (IIRC). So she refactored it to be saner.

Anyway apparently it was rejected for much the same reasons, aka Rust bashing thinly disguised as concerns over maintainability.

Technically the R4L project did have an impact. But what’s the worst case? Spending some time on improving the C interface for an edge case? The ignominy! NAK.

Don’t force me to deal with your shiny language of the day,

WE HavE LegItImaTe COnCeRNs

Exact same shit as last time, some cranky old dude with the territorial instinct of a bulldog sabotages anything to do with rust under a very thin layer of so-called technical concerns, yet refuses to partake in constructive discussion. Like, literally, the changeset is just bindings in rust/kernel? What even is there to complain about regarding maintainability of kernel/dma, given that as far as I can tell the rust devs will deal with any future incompatibilities?

Very shameful for the kernel community that this kind of aggressive sabotage is regular and seemingly accepted. The incessant toxicity is not a good look and very discouraging to anyone thinking of contributing.

Hell, pass init=/bin/yes and you’ll see even more greatly reduced RAM usage!

❯ ps aux | grep /usr/lib/sys | awk '{print $6}' | sed 's/$/+/' | tr -d '\n' | sed 's/+$/\n/' | bc
266516

So that’s 260 MiB of RSS (assuming no shared libs which is certainly false) for:

• Daemon manager
• Syslog daemon
• DNS daemon (which I need and would have to replace with dnsmasq if it did not exist)
• udev daemon
• network daemon
• login daemon
• VM daemon (ever hear of the principle of least privilege?)
• user daemon manager (I STG anyone who writes a user daemon by doing nohup & needs to be fired into the sun. pkill is not the tool I should have to use to manage my user’s daemons)

For comparison the web page I’m writing this on uses 117 MiB, about half. I’ll very gladly make the tradeoff of two sh.itjust.works tabs for one systemd suite. Or did you send that comment using curl because web browsers are bloated?

For another comparison 200 MiB of RAM is less than two dollars at current prices. I don’t value my time so low that I’ll avoid spending two bucks by spend hours debugging whatever bash scripting spaghetti hell other init systems cling onto to avoid “bloat”. I’ve done it, don’t miss it.

What even are GCC’s advantages in 2024, besides “we painted ourselves in a corner with proprietary extensions” (e.g. Linux)? That aside I personally only see upsides to clang, but I don’t routinely do C work and maybe I’m missing something.

Removed by mod

Source?

In the EU at least this is demonstrably false. LNG has slightly risen since 2000 but other fossil fuels (namely coal) have gone way down. Total consumption has been steadily declining in the past few years and is down to 2004 levels. So overall our electricity is a whole shitload cleaner.

The story is even starker for domestic heating. Gas and coal are vanishing since the mid-2000s.

Kids finish school around 3 pm where I live. They have time to do their extracurricular activities (partially) during daytime even in the dead of winter. So of course it’s the mornings they find dreadful. If school finished around 5-6 pm I think they’d be miserable then as well.

Speaking of which, I’m about to end my work day and the sun is setting right now. FML.

Yes it would. I, like most 21st century humans, wake up for work and have free time after work.

In practice for my relatively northern latitude this means I get a little bit of daylight before work (except perhaps around december/january), but winter time is very specifically designed so that today the sun will set exactly 6 minutes before I end my work day.

Were we to keep permanent DST I would get an hour of free time in the daylight today, and at least a little bit of light outside for all winter except perhaps for a month around December. As it stands, I do not get any free time in sunlight for 5 days a week for the entire duration of ST. The switch to ST means “bye-bye sun” and I hate it, I hate it, I hate it, I FUCKING HATE IT.

The 24 hour clock is a made up construct. So are business hours. But if we already agreed to change one of these twice a year, can we make it so that it is not optimized to trap me inside for the entire duration of daytime???

The studios! Think of the studios! Their execs couldn’t live off merch sales and shitty reboots anymore! They might even have to - gasp - develop original IP if they want to milk an exclusive license. Some other execs would make money off some of last century’s licenses! The horror! The tragedy!

That can’t be. Clearly the best thing about Indiana Jones and Jurrasic Park is the death grip the studios have on those IPs. Ever since Steamboat Willie fell into the public domain I’ve been unable to enjoy the Disney Classics. All joy has been snuffed out from my life.

Wait until you learn about debhelper.

If you use a debian-based system, unless you have actively looked at the DH source, the one thing that built virtually every package on your system, you do not get to say anything about “bloat” or “KISS”.

DH is a monstrous pile of perl scripts, only partially documented, with a core design that revolves around a spaghetti of complex defaults, unique syntax, and enough surprising side effects and crazy heuristics to spook even the most grizzled greybeards. The number of times I’ve had to look at the DH perl source to understand a (badly/un)documented behavior while packaging something is not insignificant.

But when we replaced a bazillion bash scripts with a (admittedly opinionated but also stable and well documented) daemon suddenly the greybeards acted like Debian was going to collapse under the weight of its own complexity.

I wonder how many terrorist (and “terrorist”) plots that were foiled were from compromised telegram messages. How many Ukrainian airstrikes were called from similar sources. My gut says a whole lot more than people think. Since nothing is encrypted, one backdoor is all the NSA needs to read everyone’s group messages. Like the much lamer version of Crypto AG, because in this case it’s an open secret.

It’s not about the bindings. It’s, as always with kernel devs, about gatekeeping and unprofessional if not outwardly hostile behavior.

Maintaining bindings is a hard problem for sure, but no hard problems have ever been solved by the key stakeholders refusing to partake in honest discussions. Asahi Lina’s breakdown of her rejected contributions to the fundamentally flawed drm_sched, which do not involve a single byte of Rust, demonstrates an unwillingness to collaborate that goes much further than the sealioning about muh bindings.

ls -l /proc/xxx/{fd,syscall}

Camera pans down to resource locks hiding under the floorboards

The main display that shows your speed,etc. randomly shutting down

I know two people who had this exact issue with their new-gen Golf. First cause was the French language would crash the whole dash if you cycled the dashboard views (to my knowledge they never fixed the issue and the workaround is to set the car to English). Second cause was a malformed JPEG from a radio station would cause the dash to bootloop until you drove far enough from said radio station, which would allow the car to work long enough to disable that feature (IIRC).

So yeah, QA is down the fucking drain with VW on their latest gen. They had a new CEO, and now a new one again I think? But the reputational damage has been done. Too bad, I really liked my '18 Polo.

I wouldn’t recommend sway to someone who isn’t actively looking for a tiling WM, I would recommend finding a good spotlight equivalent to use on KDE as that will still be less customization work than it would require on barebones sway (which is hardly usable).

It’s not as bad nowadays that apps yielded to GNOME’s bullshit. Back when GTK2 apps were still common… Urgh. Plenty of apps were broken without it for no good reason.

I like opinionated UX - I use sway - but GNOME’s approach is incompatible with “general use” and only works (for now) because of canonical’s weight and ability to impose their vision as the only vision.

Also they didn’t replace the tray with a better way to manage background apps, so they can suck a dick on the UX front.

The fucking system tray. Which literally every other DE and mainstream OS out there supports because some apps depend on it and break if it doesn’t exist.

Last I checked GNOME devs said “no, we will never support it, because we’ve DePRecATeD the tray in GTK”.

It’s functionality so basic I have 3-6 apps which depend on it at any time on my work machine. Anyone saying it doesn’t fall under “basic functionality” is either a GNOME dev or a troll.

I would be very surprised if it wasn’t voluntary, as far as I know each Wiki is maintained independently with very little oversight.

I remember when “new” Wikipedia came out with big press I was confused because it had already been in use on the French wiki for months.

My guess is as the biggest wiki, the English wiki is naturally more conservative on the rollout of new features.