Breaking the grip JS has on the DOM: Difference between revisions

m
(LegacyPlugin isn't ignorable)
Line 389: Line 389:


Any idea what we're doing with setTimeout and setInterval? Namely, in their string argument form. --[[User:Hixie|Hixie]] 01:43, 28 Aug 2005 (PDT)
Any idea what we're doing with setTimeout and setInterval? Namely, in their string argument form. --[[User:Hixie|Hixie]] 01:43, 28 Aug 2005 (PDT)
----
very random discussion
very minor note, not sure where else to log this, feel free to remove it if you find it objectionable...i find it disappointing that this is only being considered for XUL, not as a direct alternative to JS. props to brendan, i do not intend to speak disrespectfully of his contribution, but everywhere now i see "applications" written using ajax (i don't think this is a fad). this may very well be the next step in application development, and we are very early on in the process and have a chance to set a decent foundation before the web application economy takes off. i think we all will  admit JS is not a language many of us are interested in coding largish apps in, once again, no disrespect. ten years from now JS will be like a tyranny, not a tool, with countless hacks to get around its limitations. i love the idea of language neutrality, i would love to be able to drop ruby in where i am now using JS. i understand the security issues but there has got to be a way. please, if we don't fix this as an application platform, someone else will, refragmenting a market that is finally coalescing around standards.
2

edits