Re:Stadia died because no one trusts Google
by password4321 on Saturday October 01, 2022 @10:41PM
(#33052324)
I was just whining how when Chrome-based browsers first open up on my 5400rpm hdd, I paste in the URL and press Enter, then it loads the default home page and wipes out what I pasted... "you're goin' nowhere!"
[ Parent
| on HN ]
Re:Stadia died because no one trusts Google
by MereInterest on Sunday October 02, 2022 @12:19AM
(#33052812)
Opening Google maps, the text entry is editable far, far before when it should be. As soon as the page loads, I can start typing. Then the JavaScript starts running, and helpfully selects the text entry, placing the cursor at the beginning of the text field. Then some cached suggestion loads, inserting some suggested search for the area being viewed.
The end result is that anything I type gets jumbled or overwritten multiple times before the page settles down and can actually be used.
Re:Stadia died because no one trusts Google
by int_19h on Monday October 03, 2022 @10:44PM
(#33076217)
This is the general curse of async UI these days, and it's everywhere from the web to native desktop apps to the OS itself.
Obviously, it can be done right, but it seems that most devs who are so eager to jump on the async bandwagon have no idea that they have to make that effort now.