qalmakka

I think that's because not everyone does the same job within the same stack and constraints. I'm yet to find an LLM that writes the kind of C++ I dabble with without having to manually tweak it myself (or that truly understands our codebase). Conversely, I find that LLMs are now excellent at python and orchestration tasks for instance. It's very situational

On Linux in a pinch you can use bubblewrap to hide and replace directories for a given process

I am much younger than the author, but I've been coding for most of my life and I find close to no joy in using AIs. For me coding has always been about the nitty-gritty quirkiness of computers, languages, solving issues and writing new cool things for the sake of it. It was always more about the journey than the end goal, and AI basically hollows out all of the interesting bits about coding. It feels like skipping straight to the end of a book, or somewhat like that.

I don't know if I am the only one, but developing with chatbots in my experience turns developing software into something that feels more akin to filling out forms or answering to emails. I grieve for the day we'll lose what was once a passion of mine, but unfortunately that's how the world has always worked. We can only accept that times change, and we should follow them instead of complaining about it.

I for one still like the good old Cantata. It's still maintained by the community after the original dev bailed out, and it has good UX and lots of features. Feishin is also great but it's way heavier on RAM being basically a glorified website and all, so unless you have a reason to have Navidrome up and running it's overkill for most people

> Telecom Italia Sparkle

A corollary to the Hanlon's razor: prefer assuming incompetence over malice if there's Telecom Italia involved in any shape or form

Calling butter or red meat "healthy" is so utterly wrong. Saturated fat is at best neutral, and probably bad for you. Putting it in the same league as extra virgin olive oil is an insult to anyone with intelligence, even lard would be less bad than that

And given that we know that red meat is probably carcinogen it's insane for anyone to recommend its consumption. You should be eating as little of it as possible and focus on fish, beans and poultry. Ironically there are basically no recommendations anywhere to eat more beans.

Is so blatantly clear to me that the USDA and RFK jr got bought by the meat and dairy industry that's not even funny

We're already at the point where in order to have a "decent" desktop software experience you _need_ Rust too. For instance, Rust doesn't support some niche architectures because LLVM doesn't support them (those architectures are now exceedingly rare) and this means no Firefox for instance.

> Embedded - This will always be C. No memory allocation means no Rust benefits. Rust is also too complex for smaller systems to write compilers.

Modern embedded isn't your grandpa's embedded anymore. Modern embedded chips have multiple KiB of ram, some even above 1MiB and have been like that for almost a decade (look at ESP32 for instance). I once worked on embedded projects based on ESP32 that used full C++, with allocators, exceptions, ... using SPI RAM and worked great. There's a fantastic port of ESP-IDF on Rust that Espressif themselves is maintaining nowadays, too.

There's a huge difference between "AI" and "tech bros and finance guys getting amazed by an LLM that talks back to them without realising it's just a language model and not intelligence, so they started chucking the massive piles of cash they had lying around the world to evade taxes to them in a pyramid scheme of colossal scale". We currently are heading more and more towards the latter, and when it crashes it will sow so much distrust and curse the "AI" name so much that we'll probably get a decades-long AI winter after that. In the end none of this nonsense will help the world towards getting better AI any time soon.

Already most "AI researchers" outside of the big corps have basically turned in the last 3 years from "people training their models and doing research" to "webdev plugging into other people's APIs to use LLMs they don't know crap about". When, not if, the big AI bubble bursts, the damage done to the sector will be immense

   struct parent *p = (struct child *)c; // valid

Note that this cast would be valid without the MS extensions too, you can always cast a pointer to a struct to a pointer to its first member and viceversa. What the MS extensions allow you to do is to just do `c->i` directly, without having to name the parent

> UNIX vendors

Well FreeBSD exists, just look at Netflix

Yeah it's all shit and giggles until you need to allocate memory and handle it. Or when you need to use vector instructions or some CPU-specific stuff. Then you start understanding why people call it nightmarish

OT: using the `strcasecmp` family of functions is basically asking for trouble - unless you've previously set the locale to "C", which is basically the only locale with a defined behaviour. Otherwise you're basically bound to run onto very funny internationalisation issues you'd rather know nothing about (and fail the Turkey Test)

yeah especially since it stopped being an actual subsystem in the Windows NT sense of the term with WSL2 - it's a hecking virtual machine that's very convenient to run, but that's like saying that WinBoat is a "Linux subsystem for Windows" - totally ludicrous

Integer operations, the one thing in computers where basically there's no non-annoying way to do them right except being over pedantic with checks

Linux didn't win because it was GPL'd, it won because it was the only real alternative back in '92. The BSDs were all caught up in the moronic SCO lawsuits of the time, otherwise we'd all be using FreeBSD or some other 386BSD variant today instead of Linux. The GPL was a nice bonus but it isn't the real secret sauce that has powered Linux's growth, it was mostly good timing.

