3 ms·
That makes sense. Browser implementors would definitely balk at anything that they couldn't guarantee would stop in a reasonable amount of time.
by jeffasinger 13y ago
That makes sense. Browser implementors would definitely balk at anything that they couldn't guarantee would stop in a reasonable amount of time.
- throwaway1980 13y agoWhat about JS?
- jeffasinger 13y agoJS is trivially Turing complete (given infinite RAM) See this: http://www.turing.org.uk/turing/scrapbook/tmjava.html http://www.turing.org.uk/turing/scrapbook/tmjava.html
- throwaway1980 13y agoWhat I meant was, why don't browser implementors balk at it?
- jeffasinger 13y agoI think the thing is, that JS can be executed separately from the layout engine, but CSS can't, however, I'm definitely not an expert in the matter.
- gcr 13y agoBrowser vendors control the javascript VM. Though we can't solve the halting problem, we can just throttle or unplug the JS interpreter if it causes usability problems. But CSS is required for the site to look right There's no way to turn it off without messing with the site's layout.