Echo JS 0.11.0

<3 Ramda.

So... they've changed their tune almost completely. JXCore began life as an ambitious project to create a multithreaded/multicore variant of NodeJS by employing multiple V8 instances to run an app (as I understood it). Now it's on SpiderMonkey and they're downplaying the threading in favour of a cross platform app runtime sales pitch. The open source edition of this probably resembles the beta very little as they're now two distinct platforms. That renders me curious as to why they kept the name.

This is awesome.

Hello! So sorry I didn't write back. And thank you lordhanson - I didn't know that, but it makes perfect sense. To answer your question, coffee:

a) I did, yes, as statically typed code is much easier to reason about. TypeScript is naturally a little more verbose than plain JavaScript, but what it lacks in brevity it more than makes up for with clarity.

b) Nope, no problems; I use Browserify a lot so tsify was a natural choice of tooling for me. But there are many options available to support whatever you're using to compile modules.

I may well end up using TS exclusively going forward, especially due to the quality of code produced using TS + ES6. It's a Microsoft-backed project and seems it's around to stay, so my conclusion is that it's well worth taking it up if it piques your curiosity sufficiently after one or two tries.

Admittedly I haven't used it much, but it strikes me as a superset of JavaScript for C# developers and a slight rehash of JScript. This should be no surprise, as it is a Microsoft initiative and doubtless enables .net developers to achieve a higher level of full stack productivity.

While its compatibility with Visual Studio's debugger is excellent and it can in theory output highly performant JS, I have to say that, having myself approached C# only after JS, and having a better knowledge of JS than the former, I don't really see the point in writing typesafe code that's eventually transpiled for a non-typesafe interpreter.

Been loving the lean approach using Vue.js, collections.js, page.js and good plain old JS to cover all bases in a loosely coupled manner. I think Vue may have been developed in response to Angular's quirks.

Good one, thank you! I'm a bit wary of replacing anything in Node's Module.prototype. Might build a quick need() [or something] fork.

Interesting experiment.