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.
12 karma · joined July 3, 2015
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.
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.
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()