Production quality of applications made with Node.JS, GO and ASP.NET -
tj holowaychuk in blog starts pain using node.js apps in production. in blog, same pain detailed, , using set of libraries overcome that.
is there statistics on 1 of these node.js, go, asp.net apps developed in c# more stable in production environment?
i remember reading book long time ago entitled "code complete". it's 1 of few i've read include copious amounts of statistics related quality. couldn't tell whether or not latest revision includes of "new new" things node, example.
i'm long-time coder , have worked on big (expensive) microsoft-related programming projects. on last year i've converted on node. it's difficult quantify quality-versus-code, honest. i'm left sense of faster development project span. acknowledge fair amount of i'm bundling isn't code case before. in past, though, microsoft author of "unknown" code. , now, it's collection of authors , dependency tree odd me--a project might have several different versions of same module in it. inherently better or worse result?
at unit (module) level it's healthier each component manage dependencies. , yet when "npm install ..." i'm grabbing snapshot in time. module author continue work on code , may or may not revisit collective versions of own dependencies.
on platform microsoft presumably recipient might run update once in while. don't believe there's of sort dependency tree average node project. strikes me sort of "update debt" incurred everyone.
i can't have enough experience go comment on that.
Comments
Post a Comment