Every year we’re throwing more and more JS on top of the web, dooming our best intended semantic thoughts to suffocation in the Turing tar pit. JS libraries are the “fuck it, we’ll do it live!” of the web.
Still waiting for someone to invent the thing that lets you write server-side code and client-side code in the same language in the same file, and magically handles the execution of what where (and the secure transmission of stuff between the two) on the server.
I can imagine something like Parse where in addition to sending them data and stuff to store, you can send them a block of code to run on the server. They would of course cache compiled versions of those blocks for speed, but the idea of blocks (as in Obj-C) is an attractive one.
Check out nowjs[1]. It's not quite what you want, but I think it's in the same spirit. I haven't used it personally, but I've heard only good things about it.
I'm not sure that it lets you share code between sever and client entirely seamlessly (it might--I honestly don't know), but it has another advantage: it lets you share objects between different clients seamlessly.
I'm working on such a thing during my free time, it's very interesting and I don't understand why nobody implemented this idea, but there are frameworks which do it, like vaadin for Java (it generates JavaScript through GWT )
I would be very pleased to hear from people who would be interested in such a language - what features they will want from it.
Still waiting for someone to invent the thing that lets you write server-side code and client-side code in the same language in the same file, and magically handles the execution of what where (and the secure transmission of stuff between the two) on the server.
I can imagine something like Parse where in addition to sending them data and stuff to store, you can send them a block of code to run on the server. They would of course cache compiled versions of those blocks for speed, but the idea of blocks (as in Obj-C) is an attractive one.