pyre · HackerTrans

14 lat temudiscuss

You feel special because you're in an 'elite' club of people that know what the noprocrast setting does?

14 lat temudiscuss

  > thought they knew what they were doing (YES, behaving
  > God like!),

In my book, there is a significant difference between 'playing like God' and 'thinking that you know what you are doing.' I'm thinking that you left out some detail here, otherwise this just comes off as bitterness because someone that thought they were doing the right thing turned out to be wrong.

pyre

16 lat temudiscuss

I'm not talking about pulling C libraries into the browser. I'm talking about expanding the use of the JavaScript language outside of the browser (beyond even something like Node.js).

Unless I'm completely misunderstanding NativeClient, that's not what it's about.

pyre

16 lat temudiscuss

It's probably less to do with a bytecode 'standard' vs. a set of standard libraries for doing things outside of the browser (file manipulations, etc). Then browsers could just not support those libraries, but JavaScript VM developers could. In this way, it would be possible to not have 'the future of JavaScript' tied down to a specific bytecode implementation. Then people could pick and choose the VM that they want to run their JS in based on what sort of optimizations they needed.

One of the largest requirements here would probably be a method of linking against/using C libraries, and also a standard for 'import/#include/etc' statements.

Maybe I'm being naive here though. Feel free to correct me.

comments