Lemmy is the only website that causes my CPU fan to ramp up, other than games or heavy 3D stuff. Why is that?
Firefox on Windows 10 on Ryzen 5 5600X. It does seem to run better in Chrome. It’s only noticeable when the page is loading.
Sounds to me that Firefox is the “problem”.
Then again, open source projects like Firefox and Lemmy aren’t exactly known for being the best in resource optimization.
Add up the layer of bloatware that’s included in Windows and… voliá! You got yourself an un-optimized mess.
I personally access Lemmy through a low end phone, so i use Jerboa which despite veing pretty “basic” (unlike, you know, Boost), has the advantage of being lightweight and pretty well-optimized.
Jerboa is horribly optimized and scrolling through comments in a 100+ comments thread is like 20fps on a Pixel 7.
+100 comms… Jesus, those are some large ass threads you’re reading.
While i do not (usually) scroll through threads as large as yours, i do own a much cheaper phone (Moto G8 Play), and my experience so far has been great.
Nah, I use Firefox and lemmy is fine for me. It’s also fine for pretty much everything else I use it for, and I use it on my phone (Android), work laptop (macOS), and personal computers (Linux). I haven’t used Windows in over a decade, so I can’t say much about that, so maybe there’s an issue with Firefox on Windows. Also, it’s funny that you blanket blame open source software for being slow in the same breath as blaming Windows, and I’m guessing you’d say that Linux is well optimized.
And Jerboa is also an open source project build by one of the two core developers that work on lemmy, and most of the patches come from the community. The same is true for lemmy’s web UI.
So I’m not really sure where you’re getting the idea that open source projects tend to be poorly optimized compared to proprietary projects (also, Chrome is based on an open source project, Chromium). Projects can be well optimized or poorly optimized, and that’s independent of the licensing of the source code.
If lemmy’s UI is slow, it’s because it’s an immature project still in an alpha stage of development. Or maybe OP is on an unstable instance and a bunch of requests are failing, or maybe they tend to browse image-heavy communities and thumbnails are poorly optimized or something. But it’s unfair to blame any apparent performance issue on the licensing of its source code.
