I don’t think upscaling the text/UI and downscaling the whole screen are the same thing.
I don’t think upscaling the text/UI and downscaling the whole screen are the same thing.
Haiku
Personal use 0.2%
Pro. use 0.1%
Some people love a challenge I guess. No disrespect to Haiku.
Tumbleweed surprised me with how it receives constant, up-to-the-minute updates yet somehow doesn’t ever seem to break.
It also surprised me with how much I like KDE. I had used it way back in the day when it was a bit complicated looking and ugly. These days Plasma makes the whole experience nice.
I have set up OpenSUSE Tumbleweed on a couple of my machines with Windows 11 in a KVM virtual machine. Windows runs at a perfectly good speed in this setup, and I use it when I want quick access to proprietary software that only runs in Windows. It’s simpler and more reliable than messing around with Wine. It can be a little more complicated if you want to share folders between guest and host, but there are several ways you can achieve that.
Yes, in addition to MS Office, MacOS is particularly used by a lot of people who work in art or music, and none of the programs they use professionally for that will run on Linux. You can’t just go it alone with free software when all your colleagues expect you to use proprietary tools. And what people like about MacOS is that it is reliable for running these programs with a minimum of fuss, has a solid low-latency sound system (for musicians), and has easy access to Apple features like cloud backup. Imitating its desktop brings none of that.
So we know these things work on one person’s computer (theirs) but not on another’s (yours). Such anecdotal experiences are not a reasonable basis on which to judge any OS, positively or negatively.
To be fair, most of them aren’t as nasty as C++. But Rust certainly gives you a sense of security you don’t get with most other languages.
I’m no Rust expert, but in my experience the borrow checker is a pain for a bit, then you start to get a sense of what works and what doesn’t, and after a while it has taught you to write cleaner code.
As one of the other quotes suggested: fork the kernel project and rewrite it entirely in Rust
That’s not practically possible given the scale of the kernel. And doing a total rewrite is almost always a recipe for getting stuck and, if you ever create anything, creating something worse.
Replacing C with Rust in the upstream kernel is akin to replacing the engine in a car while it’s running or being used every day.
Almost all real-world software development is like this. That’s what we do.
Maybe I’m a bad programmer, or maybe I’m just busy and tired, but honestly I don’t often care enough to investigate until I need to build something similar.
Yes. They just don’t want the AI being trained on its own excrement.
This should be the splash screen on every distro.
That’s why I’d love to see more developers take another look at Linux. Such that they may develop better proficiency in the basic katas of the internet. Such that they aren’t scared to connect a computer to the internet without the cover of a cloud.
The developers I have come across mostly use Linux if they can, or another OS if they can’t (e.g. when developing specifically for Apple or Microsoft platforms). Are there many that haven’t even looked at it?
I wonder how plausible a complete Rust fork of the kernel would be.
It sounds highly impractical, and it would probably introduce more issues than Rust solves, even if there were enough people with enough free time to do it. Any change must be evolutionary if it’s going to be achievable.
Not as annoying as all these people being sent over from number 302.
https://wayland.freedesktop.org/xserver.html
It provides backwards compatibility for running X apps under Wayland.
OpenSUSE Tumbleweed is another good distro that uses KDE.
Microsoft fired its entire QA team 10 years ago, and shifted the responsibility for testing onto developers. They also got rid of their dedicated hardware lab where software would be tested on many different hardware combinations.
I have worked in two companies that made the same move of firing QA, and in both the quality of the released software took a marked dive. (In neither company did senior management admit that what everyone warned them would be a mistake was a mistake. Instead they blamed developers.)
These days Microsoft’s testing team is whichever users receive each update first. They rely on users and telemetry to do what should be the job of dedicated testers.
I’m old enough to remember the start of eternal September. It hasn’t stopped yet.
We’re doing this again?