Hacker News new | ask | show | jobs
by pantaloony 2157 days ago
Gnome is crashy, gobbles resources, incredibly laggy, and drops frames on my beast of a newish hex-core machine. I've switched to KDE in a VM on Win10 (some of the crashes were Linux graphics drivers, not entirely Gnome's fault, though some were Gnome—running in a VM makes them go away entirely, and also all my bluetooth stuff stays paired much better since Linux doesn't even know it's bluetooth) and it feels 4x as responsive on literally half the hardware, and under virtualization, as Gnome did.

I recently trialed a 2GB memory (!) dual-core Celeron minipc as a workstation, and if I could have solved all the 4k 2x scaling issues without spending hours (more) on it or resorting to a too-heavy-for-the-hardware DE, and gotten 60hz out of it rather than 30, I'd probably have upgraded the RAM to its max of 8GB and been totally happy on it. Void Linux with suckless tools made it feel blazing fast, as long as I avoided webshit (so, Sublime over VSCode, keep Slack the hell away from it, use a real email client rather than a webpage, that kind of thing). All browsers felt too slow to even launch except Surf and qute, and the latter was a tad slower and jankier than Surf so I settled on that, but it was fine as long as I avoided the kind of pages that eat a couple hundred MB and burn cycles for no clear reason (which is lots of them, sadly). I bet I could have made it work even better if I'd looked into adding a disable/enable JS toggle, defaulting to off, and maybe some kind of click-to-load-media thing, but it was surprisingly usable as it was. FF and Chromium were far too heavy to launch with no page loaded, of course. Man I miss pre-2.0 Firefox, when it was light and fast.