4 ms·
I did the same as you, and my experience couldn't have been more different. It was tremendously freeing to escape the whole .NET framework that came with C#. M
by untog 10y ago
I did the same as you, and my experience couldn't have been more different. It was tremendously freeing to escape the whole .NET framework that came with C#.
My view is that you're always more productive in the language you know better. I find things like being able to use functions as variables tremendously useful in JS. Not to mention the ability to share code between the back and front end of a webapp.
- rjbwork 10y ago>I find things like being able to use functions as variables tremendously useful in JS A thing in C# for 9 years now. > Not to mention the ability to share code between the back and front end of a webapp Technically possible if you care to do so, but TypeScript + a framework with bindings should be good enough on the front end to not have to completely tear down your conception of what you're doing when you move from front to back.
- blakecaldwell 10y agoWouldn't you agree that a compiled language is typically much easier to maintain than an interpreted one (refactoring, etc). Also, it's been years since I've worked in C#, but I would imagine you could stay in the language but ditch the frameworks.
- rjbwork 10y agoIt's not interpreted vs compiled, it's static/strong vs dynamic/weak. These just usually happen to fall along the interpreted vs compiled dichotomy. But, for instance, IronPython and IronRuby are compiled, yet dynamic, and GHCi is a Haskell interpreter that runs an extremely strong/static language.