4 ms·
I have migrated from C# to Node.js, my code is now 20x times shorter (from 800 files to 40 files), simpler to read and maintain, there is 100x more packages ava
by js4ever 6y ago
I have migrated from C# to Node.js, my code is now 20x times shorter (from 800 files to 40 files), simpler to read and maintain, there is 100x more packages available on NPM compared to nuget. Performance is stellar, even better than in C# for my use case (Mega tons of concurrent queries executed in 1-5ms avg)
And also I don't have to fight against the language to do what I want to do ... No classes, no types, no constraints.
- tester756 6y ago>20x times shorter that's giant, but I don't think that "just" language / environment difference makes this huge difference
- Scarbutt 6y agoI would say 2x-5x shorter is pretty realistic.
- balfirevic 6y agoI would say that that C# code that can get 2x-5x reduction in size by being rewritten in JS is terribly bloated (not taking into account the case where you just remove code because there is now a library available for what you had to do yourself before).
- merb 6y agoyeah javascript is pretty short. unfortunatly I do not know how people love it. npm/yarn and javascript dependency management is the worst thing i've ever seen and it is slow and pulls in millions of files, just for a small project.
- ArtifTh 6y agoHuh, that's quite a dramatic code size reduction. Which percentage of this codebase was in tests and boilerplate code for stuff like helper data classes?
- littlecranky67 6y agoEvery rewrite yields better results, even if you'd have rewritten your code in (modern) C# again.
- Xevi 6y ago> my code is now 20x times shorter (from 800 files to 40 files) Well, do you have all of the bells an whistles that you had with .NET? I mean, you can shrink a .NET API down to pretty much just 1 file if you really want to. The question is if you should. WebHost.CreateDefaultBuilder().Configure(app => app.Run(c => c.Response.WriteAsync("Hello world!"))).Build().Run();