3 ms·
Who remembers how snappy the experience was on a fresh XP install? Sure, everything loaded slow off disk, but once you got your basics into RAM it felt so much
by bob1029 7y ago
Who remembers how snappy the experience was on a fresh XP install?
Sure, everything loaded slow off disk, but once you got your basics into RAM it felt so much faster by comparison to how Win10 responds today. Explorer.exe in particular. What a gem that implementation was. I could play folder tetris at lightspeed with that thing, because it actually felt faster than I could ever go. Today, I am sad to report that despite my reflexes not being what they used to, I now wait upon file explorer to do its thing on a regular basis.
To see what I'm talking about, just run something extremely lightweight like mspaint, then right click it in your task bar. Be sure to have a stopwatch handy. It might take a little while for the context menu to appear and you don't want to lose track of your seconds. It's the perfect amount of delay right between complete disengagement (e.g. walking off to get coffee) and proper instantaneous feedback. I sometimes wonder if psychologists working at Microsoft have specifically tuned this delay to be as misanthropic as possible. I used XP not too long ago and I recall a visceral emotional experience due to the realization that we will never have a UI that feels that snappy again branded by Microsoft.
I realize I can probably get my low-latency UI fix with various Linux installs... Anyone have any recommendations? Who has the fastest window manager these days? With .NET Core working on Linux and any code targeting it being largely portable... I could maybe get used to a new normal on Linux for purposes of software development, which is also when I'm looking for a snappy UI. Visual studio on windows being the bloated nightmare it is... Some days I spend a few minutes writing specifications for a new IDE just as a means of catharsis. There is zero excuse for the kinds of delays I regularly see between keypress and UI feedback.
- zozbot234 7y ago> I realize I can probably get my low-latency UI fix with various Linux installs... Anyone have any recommendations? Who has the fastest window manager these days? LXDE (the original, not LxQT) is still well-supported on Debian Stable, and that's probably the closest thing to a 'XP-like or better' experience on Linux these days. Xfce is not far behind, though. Or you can experiment with more niche stuff such as WindowMaker, Fvwm95, IceWM and whatnot, but you're more likely to run into unimplemented stuff and these are simple window managers, so utility programs must be installed separately. Of course, you should be mindful of RAM requirements. A modern Linux install will need at least 1GB to feel really snappy, which is far above the typical XP machine.
- agumonkey 7y agoI rarely use LXDE because it feels like win95 alpha1 and XFCE like Win2K Plus! Mint + XFCE is really a fine combo.
- agumonkey 7y agoEven the nicest Linux desktop has more lag than ~KDE3 days. I think that's a global shift in how rendering is done, it used to be crude and glitchy but extremely cheap cycle wise, now you have compositing ... smooth matrices but maybe (I never wrote code for composited DE) this cause a fixed offset in response ?
- zozbot234 7y agoThe compositing step is done entirely on Vblank and is typically hardware-accelerated (hence no CPU overhead), but this means that updates to the screen only happen at next Vblank. With a single, non-composited framebuffer, an update happens as soon as the updated content is "scanned out" to the display, so you will save half a Vblank interval on average. (You will also incur some tearing but that only matters when showing media content, not in typical use.)
- alxlaz 7y agoMost of the latency you see in modern Linux desktops comes from the tech stack, not the compositor. E.g. Plasma, and lots of other KDE components, are QML-based. You can see ths if you disable compositing. For example, you can run KDE with Openbox, without compositing, and lots of things are still laggy. Same thing with XFCE, where it's possible to disable xfwm4's compositor. Not picking on KDE specifically -- I'm mentioning it because I use it on a few machines and it's the one that I'm most familiar with. Compositing will inevitably give you some lag, but there's cap on how much, depending on the Vblank time. Extra lag is entirely self-inflicted :-).
- agumonkey 7y agothanks. I only mentioned composting because that's the only change I know happened since 90s gui engines, so I thought it would have an impact.
- alxlaz 7y agoAnd it does! Even when it's the only form of lag in existence, it's still noticeable -- see http://www.lofibucket.com/articles/dwm_latency.html http://www.lofibucket.com/articles/dwm_latency.html for the notes of someone else who's noticed it. I usually disable it on my work machine, too. I don't use flat themes anywhere, so I don't really need shadows, and I'm more than happy about the reduced latency.
- Rury 7y ago>To see what I'm talking about, just run something extremely lightweight like mspaint, then right click it in your task bar... >I'm looking for a snappy UI. Problems like these I think stems from poor design decisions made at Microsoft as a whole. Take ARC compared to Garbage Collection as an example. Not sure why Microsoft chose a Garbage Collector design when implementing .NET, but given how Garbage Collection works, there's always risk of it causing UI stutter when it's doing its thing. Apple in comparison chose an ARC design when implementing Swift to avoid potential responsive UI issues... even if ARC is overall less performant. Then you also have the decisions to support backwards compatibility and you have a mess on your hands. Frankly, I hate it somedays when I click on my windows calculator app and it opens a blank window and just sits there. I have to kill it and restart it 2-3 more times before it actually opens up. Stuff like this should never happen!
- pjmlp 7y agoReference counting is garbage collection. Same UI issues can happen in reference counting with deeply nested data structures.
- Rury 7y ago>Reference counting is garbage collection. Sorry you're right, I meant tracing garbage collection. >Same UI issues can happen in reference counting with deeply nested data structures. Only if done poorly. The difference is this is deterministic and therefore an issue you can control and avoid with ARC (albeit at a cost to overall performance). The point was that ARC doesn't have the potential for a uncontrollable random process kicking in, stopping your app and causing UI stutter as it cleans up memory, whereas tracing GC does. A good comparison: http://developer-toolbox.blogspot.com/2017/12/garbage-collection-vs-automatic.html http://developer-toolbox.blogspot.com/2017/12/garbage-collec...
- pjmlp 7y agoThis one is more up to date, https://github.com/ixy-languages/ixy-languages https://github.com/ixy-languages/ixy-languages