News for hackers. Stuff that matters.
Re:Did Windows 10 slow down with each feature update? by ksec on Monday June 21, 2021 @09:55PM (#27587126)
That is what I have been banging on about for years. Latency added, not just in Software, but in Hardware as well from Display, Keyboard, Mouse and even Network. The past 20+ years the whole industry nearly went all out on optimising for throughput.

Sometimes I look at macOS, Windows 10. Apart from some UI facelift I dont even remember a single user feature that was relevant or important in the past 5 years. Apart from latency added cause of feature bloat

The beauty of Gaming is that there are finally some incentives for people to work on the issue.

And a video from Microsoft Research on 1ms Latency

https://www.youtube.com/watch?v=vOvQCPLkPt4

Re:Did Windows 10 slow down with each feature update? by samplatt on Tuesday June 22, 2021 @12:28AM (#27587998)
>Sometimes I look at macOS, Windows 10. Apart from some UI facelift I dont even remember a single user feature

The user "feature" that comes quickest to mind for Windows 10 was the first run of calc.exe showing a popup notification begging for a 5-star rating in the Microsoft Store.

The fucking CALCULATOR. Literally the first and most basic function any computer ever had, which has had NO ui changes in the million software and hardware permutations for 70 years, because it's already perfect. Something has gone unfathomably, fundamentally wrong with how Microsoft works internally.

Re:Did Windows 10 slow down with each feature update? by alternatetwo on Tuesday June 22, 2021 @03:34AM (#27588971)
I installed the Win7 calculator, and it works like a charm. The no-hex functionality and splash screen really are terrible. I was used to start typing immediately after win+r calc ...
Re:Did Windows 10 slow down with each feature update? by mongol on Tuesday June 22, 2021 @01:42AM (#27588372)
What rating did you give it?
Re:Did Windows 10 slow down with each feature update? by samplatt on Tuesday June 22, 2021 @02:09AM (#27588522)
I gave it one star and left a scathing review. What are they going to do, not include a calculator in the next Windows?
Re:Did Windows 10 slow down with each feature update? by ht_th on Tuesday June 22, 2021 @02:49AM (#27588719)
They might. It would not surprise me if a lot of people just type their calculations into the browser address bar or in their Internet search engine's input box. Or search for a calculator web application, and use that as their calculator.
Re:Did Windows 10 slow down with each feature update? by noisy_boy on Tuesday June 22, 2021 @02:41AM (#27588681)
They can not include it and instead provide a menu option that actually takes you to the store on first run :)
Re:Did Windows 10 slow down with each feature update? by rightbyte on Tuesday June 22, 2021 @06:03AM (#27589793)
Don't give them any ideas please.
Re:Did Windows 10 slow down with each feature update? by formerly_proven on Tuesday June 22, 2021 @02:14AM (#27588555)
> The past 20+ years the whole industry nearly went all out on optimising for throughput.

It used to be that GPU drivers would queue up to ~10 frames just to get slightly higher FPS in benchmarks (while adding basically a quarter of a second input lag)... naturally, this is an extremely bad trade-off for gaming, but made them look a few percent (at most) better on paper.

Re:Did Windows 10 slow down with each feature update? by fouc on Monday June 21, 2021 @11:57PM (#27587828)
You reminded me of "Computer latency: 1977-2017" https://danluu.com/input-lag/
Re:Did Windows 10 slow down with each feature update? by cheschire on Tuesday June 22, 2021 @01:21AM (#27588249)
"Finally" seems a bit myopic. The war against latency has been going on continuously since the beginning, even in gaming. Check out nearly any content John Carmack has ever written or spoken on the topic of gaming or VR, just as one example.
Re:Did Windows 10 slow down with each feature update? by ectopod on Tuesday June 22, 2021 @06:03AM (#27589786)
For those of us who grew up with 8-bit home computers low latency was the starting point. On my first computer you could detect a keypress, update video memory and (assuming the beam was in the right place) see the results on screen in a few microseconds.