![](https://aggregatet.org/pictrs/image/1342e9a3-c172-4918-8a34-accd26338de2.jpeg)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Can you (or a human) expand NPM, presumably not the Node Package Manager?
Can you (or a human) expand NPM, presumably not the Node Package Manager?
It’s also a lot better than doing it in 100% C++ templates!
I tried but it turns out writing device drivers it very very boring
The hell? This is precisely what atomic desktops were supposed to save us from!
I’m planning on making Linux from super scratch where I start with the kernel and write every other component myself. ETA: 9000000 years
I’m kind of souring on Fedora Kinoite. I generally sometimes pop in to try how Linux is doing, and I had great hopes for KDE Plasma 6 and immutable distributions for stability. However, I’ve found that many things in the UI are still wonky and broken, fonts don’t render well, and I keep running into limitations in the flatopak/containers ecosystem.
Here are a few paper cuts:
I meant, obviously in the sense that Windows and macOS both apparently already do this and that it’s a desirable property to have, not that it’s technically easy.
Lots of bad answers here. Obviously the kernel should schedule the UI to be responsive even under high load. That’s doable; just prioritise running those over batch jobs. That’s a perfectly valid demand to have on your system.
This is one of the cases where Linux shows its history as a large shared unix system and its focus as a server OS; if the desktop is just a program like any other, who’s to say it should have more priority than Rust?
I’ve also run into this problem. I never found a solution for this, but I think one of those fancy new schedulers might work, or at least is worth a shot. I’d appreciate hearing about it if it does work for you!
Hopefully in a while there are separate desktop-oriented schedulers for the desktop distros (and ideally also better OOM handlers), but that seems to be a few years away maybe.
In the short term you may have some success in adjusting the priority of Rust with nice, an incomprehensibly named tool to adjust the priority of your processes. High numbers = low priority (the task is “nicer” to the system). You run it like this: nice -n5 cargo build
.
I have no idea what you’re talking about but you seem to be quite upset about something I guess
I’ve also set up both and in my experience Nextcloud is much much more complicated to set up but simpler to use and syncthing is pretty much the exact opposite.
In my case, a rather long time ago, it failed to reliably sync my files, had a super annoying web based UI, was a pain to get all my devices to talk to each other because because they had to join some sort of peer to peer network and authenticate with the earth other all three. It also didn’t have any working solution for mobile devices. Hopefully all of that’s fixed now because there’s no inherent reason it couldn’t work.
I’m a bit worried about their choice of name