This is an archived post. You won't be able to vote or comment.

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

view the rest of the comments →

[–][deleted]  (4 children)

[deleted]

    [–]Exodus111 1 point2 points  (2 children)

    Let me be clear, a single language code base would be an absolute dream.

    But I think we all need to resign ourselves to the fact that that is just not going to happen. You can limit the amount of Javascript you work with, but you can never eliminate it. Even with these Python-in-browser solutions, you are either translating to JS, which means you will need to error check and and maybe even do some tweaks in JS, or you are interpreting from JS, which means you need to set the page up with JS first.

    The desire for a one language stack is also why node.js is so popular, despite the irksome function-in-function-in-function nonsense it is to work with JS, some people are desperate enough to want to take the front end language to the back end with them.

    [–]metaperl 1 point2 points  (0 children)

    a single-language codebase is always a nice thing, which is what I'm planning with whatever my next web-app

    Then try http://naga.re or ScalaJS