3 ms·
If a page contains multiple sections it often waits ~10s until it's usable and I have to wait looking at rotating busy signs (compare e.g. NHL.com and its previ
by bitL 8y ago
If a page contains multiple sections it often waits ~10s until it's usable and I have to wait looking at rotating busy signs (compare e.g. NHL.com and its previous version that loaded instantly). Lately I am also getting extremely upset when on a recent i5 NUC just vertically scrolling on a trivially looking page stutters and NUCs fan goes to overdrive. It's getting ridiculous. It's not like you can pan in 2D or 3D an move in any direction, doing creative things, it's just a silly looking page with some title, links on the right and some images and embedded videos (just a large preview pic) in the main body.
Everything is getting extremely bloated. Can't wait until I need an overclocked Threadripper with 1Gbit Internet to see what the weather forecast is...
- orange8 8y agoIf your "world class" games from 10 years ago were online based, they'd have the same problem. So its not really the web tech you are against, its the client-server application model.
- ori_b 8y agoSo, your argument is that it's not the implementation, but that the technology itself is fundamentally broken.
- orange8 8y agoThat's not my argument, and I can see how it got misunderstood: mean to reply to the grandparent comment, which was comparing the responsiveness of a desktop app where all required resources are installed and locally available, to that of a web application. Whatever you build it with, if the data has to come down "through the wire" then you will wait..
- bitL 8y agoMy objection was that the previous designs provided exactly the same real-time information, used client-server architecture as well, but were fast.