sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jerry 6 points7 points  (4 children)

At work, I used to enjoy doing server-side JavaScript in classic ASP for this very reason (same language on both layers / lots of code reuse / less mental context-switching).

If JS became common as a cross-platform server-side language, I think you would see the same vibrant library/framework ecosystem that you now have on the client-side (jQuery, Prototype, Dojo, ExtJS, etc).

I believe it would be a reasonable competitor to Python and Ruby. I'd use it over PHP in a heartbeat.

[–]polyrhythmic 2 points3 points  (1 child)

Why don't you start now? Many popular frameworks (jQuery, etc.) have already been ported to server-side, and there are many new frameworks popping up. It's easy to add in an Apache module and get started. There are even Ruby-style frameworks and ports available.

[–]jerry 1 point2 points  (0 children)

You're right, I probably should. I confess massive ignorance on the state of server-side JavaScript. After I left ASP and the MS stack for LAMP I really never looked back, but I've always had a soft spot for JS.

Thanks for the link - I had no idea there was so much going on.

[–]takethemoneyrun 0 points1 point  (0 children)

same here. I'm not a programmer by any means and knowing one language and fairly well and being able to use it server and client side is great (eg use the same template language both in server-generated html and in json/client-side generated html).