3 ms·
Going the other direction (moving server-side languages into the browser) is simply not feasible with the current rate of browser development and adoption. It w
by sant0sk1 17y ago
Going the other direction (moving server-side languages into the browser) is simply not feasible with the current rate of browser development and adoption. It would be at least 5 years with a concentrated effort to accomplish such a task.
- mahmud 17y agoPlay with the TCL plugin for IE or Firefox. That thing is a winner. (NB: last tried in 2004, IIRC)
- tmikew 17y agoI agree that the effort is large, and the browser platforms are constantly in motion. I was mostly just musing about it. My gut feeling is that getting Java script up to speed on the server side is just as much if not more work. Look at how much work has gone into the tools just for Java for example. Years. Before I get flamed, I will say that I am not bothered at all that some folks are willing to take up the effort to do it anyway. That is how things get done. I am just wondering about it.
- boucher 17y agoDisagree. Every month we're seeing a new "X to JavaScript" compiler, and increasingly they are being written natively in JavaScript.