I’m sorry, but competition is good.

Installing some closed blob into your kernel, that’s on you.

The problem is if anything is not enough competition. We just saw a centralized monoculture fall over.

Exactly. I don’t even think it’s that different to be honest, it’s just not identical to PS and comes from a different windowing school of thought.

Yer, I didn’t, but this does seams a very Windows’y way of doing things, so can’t see it widely done in Linux/BSD/Unix world.

The joke is Mac and Linux users, who aren’t actually effected, are incapacitated due to being busy gloating on social media.

It needs to be faster and more stable. Crashes and slowness are killer issues. Slowness is single core issue. You can see one core working it’s ass off, but the other like 15, sitting doing nothing. Plus it freezes during that often because it’s not async/multi-threaded enough. Crashes, well that’s just bad, but in this case it’s normally when even 48GB RAM isn’t enough. Bloody curved geometry from external sources with massive messes. Needs more exchanging files methods that isn’t mesh based. But also mesh rationalization tools are need too.

Meh, always done what I need and I find easy enough.

I’ve been in rooms for people forced to switch from PS to GIMP for corporate cost cutting. Every time I went to help someone on something else (animation or exporter related), I’d hear “GIMP can’t do X” and “GIMP can’t do Y”. I’d go over and show it could and how. It was never even stuff that hard. Layer stuff often. GIMP gets a lot of hate I just don’t think is justified.

It’ll catch on at some point. KiCAD did. Blender did. Many other FOSS apps have!

Gimp is intuitive to me. I grew up on RISC OS, not Windows, and only later learned Photoshop. Switching was easy for me, and that was before I got into FOSS. It was just free and legal.

I’ve seen lots of people from a Windows only background struggle with it. I agree it’s not like a normal Windows app. Maybe single window mode helps, but I’m not in a place to judge.

I don’t need some closed blob, with auto updates, in my OS. I doubt many Linux people would be happy with that.

To deal with a bad update, I’d boot a Btrfs snapshot from before the bad update. ‘grub-btrfs’ is great. I confess, it works great for my laptop, but I’ve not yet got it on one of my server. When I finally rebuild my home server, I will though. Work servers, I hope won’t always be my problem!

Not quite the same thing. I doubt, for example, they have a big bag of device trees for different ARM devices to build from.

Can’t see many Linux, or BSD, admins, being happy with “self-updating ring-0 proprietary software”. That’s very much a Windows culture thing.

They can’t fix Windows either, so that’s not an argument.

Least if it’s a Linux system, they don’t need to buy any software to sort it out. It’s free and out in the open.

Android makes RMS’s GNU/Linux language make sense. It is a Linux, but not a GNU/Linux.

Google’s attempt to fork Linux failed and now is mainlined so they can maintain as small a set of patches as they can. Once binder was merged, there is no fork anymore.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/android?h=v6.10

Android is basically a build config now.

TVs that aren’t Android are probably GNU/Linux. Smart white goods are often Linux. Linux even get used in cars. Some of it under Automotive Grade Linux, but not all. If some random thing has a user interface, find licenses and you can normally see what FOSS went in.

You can do so much with so little, at no cost of licencing or access. Why wouldn’t you?

You use things like Yocto and Buildroot to build a image that has nothing but what you need, how you need it.

Except lots of IoT things, router, etc. Also Cromebooks and Steamdecks. And us GNU/Linux people. Android is Linux, just not GNU/Linux. Really isn’t just servers.

The is no single Linux. It’s not a monoculture like that. There are many distros with different build options, different configurations and different components.

Also culture is different. Very few Linux admins would be happy putting in a closed blob kernel driver for anything. In Windows world that’s the norm, but not Linux.

What’s just happened to Windows world would be harder in Linux world. At worse, one distros rolls out a killer update. Some distros would just reboot to the previous kernel.

Mmm depends. I have some automatic updates on my servers: https://wiki.debian.org/UnattendedUpgrades

Few things, in rough order:

• Smaller = less attack surface. You can strip a Linux OS down to only what is needed.

• Open source, so it’s can be peered review. There are Unix distros like OpenBSD, that share lot of user space component options, where auditing is a big thing. The whole sunlight and oxygen stops things festering as much. As abosed to things locked in a box in another box down in a cellar.

• Open source transparency forces corporates to be better. We can see what they are and aren’t doing.

• Diversity. The is no “Linux”, it’s a ecosystem of Linux distros all built and configured differently, using different components. Think of Linux as just a type of base board in a sea of Unix Lego bits. There are plenty of big deployments on BSD bases that share a lot with some Linux deployments.

• Unix security is simplier than Windows security, so easer to not mess up.

Yes and no. Linux is inherently more diverse. All the different distros doing things in different ways, sometimes with different components. It’s not as much of a monoculture as Windows. There isn’t a Linux that 90% is.

Certainly not the way we lunch right now. The energy used, that focused, in that short a time, is insane.

Electric is far more efficient too, thus cheaper. Electricity you can transit over distance over wire and generate however you like. We’ve done it a long time, far and wide.

Turning electricity into hydrogen, distributing it, and then turning it back into electricity to move a vehicle, is so wasteful/expensive.

Just use a big battery.