morebetterer

6 ms·

1.
by morebetterer 11y ago
I like the proposal. It took me 20 years to master the 10% of C++ I understand and use. I wonder how new programmers will be able to pick up this language.
2.
by morebetterer 11y ago
Thank goodness we have you and others to police the jokes. Remain vigilant! Keep up the good work.
3.
by morebetterer 11y ago
I was asked a question and provided an answer. So I don't care for syntax highlighting or colors in my editor and command line - big deal. I am not imposing my view on others. When working with a command line one wants npm or any comma
4.
by morebetterer 11y ago
I bet it was. Well done. A couple of years ago I was just about to throw out all my O'Reilly X Window/Motif books from 20 years ago and when I landed a contract to update a K&R C based Motif system running on 32-bit Solaris co
5.
by morebetterer 11y ago
No, never had a need for it.
6.
by morebetterer 11y ago
I have a soft spot for those short-lived X-terminals as well. The golden age of computing. Colors are great for web browsing, don't get me wrong. Just not near my code!
7.
by morebetterer 11y ago
"Catered to", "dissuade", "push that choice" and "insanity"? Now this is just getting silly. You are taking my comments far too seriously.
8.
by morebetterer 11y ago
I don't even want color and terminal graphics done goodly. I code with two monochrome terminals on the screen using vim and the command line.
9.
by morebetterer 11y ago
Upon first seeing npm 3.x I immediately added `--progress false --color false` to my npm installs and never looked back. Color and terminal graphics are the work of the devil.
10.
by morebetterer 11y ago
What about: * sqlite3 amalgamation: https://www.sqlite.org/download.html * duktape javascript interpreter: http://duktape.org
11.
Node.js Foundation Core Technical Committee Meeting on Chakra(docs.google.com)
7 points by morebetterer 11y ago|0 comments
12.
by morebetterer 11y ago
If it's a compile-time switch to build v8 or Chakra and it's not impeding Node development, there's no harm. Node is a large code base. The Chakra merge will eventually work and pass all tests - give it some time. One cannot
13.
by morebetterer 11y ago
>>> I don't believe the web is stronger with more rendering engines and more JS runtimes... I think it's weaker I disagree. I'm happy to see numerous JS engine implementations that embrace a common standard. If you h
14.
by morebetterer 11y ago
As long as each JS engine uses the same API (at this point V8's C++ API, hopefully something engine neutral later) what difference does it make?
15.
by morebetterer 11y ago
Many posters in that Github Chakra pull request thread appear to be in the "Node is V8 and only V8" camp. This is disappointing. Since when is having a bigger developer community, supporting the latest ES6 standards, and having wi
16.
by morebetterer 11y ago
Keep in mind that native modules coded against NAN1 do not work with NAN2. Not sure about forward compatibility of NAN.
17.
by morebetterer 11y ago
The Node fork JXCore supports Chakra, SpiderMonkey and V8 right now. It's pretty fast, probably because it's based on a pre-0.12 node fork when node was known to be faster than it is presently. https://github.com/j
18.
by morebetterer 11y ago
I hope the V8 C++ API doesn't become the defacto Node engine API. Node really needs a proper engine-neutral API. This way the native node modules can truly be portable across engines and across node versions. Supporting additional JS e
19.
by morebetterer 11y ago
The state of documentation of Express 4 is not great. You have to look at the source code to see how it really works most times, or read someone's blog about how it used to work in Express 3 - but no longer does. Whose decision was i
20.
by morebetterer 11y ago
That thread doesn't show a lot of promise towards an engine neutral API.
21.
by morebetterer 11y ago
I see Chakra has caught to up Dec 30, 2015 with the nodejs tree. Which branch are you basing the fork against?
22.
by morebetterer 11y ago
Any progress in talks with Node.JS to make an implementation independent JS engine API for node?
23.
by morebetterer 11y ago
Ironically Microsoft had to create a V8 C++ API facade over Chakra in order for Node to compile with it. https://github.com/Microsoft/node/tree/chnext/deps/chakrashi... It's interesting that th
24.
by morebetterer 11y ago
Constantly being interrupted to answer simple questions is a thankless task that has negative consequences to your own productivity. You ultimately have to do their work and have less time for your own, which can be stressful when on projec
25.
by morebetterer 11y ago
Isn't it possible to create multiple asm.js memory arenas?
26.
by morebetterer 11y ago
Aside from a few game demos, is anyone using asm.js in production systems?
27.
by morebetterer 11y ago
Good stuff. Looking forward to the neutral binding layer for different javascript engines for Node. Ideally for a given platform a native Node module should be ABI compatible with v8 Node or Chakra node - without the need for recompilation.
28.
by morebetterer 11y ago
I am fully aware of that. I had to port orphaned NAN1 code to the new v8 API which I found easier to work with than NAN2.
29.
by morebetterer 11y ago
Are you aware that NAN2's API is incompatible with NAN1's API? How is that backwards compatible?
30.
by morebetterer 11y ago
It would be very interesting if you could share your team's challenges and insights in creating a Chakra shim that exactly mirrors v8's C++ API so that it's a drop in replacement for v8 for Node. Is it difficult to maintain

More ›