So, is no one else nervous about the fact that Oracle owns the trademark "JavaScript", acquired along with Sun. If they develop a JavaScript implementation it gives them grounds to "defend the mark".
-Rick On Thursday, October 4, 2012 at 11:52 PM, Jonathan Buchanan wrote: > There's been an interesting thread I've been following throughout this (my > first) JavaOne of "polyglot" - pretty much: "Java the language is way, waaay > far from perfect: use whatever JVM language best suits the job/domain at > hand." Obviously, there's been that "on the JVM" bent, but the message > dynamic language guys have been selling is: "if you need middleware which > already exists in a Java EE app server and there's a wrapper for <favourite > dynamic language>, just *use* the <favourite dynamic language> wrapper." > Other talks have gone further and pretty much said: "look: when you need to > scale, just use whatever's best at the task at hand, doesn't matter what it's > written in/runs on," at which many mental high-fives were given by myself and > a a certain amount of confuzzled questions were asked. > > The JRuby guys are way ahead on this front: Charles Nutter has had a bunch of > great talks here, and from listening to the Oracle & JVM guys it sounds like > he's been a key driver as an initial user of the JVM-specific details > (invokeDynamic). He and Tom Enebo (another JRuby guy) had a packed talk where > they did a great job of sellling dynamic languages in general and for > build/testing tools in particular as an entry point. Given that Oracle have > people working on a more efficient JavaScript implementation than what's > standard in Java-land, and that they're working on a Node API implementation > (a talk today about implementation details such as > https://github.com/szegedi/dynalink was a programmer geeking-out-fest, as > someone who's been stuck in webapps-land for too long), I guess this just is > a bit of a heads-up. > > (I should point out, FWIW, that I use (server-side) JavaScript and Python > almost exclusively in my free time and Java/JVM/enterprisey stuff almost > exclusively at work, so I'm currently a bit stoked (and drunk on free > alcolhol, and overwhelmed by SF partially due to the former) about having > attended days of talks which merge stuff I'm interested in personally and > stuff I *have* to be interested in professionally) > > Thanks, > Jonny. > > On 4 October 2012 19:05, Ben Noordhuis <[email protected] > (mailto:[email protected])> wrote: > > On Thu, Oct 4, 2012 at 7:16 PM, Jonathan Buchanan > > <[email protected] (mailto:[email protected])> wrote: > > > I'm at JavaOne, for my sins, and I've been attending all the sessions > > > related to Oracle's new JavaScript implementation in Java, called Nashorn. > > > > > > What initially caught my eye was that they're also porting the Node.js > > > APIs, > > > module system etc. in a project called Node.jar. Nashorn itself is going > > > to > > > be open-source, but it sounds like it's hard to get a hold of Node.jar > > > even > > > if you work for Oracle, and there are no plans to open-source Node.jar, > > > but > > > it could be another deployment option in the future and another way to get > > > at multi-threading. > > > > > > These are what I can decipher from my scribbled notes: > > > > > > https://insin-notes.readthedocs.org/en/latest/JavaOne2012/meet_nashorn_bof.html > > > https://insin-notes.readthedocs.org/en/latest/JavaOne2012/nashorn_node_jpa_persistence_bof.html > > > > > > > They at pains to point out they hadn't looked at any other implementations > > > to keep the JavaScript engine "pure", but it sounds like the Node port is > > > trying to reuse as much of the Node JS libs as possible and Node's tests. > > > > > > Has the Node dev team been involved with or consulted about any of this > > > stuff? > > > > Very interesting, thanks for posting that. And no, we've not been > > consulted. :-) > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
