This strikes me as the sort of shitty compatibility fragmentation that browsers suffer from. What happens when "node.jar" falls behind in supporting new features? Bug fixes?
-Rick On Monday, October 8, 2012 at 9:03 PM, Ben Noordhuis wrote: > On Tue, Oct 9, 2012 at 2:21 AM, Stewart Mckinney <[email protected]> wrote: > > I'm just curious as to why having Node run on top of the Java run time is > > better than say, vanilla C++ compiled Node running naively. Doesn't it run > > on pretty much every popular platform now, anyway? > > > > > The major ones, yes. But there are some high margin, low volume > architectures like POWER and S/390 that V8 doesn't support (and hence > node.js) but the JVM does. Think AIX, mainframes, etc. > > There has been some corporate interest in running node on such > architectures but the time and money to get (and keep) it ported isn't > worth it. node.jar could be a viable alternative. > > -- > 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
