Earlier quoted context omitted.
When working on digital settop boxes a decade or 2 ago, channel change latency was one of the toughest problems. Eventually we (collectively, the whole industry) gave up and settled for 1 second as acceptable. Channel surfing quietly went away. When your i-frame only comes so often, there's not a whole lot you can do. Nowadays, that problem is solved by reducing actual live content to a strict minimum; everything els…
These days they should be able to guess what 20 channels you might change to and start recording those in the background. I've always suspected the reason it's slow is because you press the remote button, the DVR sends that to the provider, the provider has to verify that you can do what you are asking it to do, then a response comes, then the change can start.
Almost everything on computers is perceptually slower than it was in 1983 (2017)
51–60 of 451 posts
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#52Has anyone ever also noticed how cars are always heavier than the bikes we used when we were children. And how much more air you need and how much longer it takes to fill a car tire with a hand pump. Also, remember when none of us was a portuguese author and we used paragraphs rationally and wrote things down without splitting them into 200 letter long strings because we used mediums made for rants and did not need a…
Calling this sort of thing out, when the entire industry keeps professing they're "making the world a better place", is valuable IMHO. I happen to agree with a lot of the examples.
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#53There are some good points here, but of course I am going to ignore those to talk instead about the stuff I disagree with! The section about google maps follows a form of criticism that is widespread and particularly annoys me, namely => popular service 'x' doesn't exactly fit my power user need 'y', therefore x is hopelessly borked, poorly designed, and borderline useless. There is always room for improvement, but a…
The example for maps is not a "hyper specific use case": "The process you WANT: pick your start and end. now start searching for places in between. Your start and end are saved. When you find someplace interesting, add it to your list. Keep doing that, keep searching and adding." That's a common use case. The problem with Google maps (and the problem with a lot of modern software) is, as you say, it makes a lot of gu…
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#54Kind of related: does anyone else notice how long it takes to change channels on the TV these days? It used to be instantaneous when cable first came out and at some point it became this laggy experience where you'll press buttons on the remote and the channel takes forever to change. I hate it and it's one of the reasons I don't have cable any more.
The central reason is that modern video codecs use I-frames and P-frames (sometimes also B-frames; even though as far as I am aware, these are not used for TV broadcasts); see https://en.wikipedia.org/w/index.php?title=Video_compression... I-frames are only sent, say, once or twice a second. When a channel is switched, the TV has to wait for the next I-frame, since P-frames (and B-frames) only encode the difference t…
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#55Earlier quoted context omitted.
Unless I'm very mistaken about modern digital transmissions, cable coming into the house is still based on a broadcast system, which means you're getting everything all the time. The frames are all there for every channel, they're just not being read. I don't know how much processing or memory it would take to read and store frames for surrounding channels to the one you're on, but I imagine its possible.
Feel free to find a chipset on the market that can decode hundreds of channels of Full HD H.264 simultaneously...
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#56Earlier quoted context omitted.
all they need is to create to a low rate channel with slowly updating snapshots of all the programs being transmitted. i don't know anyone who does that, but it is damn trivial. (former middleware engineer)
> all they need is to create to a low rate channel with slowly updating snapshots of all the programs being transmitted. > i don't know anyone who does that, but it is damn trivial. Getting this standardized in an international standard is far from trivial.
pretty much anything cable and satellite tv companies do is against the user. there is very little (if any) innovation in the industry, and that's why they will eventually die.
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#57Has anyone ever also noticed how cars are always heavier than the bikes we used when we were children. And how much more air you need and how much longer it takes to fill a car tire with a hand pump. Also, remember when none of us was a portuguese author and we used paragraphs rationally and wrote things down without splitting them into 200 letter long strings because we used mediums made for rants and did not need a…
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#58Earlier quoted context omitted.
It takes time to pick up the MPEG2 scheme and start decoding.
all they need is to create to a low rate channel with slowly updating snapshots of all the programs being transmitted. i don't know anyone who does that, but it is damn trivial. (former middleware engineer)
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#59This is a very hard rant to read. The examples either aren't factually true or are poorly explained and the "solution" is largely nebulous. I feel like this topic has merit and with a well written article with real examples (both 2019 and 83) it could be something special, but this isn't that. I'd be interested to know how many upvoted based on the title/what they expected this to be, rather than after having tried t…
My first job out of college was to migrate an internal inventory management system from a in-terminal keyboard-based application (which nobody could be hired to maintain, as they stopped teaching IBM-RPG to college grads twenty years before) to a webapp. As part of gathering requirements I learned how to use it, and god damn was it fast. I watched salespeople and warehouse stockers alike fly through the menus so fast that they didn't even need to wait for screens to draw before advancing (and the screens were snap-quick to draw!), they just conjured the paths they needed from muscle memory and batched up a dozen keypresses and boom, done. I felt awful imposing this new laggy webapp on them, though I did make sure to at least leave the familiar keyboard shortcuts.
But at the same time I think the author is somewhat overselling the idea that keyboard interfaces are just as intuitive as mouse interfaces. To use the application above as an example, when we showed the new webapp to people who only had cause to use this system occasionally, they were able to navigate it more easily and professed to prefer it over the old one. Contrast this with people who used the system all day, who grumbled at the loss of productivity and need to re-learn things.
Keyboard shortcuts are great for power users who have cause to master an application thoroughly. For occasional users who don't need to master it and don't want to learn anything, a mouse will get them up and running faster. And, of course, there's still no excuse for how much lag and slowness we willingly endure in our modern UIs.
Re: Almost everything on computers is perceptually slower than it was in 1983 (2017)
#60There are some good points here, but of course I am going to ignore those to talk instead about the stuff I disagree with! The section about google maps follows a form of criticism that is widespread and particularly annoys me, namely => popular service 'x' doesn't exactly fit my power user need 'y', therefore x is hopelessly borked, poorly designed, and borderline useless. There is always room for improvement, but a…
The thing with Google Maps was that it was actually reasonably good and intuitive on mobile until sometime 5 or 7 years ago when someone decided it had to be "simplified".
The old version was easy: you enter "to" and "from", and it gives you a route.
I think it also had multiple entry points so you could choose "navigate", "browse" and "timeline" or something directly from the system menu.
The "simplified" version removed all that + the timeline feature I think and replaced it with one search box.
The timeline came back after a while as did a number of other features they removed but it still isn't as easy or intuitive as the early versions and it still annoys me every time I want to get a route from A to B (as opposed to from where I am now to B).
Compare this to Windows 95 that I disliked for a few months until I got used to system wide drag and drop and realized it was in fact better than Windows 3.1.