Skip to content

Comment on What is wrong with GWT.parent

Comments

Javascript is interpreted.

No, it's JIT compiled, at least in any recent browser or in Node.JS.

Which actually highlights my point that languages (of any level) have usually be designed to solve a particular set of problems or targetted for a particular type of runtime environment.

But what if you have a problem that fits Java much better than JS, but you just need to distribute the client through the browser?

Actually, I think your last sentance exactly highlights my point (I dont know how to do that italicy/quote thing).

Whether you choose to write your code in Java or Javascript doesn't matter because it will HAVE to be run in a Javasript environment (browser) so you will always be limited to the target language - Java allows you to connect to databases with JDBC, read/write files and create rich user interfaces - none of these language features can be used by javascript in a browser.

So solving a problem that is more appropriate for Java can never be a problem that needs to be solved inside a browser by javascript...

You are mixing up the languages with the platforms.

Java doesn't let you connect to databases or any of that - the JVM does, and for any language running on it (Scala, Clojure, etc).

Java the language just gives you a certain set of syntax and semantics which can be useful to model a problem and its solution - classes, interfaces, etc.

Even if you're limited by the API of the platform - the browser - that has nothing to do with whether a different language is useful or not for your particular problem.

(I dont know how to do that italicy/quote thing).

Enclose the quoted phrase in asterixes...

thanks!

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.