Is it rarer? I think a lot of modern languages go for the first option but pretty much all C style languages use the latter. It’s probably a wash for which is more popular I’d think.

Ok but, in the second example you typically just put final or const in front of the type to denote immutability. I still don’t see the advantage to the first declaration.

You aren’t though. In most languages that use the latter declaration you would prefix the declaration with final or const or the like to specify it won’t be updated.

Source?

Can I just say it’s hilarious you marked this NSFW, it is quite literally NSFW

In contrast to most people here who talk about solutions to this problem with tooling often used for batch deployment what I’ll say is just my opinion on the matter. Outside of OEM or fleet deployments the advantages of nix just aren’t that apparent. You feel like your system was a house of cards but I’ve personally never felt that way and I suspect neither have most other users. Every OS to ever exist more or less behaves in a similar way, i.e. it’s mutable, so most users have only ever known this behavior. Installing software and then having to configure it in a software specific way is the norm across all existing computer platforms for all of time and for most situations it’s worked well enough. It isn’t nearly broken or painful enough for most people to care. Honestly if nix was the norm for Linux it might even scare away windows or Mac users looking to move. Linux is already a learning curve and completely changing the software installation and management paradigm(beyond using a package manager which can conveniently be explained like an app store) would not help the situation.

The problem with that thought is the lower level bits are very *nix but all the higher level bits like the GUI and other surrounding APIs are all heavily Objective-C/NextStep based and aren’t really all that unixy. We do have GNUStep as a base to use for that to an extent but I really don’t think the unix parts of Mac, are that helpful to porting complex user facing GUI programs.

People say this but I’m not sure I believe that. Keep in mind Google is the only android OEM that allows you to do a bootloader unlock and root without an exploit, it’s officially supported as a developer configuration.

Tbh I’m not an apple person either. The comment about macOS being on 26 caught my eye and I went and did some research.

Darling is a cool project but I think the reason it hasn’t taken off is because there isn’t a lot of software people both want to use on Linux and software that isn’t already covered by wine. You need an overlap between those 2 and that’s a small market

I do find it funny how android is Linux yet their Linux feature is a VM

Looks like they’re jumping from 15 to 26, in fact they’re doing the same thing for iOS, jumping from 18 to 26 for the next release. Looks like they’re synchronizing all their OS version numbers using the year they’ll be primarily used(i.e. 2026) from what I can find.

At this point why use Ubuntu?

🤔 this appears to be the outdated version 4 of this form.

Yeah, at one point vulkan was called glNext so I guess it isn’t that wild. Although I’m surprised they would have started development on a driver before any spec was fully agreed on. Unless they just reworked their mantle driver to become their vulkan driver?

The windows vulkan driver is called XGL? That’s not confusing lol

That is a big deal. RadeonSI has always had official support but for some reason AMD has been ignoring RADV in favor of their own stuff. Glad to see they’re shifting to mesa for literally everything other than compute.

It’s wild to me that even MS and the WSL play nicely with mesa but not Nvidia, God forbid Nvidia play nicely.

Unrelated to the question but I don’t believe webm(matroska) is based on RIFF, webp is but that’s separate.

Maybe it’s just me but it feels like calling it anything other than Linux is just an UHM, ACKTUALLY. And that’s saying something because I’m one of the most pedantic people I know.