3 ms·
My current stack: - Server: Node & express - DB: Mongo (using mongoose) - Frontend: Knockout.js using components (introduced in 3.2), Cordova when developing
by iEchoic 12y ago
My current stack:
- Server: Node & express
- DB: Mongo (using mongoose)
- Frontend: Knockout.js using components (introduced in 3.2), Cordova when developing mobile.
- Hosting (db, services): Azure
Pretty standard with the exception of Knockout.js, which I think is criminally underrated following the introduction of components in 3.2, especially given all the recent hype around component/module based separation of concerns. Also Azure, mostly because I get $150 free monthly from MSDN.
- itsbits 12y agoknockoutjs is something i loved to code. Althgh its long time now when I had a look. Does that still fire all bindings together?
- iEchoic 12y agoIf it's been a long time, you should definitely take a look again at components, which really feel like the thing knockout has always been missing. All bindings are still fired upon applyBindings, but I haven't encountered issues here - it's still once on page load, and I can't imagine that it's much different than building the DOM initially using handlebars or react.
- itsbits 12y agoI would surely make time for KnockoutJS. But currently I have been following flux which is quite easy to implement althgh I am still not sure how it works with routing, 3rd party libs like some charts etc.