2 ms·
Javascript still doesn't have 64-bit numbers or real multithreading or serious async or proper namespaces and modules. C# the language is also not the same as
by manigandham 8y ago
Javascript still doesn't have 64-bit numbers or real multithreading or serious async or proper namespaces and modules.
C# the language is also not the same as the .NET runtime and framework, but Microsoft is the best organization in the world when it comes to backwards compatibility and the C# code you wrote a decade ago will still work flawlessly today.
I don't understand how you're switching to Node.js and shell scripts(?!) to take over all that functionality.
- eksemplar 8y agoNode.js is better at web apps, and for us it’s been much faster to get stuff out too. The ability to quickly prototype is instrumental when you’re doing service design, and node excels at that. SSIS is better at moving data. Powershell has come really far, it’s certainly not C#, but where it really excels is when it’s integrated into our Azure orchestra giving us faster error reporting and making us capable of addressing those errors quicker. It’s also a language that’s shared between developing and operations. So while C# is better technically, powershell is better organizational and that means it’s better. Simply put C# has become an unnecessary burden, in our setup. I’m not sure I’d use node for huge projects, but our backends are mostly simple frameworks for manipulating relatively small amounts of data. We’re not leaving .Net or Microsoft, our node server runs behind an IIS with IIS node. SSIS, powershell and Azure are obviously Microsoft. Our entire security model is based around AD and ADFS.