von_lohengramm

I'm curious what you've found the troublesome subreddits to be. I think I have a pretty strong idea what they are, but some validation would be nice.

> like in Infinity War

Referencing Marvel movies in one's description of proposed military hardware is not only immediately discrediting but also a good sign that self-reflection is in order.

> Every country with conscription will do this if you refuse to show up.

Was that MP a draft dodger? The issue isn't them picking draft dodgers, it's them picking up anybody that looks like they might be a draft dodger and the tactics they employ to do it.

I'm completely alright with just having fun and hosting your own little sandboxes online, but what good does it do to post and share this with others in its current state? The picture it paints is certainly not representative, and this sort of thing has been done a million times over with much better consistency. Again, I think it's great to hack around in every language and document your journey all the way, but sharing this is borderline misinformation. It's certainly not my duty to right the wrongs of this benchmark.

This entire benchmark is frankly a joke. As other commenters have pointed out, the compiler flags make no sense, they use pretty egregious ways to measure performance, and ancient versions are being used across the board. Worst of all, the code quality in each sample is extremely variable and some are _really_ bad.

> and the 2nd most being the word 'try' instead of just ?

All control flow in Zig is done via keyword

> JXL's theoretical maximum image size is bigger.

This is all fine and good until you actually try encoding such an image with libjxl. What an absolute garbage codebase. I'm sure it's gotten better since I've last used it, but it's impressive how unoptimized, memory hungry, and of course wildly unsafe/crashy it was. Many of the options just completely didn't work, either due to exponential performance, crashes, or weird special-casing that breaks the moment you encode anything that's dissimilar from the sample images used in the sham benchmark made by the libjxl creators. I don't even think a high resolution image had ever been successfully encoded on higher effort levels, since I doubt that anyone trying to do so had the terabytes of RAM required.

I was genuinely flabbergasted when there was mass support for reviving it a couple years ago. I don't think anyone advocating for it has actually used libjxl at all and were just internet hypemen. That seems to happen all too often nowadays.

This all being said, I'm mildly optimistic for a retry with jxl-rs. However, seeing much of the same contributors from libjxl on jxl-rs does make me quite cautious.

Imagine wanting tivoization. Horrifying.

> vlang is really fast, recompiling itself entirely within a couple of seconds.

Does V still just output C and use TCC under the hood?

That might be the case in C land, but C++ land usually has a lot more stuff in headers. For examples, templates are not very useful unless they're defined in headers.

>Users ... want a snappy interactive UI with lots of animations to get the "vibe" right

[citation needed]

There's nothing contradictory here. Not once do I say that I've found the best solution. I merely reached a point where more effort & time spent on this problem will only give me a worse solution. And of course this is merely for myself and everybody has different needs. I never claimed otherwise. The crux of the issue is that we all disagree on what's good and bad, what's necessary and pointless, and too many people are just willingly accepting what's being given to them even if it's worse by their own metrics.

I used to go through phases where I would try this. I gave Windows + WSL a shot. I gave embracing the Apple ecosystem a shot. I gave GNOME a shot. I gave KDE a shot. I was even crazy enough to give ChromeOS as my daily driver a shot. And so on and so forth.

I found every single time that it just wasn't worth it. There was always some critical failure that was either completely underlooked or a 20 year old bug/shortcoming that had every patch to fix it rejected. I genuinely don't understand how people tolerate the dogshit being forcefed to you on all of these controlled platforms. People say that everything is getting worse, and it's true, but it's also true that you're actively choosing to use the things that are getting worse.

I've eventually settled on NixOS and XFCE so I can tweak things to my particular needs while also benefiting from an army of unpaid labor continually improving nixpkgs and other flakes. This setup isn't perfect, but I've optimized for maximal comfort & utility while exerting minimal effort & time. Things really only break when they're self-updating under the hood, which thankfully is rather rare in nixpkgs.

> The argument against using violence to achieve you ends is that if everyone does it, it is bad for everyone.

If you subscribe to Kant perhaps, but most people's argument against violence (and morality in general) is probably not Kantian.