Well... not really. Terminal response times are way slower than they used to be in the 80's. Sure, we have greater throughput, but we also have greater latency. https://danluu.com/term-latency/
Do you have data / a citation to back up that statement? Most things seem faster to me. As long as the command line responds as faster as I can type, I don't care about it being faster.
That being said, overall speed and what can be handled by the system certainly does matter in many cases, even if it is _just throughput_. I've recently been running commands to search/process data from the command line recently
1. Search through a directory structure with millions of files (find)
2. filter down to ones containing a certain thing (grep)
3. find certain values in the files based on pattern matching (sed)
4. filter to files where one value equals another (test)
I can't imagine that would _ever_ finish running on a computer in the 80s. It works just fine on my current computer (albeit taking a minute to run).
It's at the end of their comment.
That being said, it also seems to have to pull in the 99th percentile behavior in order for the timings to be an issue, and even then it's not horrible; it doesn't get actually "bad" until you consider the worst performance (99.9th percentile) of the worst performer (st). It seems overly picky to me.
Here is another survey which takes it from a different angle.
I should have clarified my original post but it's too late:
I am lamenting primarily against the latency introduced by the amount of layers involved both at the hardware and software level compared to yesteryear.
Compositors, virtualization, higher level languages, etc. do not come for free; despite explosive increases in computing capability, we also have an explosive increase in the number of running threads and the resources required to maintain them.
Another case, Google maps is a bad example in tours. Used it to explore many cities, not only turn by turn direction. It worked get although personally like openstreet maps, because I feel one company s shouldn’t control so many aspects of life and like open source nature of it.
Indeed able to discover a onsen built by community in Hokkaido. That’s based on a lake I saw by just zoom in out of the map to do exploration and saw it built by Ainu community living there. In that turn by turn map helped quite a lot to reach there subsequently just by click and dropping a pin there. Submitted a text describing it and subsequently visited by many people.
Took a journey through treacherous mountain and went up to 2500 meters high and crossed it via a tiny off-road designed for motorcycles. That too did based on exploration of map on phone.
Paper maps didn’t provide such convenience. Yes POS is slow, but then it has different expectations today. Try integrating old POS with 10 payment network working under milliseconds to authorise transactions. Worked enough since 1990 with dos based POS and also wrote IBM MQ C++ code for integration. Don’t want to go back there.
I think today is a step forward. Like always there will be good and bad as it was in 1980 or 1990. But largely today we do much more with computers than we ever did in those days.
So not everything is perceptually slow on computers. Apple Watch, iphone, androids are responsive and usually fast. Windows 10 for certain tasks might be slow but then overall it’s not that bad either.
As far as exploration goes you can do the same or even more today than before. I can discover planets. Built3D model in physical form, use CNC on desktop, do laser cutting in my home.
Built a computer like BBC micro, raspberry pi, fly a computer using fly by wire and test it using real physical model plane. Can do farming on a small scale using hydroponics at home. Can just go on and on about it. All possible thanks to advancement in speed and reduction of size in computing devices and peripherals.
So I feel it’s not slow, just the work we do with old computers is very different from what we do with modern one’s.
Given some corrections, we certainly have the capability to build terminal workflows with less latency. So there is nothing wrong with pushing the community forward.
It's not a matter of nostalgia or just being content with the way things are. People used to argue vehemently against the features we enjoy today such as autocomplete and advanced theming, but a few people kept their heads down and made it happen anyway, because it was The Right Thing.
""" It's caused by conhost.exe excessively hammering the registry to query the following two values:
HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell\TabletMode HKCU\Software\Microsoft\Windows\DWM\ColorPrevalence Having previously reported this issue through Feedback Hub (to no avail), let me offer my observations from debugging this issue:
It's not specific to Dell's XPS series - I've been able to reproduce on any Windows 10 installation from version 1703 and up It only occurs when the console application writes output that causes the console to scroll It only occurs when the console application in question is in foreground/focus Each reg value mentioned above is queried 6 times, per scroll!!! """
The solution I use is to minimize the terminal when it's scrolling. When I compile my projects if I don't minimize the terminal it takes forever to finish.
It depends on how fast you allow items to be written (pixels per unit of time) on your display and if you force writing of everything or allow line skips. If you want to experiment I think putty has pretty fine-grain control options.
I remember doing 'dir' on a large directory, it scrolled so fast, so fast. I said to my friend, "The next generation will be so fast it will have finished scrolling before you finish typing the command."
Sadly, it was not to be. DOS on a 486 is as fast as computers have ever gotten, perceptually.
Consider a VT100. It could only go up to 19200 baud, and couldn't actually handle constant streams at that speed.
However I do agree with the general message of the article. Current UX is a mess, websites are overblown by tons of javascript. There's no reason there should be loading spinners in this day and age with the power we have at our fingertips.
The VMS manuals suggested that system administrators may want to keep the hard wired terminals down to 2400 buad and hide the fact from users by turning on "smooth scroll" (which only scrolled about that fast anyway) in order to keep the interrupt load down on the Vax. Something about batching of interrupts on the multiport serial cards.
The problem is just that there's too much javascript running in the browser and it's too poorly written (loading each post individually in Reddit by example instead of batching them). Reddit's redesign in particular is really really bad. At least they offer the old site but it looks so bad. I'd love to have something looking more modern but without the javascript overload.