News for hackers. Stuff that matters.
Re:What Spectre and Meltdown Mean for WebKit by xtanx on Tuesday January 09, 2018 @04:31AM (#16104765)
The statement "a better experience" is debatable.

I cannot remember how many times I have visited SPA websites that break the browser url history.

Also, if a SPA fails to load a request for any reason, try reloading it. Ops you start over.

And I am not talking about some people that don't know what they are doing. At times I've had issues with Google's new developer console, gsuite admin, analytics, product hunt and others.

Re:What Spectre and Meltdown Mean for WebKit by send_computers on Tuesday January 09, 2018 @04:41AM (#16104818)
These are all examples of bugs or badly designed/coded applications. Don't blame JS for bad coding...
Re:What Spectre and Meltdown Mean for WebKit by alien_at_work on Tuesday January 09, 2018 @08:44AM (#16106055)
Nonsense. Bad tools are bad tools as evidenced by the fact that literally no one can use properly at scale.

Evangelists of bad technologies always like to trott out the nonsense about "a good carpenter never blames their tools"... well of course they don't: they buy the tools and always buy the appropriate ones. Further, if they did complain the customer would wonder why they bought bad tools in the first place.

A carpenter would never try to build a building with a "JavaScript" equivalent in the first place. They recognize the tool as garbage (perhaps after trying, and failing, to use it) and switch to something more appropriate.

Re:What Spectre and Meltdown Mean for WebKit by seba_dos1 on Tuesday January 09, 2018 @08:33AM (#16105982)
But it's really really really hard to not do bad code in JS - a whole ecosystem seemingly built to encourage terribleness.
Re:What Spectre and Meltdown Mean for WebKit by xtanx on Tuesday January 09, 2018 @04:48AM (#16104838)
Well, if google can't do it properly then who can? Also, I was talking about SPAs specifically not JS in general.