That doesn't mean that I'd rather see some form of copyleft in place (like the MPLv2) or at least a licence with some kind of patent protection baked in (like the Apache 2.0), the X11/MIT licences are extremely weak against patent trolls

Exactly - as if evolution cared enough about keeping us healthy after childbearing age. It's hard to state "yeah we've evolved to live like that, of course it's good for us" because clearly keeping us alive after the age of 40 really wasn't _that_ necessary for human survival. There's a lot of perfectly natural stuff that hurts us, including sunlight. Most cancers will only occur in the latter half of our lives, where usually a human historically had already had several children that are now old enough to survive on their own.

Yeah QA is basically nonexistent at Microsoft, at least it hasn't been since the early Windows 10 days. At work we ended up getting rid of all of our Windows runners because we found out that running our tools on WINE got objectively more reliable and deterministic than having to deal with Microsoft's bullcrap

Which is insane if you think about it. 20 year old NICs are still supported by the kernel. Hardware drivers should be GPLd, no ifs and no buts. As if having closed source drivers gave OEMs a competitive advantage, it's basically all for planned obsolescence

Lol. Realistically speaking, you'd have to bind mount your entire home for it to be usable then

Killing ZFS on Linux would basically make Linux unsuitable for lots of usecases. What would you use instead? Btrfs, which keeps having stupid data corruption issues? Bcachefs, which is not yet stable and now it's being struck out of the kernel? LVM2+thin provisioning, which will happily eat your data if your data overlap? I hope some industrial players will force the kernel to drop this nonsense.

Heck no native filesystem besides btrfs has compression, I'm saving HUNDREDS of GB with zstd compression on my machines with basically zero overhead

RIP BCacheFS. I was hopeful I could finally have a modern filesystem in Linux mainlined (I don't trust Btrfs anymore), but I guess I'll keep on having to install ZFS for the foreseeable future I guess.

As I predicted, out of tree bcachefs is basically dead on arrival - everybody interested is already on ZFS, btrfs is still around only because ZFS can't be mainlined basically

The real issue is that C++ does implicit _deep_ copies by default on assignment and that you can't retrofit the language to change that. One quick, fast solution to avoid such shenanigans is to follow the one parameter `explicit` constructor rule religiously and always mark copy constructors explicit unless you know as a fact the type is trivially memcpy-able. This fixes most of the issues.

Another problem with C++ references is that they aren't really reference types, they are aliases, so they have wonky semantics and crazy nonsensical features like `const T&` doing lifetime extension

The problem is not the reference, the problem is implicit copies and the horses left the barn 40 years ago, it's too late to fix that. The only thing we can do right now is deleting or marking copy constructors explicit whenever possible

The fact that implicit copies are a feature doesn't mean they were a good design choice to begin with. In new code I've started making the copy constructor explicit whenever I can, for instance, just to avoid this kind of shenanigans

In my experience Podman is better but always ends up having some wonky bug (like, the other day, secrets didn't mount anymore during builds). Rootless, daemonless is great but it's basically bound to have some extra tinkering required compared to "a stupid daemon running as root"

Thin provisioning with lvm is afaik problematic, because the file systems aren't aware of it and if you run out of space you're screwed

> Btrfs is NOT constantly eating people data

Tell it to my data then. I was 100% invested in Btrfs before 2017, the year where I lost a whole filesystem due to some random metadata corruption. I then started to move all of my storage to ZFS, which has never ever lost me a single byte of data yet despite the fact it's out of tree and stuff. My last Btrfs filesystem died randomly a few days ago (it was a disk in cold storage, once again random metadata corruption, disk is 100% healthy). I do not trust Btrfs in any shape and form nowadays. I also vastly prefer ZFS tooling but that's irrelevant to the argument here. The point is that I've never had nothing but pain from btrfs in more than a decade

The whole situation is moronic at best. Linux needs a decent modern filesystem in tree. ZFS would easily be it, but unfortunately Sun decided back in the '00s to fuck Linux because they wanted to push Solaris instead. Little they knew ZFS ended up being FreeBSD top feature for years.

Btrfs is constantly eating people data, it's a bad joke nowadays. Right now on Linux you're basically forced to constantly deal with out of tree ZFS or accept that thinly provisioned XFS over LVM2 will inevitably cause you to lose data.

Yeah, the problem is that some old web APIs have been clearly hacked up haphazardly in the '90s, probably in a hurry, and now we have to live with the consequences of that. This is not unique with the Web though, it's basically the same with the entirety of the WinAPI and most libc functions in my experience