4 ms·
I’m sorry but I guess I’m still missing the point. How is it not productive? It takes me a few seconds to get a REST API going.
by dimgl 8y ago
I’m sorry but I guess I’m still missing the point. How is it not productive? It takes me a few seconds to get a REST API going.
- manigandham 8y agoIt's not as productive. Anyone can create a REST API in any language in a few minutes, that's the easy part. Building a complex app is different though and much easier and faster in a proper environment that has strong typing, OOP, interfaces, reflection, dependency injection, a solid standard library, and more. Being able to use that same environment to create frontend views and code will greatly improve productivity compared to the current Javascript frameworks and limitations.
- dimgl 8y agoYeah sorry, I really don't buy it. Strong typing is admittedly great and there are solutions to introduce that in JavaScript. However, this is hardly a dealbreaker in complex apps written in JavaScript. OOP, interfaces: debatable and unnecessary fluff. There are plenty of productive languages without OOP. Example: Elixir. And there are plenty of productive languages without interfaces. Example: Go. Reflection is unnecessary in JavaScript. You can access any property within an object dynamically and the language is interpreted, so there's no need to perform fancy reflection operations at runtime. Dependency injection is an engineering pattern. You can apply this to almost any language. And ironically, plenty of JavaScript backend and frontend frameworks have attempted to use it successfully: Angular, Ember. Hell I even wrote my own DI layer once upon a time. https://github.com/divmgl/nwire https://github.com/divmgl/nwire I'm sorry, I really disagree with you. I believe C# has the ability to be productive, but there is just no way you're going to convince me that it's superior to JavaScript and its ecosystem. There's a lot of disdain on Hacker News for JavaScript and it's honestly beyond me.
- dimgl 8y agoCorrection: I recently learned that Go has interfaces. But my point still stands.