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 working with a command line one wants npm or any command to run as quickly as possible. Any graphics that slow operation of the command should be an opt-in, not an opt-out.

Everyone is entitled to their opinion, but some people prefer to suppress others' opinion.

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 connected to - of course - Sybase. It felt like I travelled back in time.

Old code never dies.

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.

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.

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 reasonably expect such a large merge to work flawlessly out of the gate. Even the IBM PowerPC port of the V8 engine took many months to stabilize - and it's the same v8 engine.

>>> 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 have just one common code base you also have a common set of bugs. Competition is a great way to raise the bar and try out radically different design approaches. Take GCC and LLVM for example - who can argue that friendly competition hasn't helped them both immeasurably? Link Time Optimization, C++14 compliance - choice is a good thing.

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?