Viewing profile — morebetterer

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.

Thank goodness we have you and others to police the jokes. Remain vigilant! Keep up the good work.

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…

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 b…

No, never had a need for it.

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!

"Catered to", "dissuade", "push that choice" and "insanity"? Now this is just getting silly. You are taking my comments far too seriously.

> Not everyone is you. Never claimed that was the case. God speed with your colors. May they bring you fame and good fortune.

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.

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.

What about: * sqlite3 amalgamation: https://www.sqlite.org/download.html * duktape javascript interpreter: http://duktape.org

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 pa…

>>> 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…

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?

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, …

Keep in mind that native modules coded against NAN1 do not work with NAN2. Not sure about forward compatibility of NAN.

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 …

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 engin…

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…

That thread doesn't show a lot of promise towards an engine neutral API.

I see Chakra has caught to up Dec 30, 2015 with the nodejs tree. Which branch are you basing the fork against?

Any progress in talks with Node.JS to make an implementation independent JS engine API for node?

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 intere…

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 l…