Name: Anonymous 2015-01-24 6:31
Sans javashit. I have an iPhone 6 with the fastest data plan in a big city and still 60% of websites eventually cause Safari (and Chrome) freezes. It may be mem leaks in the browser, but more likely PEBCAK and the developer's javashit is too cumbersome. Even the sites that use bootstrap.js can die.
One site that has neither crashed nor frozen on me is craigslist. The only time it comes close is loading reCAPTCHA's javashit bloat. It's disgusting how github kiddies release "elegant javashit-for-mobile library" which advertise being "compact and fast" when that is simply impossible when it uses javascript. There is nothing wrong with "grayscale" web pages with headers, links, and navigation bars using system menus, not n-nested DIVs and js. These interfaces are actually more familiar and intuitive for most users. Some web programmers try to make the site an original work of art that would only be appreciate by loyal users (see: any commercial blog). Users have a low tolerance for frustration when browsing because the exact same information is the next Google result. Flat interfaces avoid these problems. They load fast (priority no. 1 for mobile), are easier to maintain, have zero learning curve for users, highlight content which is what people are after, and allow advertisements to be actually noticed thus more potentially clicked.
The swipe on the touchscreen in a browser should only imitate a mouse. We shouldn't be able to move between articles with the swipe, unless the OS does that for everything else. Websites trying to create their own OS find themselves nested not only in the device's OS but also the browser process. So instead of making their jobs easier and just simplifying their interfaces, many websites decided to write their own free native apps. Wait, you want me to switch out of this process to another just to check your site? Well then I'll never visit it.
It's simple to write everything on the server to end up with just the page the user requested. No, there is no need for dynamically loading shit onto the page. It will take the same amount of time to load a whole new FLAT page with what the user requested. This all stems from a mentality of developers that somehow sending a new page is costly. Well, I guess it is if you're uploading 10^5 SLOC of javashit with even the Contact Us page. There's nothing to justify JS in 2015 when civilized people do 90% of web browsing on mobile phones. It needs to die.
One site that has neither crashed nor frozen on me is craigslist. The only time it comes close is loading reCAPTCHA's javashit bloat. It's disgusting how github kiddies release "elegant javashit-for-mobile library" which advertise being "compact and fast" when that is simply impossible when it uses javascript. There is nothing wrong with "grayscale" web pages with headers, links, and navigation bars using system menus, not n-nested DIVs and js. These interfaces are actually more familiar and intuitive for most users. Some web programmers try to make the site an original work of art that would only be appreciate by loyal users (see: any commercial blog). Users have a low tolerance for frustration when browsing because the exact same information is the next Google result. Flat interfaces avoid these problems. They load fast (priority no. 1 for mobile), are easier to maintain, have zero learning curve for users, highlight content which is what people are after, and allow advertisements to be actually noticed thus more potentially clicked.
The swipe on the touchscreen in a browser should only imitate a mouse. We shouldn't be able to move between articles with the swipe, unless the OS does that for everything else. Websites trying to create their own OS find themselves nested not only in the device's OS but also the browser process. So instead of making their jobs easier and just simplifying their interfaces, many websites decided to write their own free native apps. Wait, you want me to switch out of this process to another just to check your site? Well then I'll never visit it.
It's simple to write everything on the server to end up with just the page the user requested. No, there is no need for dynamically loading shit onto the page. It will take the same amount of time to load a whole new FLAT page with what the user requested. This all stems from a mentality of developers that somehow sending a new page is costly. Well, I guess it is if you're uploading 10^5 SLOC of javashit with even the Contact Us page. There's nothing to justify JS in 2015 when civilized people do 90% of web browsing on mobile phones. It needs to die.