Re:Ask HN: “What JavaScript API/Framework should I use to de...
by nippur72 on Friday October 07, 2016 @08:11AM
(#12659975)
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.
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.