|
posted by dennisn on November 23rd, 2011 at 9:26PM
Fair enough. I am all for evolving websites, and browsers too. Having centrally-controlled, non-customizable, 100%cpu consuming, crippled apps in my webpages is not evolution, IMHO.
|
posted by dsk on November 23rd, 2011 at 10:02PM
>Having centrally-controlled, non-customizable, 100%cpu consuming, crippled apps in my webpages is not evolution, IMHO."
Google docs. 10 local clients editing a session. cpu usage, 5%. 0% when no editing performed. What the fuck are you talking about? 100% consuming my ass. You're a retard .. seriously, leave 1998. It was a good time for you. Your squeegee to academic pursuit ratio was at an all time low. But man, got to move on.
And what is this centrally-controlled, non-customizable? What the fuck do you call this site? Not centrally-controlled? Fully customizable?
|
posted by dennisn on November 23rd, 2011 at 10:09PM
You really have trouble reading. My JavaShit implementation (from Webkit) regularly uses 100%, for many seconds, to load what appears to be a pretty basic webpage -- for many websites. But I guess only your JavaShit implementation counts. (In which case, you really shouldn't be touting JS, but whatever specific fucking implementation it is that you use.)
How the fuck does providing another example of a centrally controlled setup respond to the criticism that JS is centrally controlled crap? I fully acknowledge that this site is shitty, that you can't control it's layout or theme (that much), etc. It would be far better to move it to NNTP, where you could use any of the myriad of newsreader clients that already exist to interact with it.
|
posted by dsk on November 24th, 2011 at 1:30PM
>You really have trouble reading.
You have no reading comprehension. This isn't about wasted cpu cycles of JS engines. If you're using a browser or rendering engine with shit JS, that's your problem. Google's JS engine, for example, is not interpreted but rather compiled straight to native at runtime - and it's really quick. Another example: If you use WebGL the graphics pipeline is offloaded to the GPU - no cpu cycles.
Tell me, if the next generation JS engines is super-fast, would that make a difference to you? No? Then don't throw these red-herrings around.
And it's not about JS either (example: Google wants to put another interpreted language in their browser). It's about what the web is and what it could be and how fuckin stupid you are because you're stuck in 1998.
>How the fuck does providing another example of a centrally controlled setup respond to the criticism that JS is centrally controlled crap?
BECAUSE JS DOES NOT IMPLY A 'CENTRALLY CONTROLLED SETUP' ANY MORE THAN A STRAIGHT HTML PAGE - DUMB FUCK. Seriously do you practice at stupid or does it come naturally faggot?
|
|
|
|