yes it's a rabbit hole, I know it well! When PC became fast enough to be used as DSP engines with the soundcard I spent years playing with the creation of "digital modes" as HAM radio hobbyist.

down it Italy as well

> Programmers with lots of hours of maintaining code eventually evolve to return early

indeed I've evolved it myself but always wondering if it was the right thing to do. Now I even have a name for it.

I've written a large .NET SPA application and I feel very comfortable with the following technologies:

On the client: - TypeScript as language (v2.1 for ES5 async/await), strict null checks enabled - VS2015CE or VSCODE as IDE - React for rendering the UI - React-Templates for compiling HTML templates into pure React - React-router for routing - Webpack as module bundler, compiles in background (-w switch)

On the server: - IIS/.NET, limited only to serving the main .html page and to reply REST api (C#). - SQL Server as database engine

Everything is fine and debugging is smooth from Visual Studio. The only impedance mismatch is between server language (C#) and client (TypeScript). I once tried to switch to node.js but the SQL Server support was poor.

before typescript@next I had exactlt that setup, but sourcemaps were broken despite all my attempts to make them work. Now I'm using ts 2.1 and have completely removed babel out of my build.

nice small lib as you'd expect from @gianlucaguarini (of Riot.js fame).

Also, it's async/await ready:

  const allora = require('allora')
  const myGlobal = allora(global)
  
  async function foo() {
     console.log("start")
     await myGlobal.setTimeout(2000)
     console.log("end")
  }  

  foo()

thanks it's very useful, as I now I doubt async/await will ever land in TS.

is this server protocol also responsible for syntax highlight (aka colorization) of the source code?

I've just opened the GitHub repo and I see no trace of TypeScript, no .ts files anywhere

Wrong branch. Check 0.8-dev: https://github.com/trueadm/inferno/tree/0.8-dev/src

fine, thanks. TypeScript makes it even more interesting. I am going to make some tests to see if Inferno can replace React when working with react-templates.