Also using Orion! It’s the only one that’s convinced me it’s better than Safari, primarily because it’s actually more aggressive with power savings than Safari. The implementation to kill idle tab processes almost immediately is very effective imo.
SpacemanSpiff
joined 2 years ago
That might be true, I’m not a mechanical engineer but despite that, my understanding is that within the engine block itself, cylinders are primarily lubricated via the system holding pressure. This pressure starts to drop the second the engine ceases.
You can notice the effect on cars that have realtime oil temp monitors. Mine does, and it’s digital. My stable oil temp is around 216 degrees Fahrenheit. After a start-stop cycle, even for only 5-10 seconds or so, the temp drops about 5-8 degrees. After a minute, the temp is down 25 degrees. That’s significant. Essentially the engine is no longer “at temp” for the first 30 seconds or so after it resumes. That’s 30 seconds of additional semi-cold, under pressure wear each cycle.
What about the fact that the oil drains to the pan in those few seconds that the engine is stopped?
This is my real concern. Sure you can upgrade starter motors and batteries to handle the extra cycles, but you can’t do anything about increased scoring and wear on cylinders in the milliseconds before the fluids start to circulate again.
It depends on what you mean by other servers…Lemmy instances? I haven’t seen any differences between kbin instances.
Kbin is entirely different software from Lemmy; it’s a completely different backend.
So that would be why it’s “better” in that regard than Lemmy instances. My understanding is that it’s a bug in Lemmy that will be fixed soon.
The “popping” of the feed in Lemmy is tied to their use of websockets instead of http. I believe the devs stated they’ll be moving off of websockets in the future.