4 ms·
Yes there are niches where Ruby won't work, even big niches like Kernel development or real time systems maybe. But for web development, in general, these langu
by joelbluminator 6y ago
Yes there are niches where Ruby won't work, even big niches like Kernel development or real time systems maybe.
But for web development, in general, these languages have proven themselves for so long it's getting quite ridiculous now to say they won't work.
As for testing - I disagree. Frameworks like Rails are so easily testable it's a breeze. Java/Spring dependency injection is jumping through hoops just to provide a testable framework I find it hard to believe it's any easier.
- jimbokun 6y ago> But for web development, in general, these languages have proven themselves for so long it's getting quite ridiculous now to say they won't work. And I don't think web development is where Go is getting traction. More in back end services and infrastructure. > Java/Spring dependency injection is jumping through hoops just to provide a testable framework I find it hard to believe it's any easier. As someone who develops with Spring everyday, I don't think it's the best solution for anything.
- joelbluminator 6y agoWhat are your main pain points with Spring?
- jimbokun 6y agoAnnotation oriented programming. Having the code execution paths radically change by adding an annotation to a method or a class makes it very difficult to reason about what it will do when deployed. If that annotation you found through Google does what you want and expect, that's great. But if it doesn't, or fails in unexpected ways, debugging it can be a nightmare.
- joelbluminator 6y agoIts interesting that a java framework is so "magical", feels like it goes against the java mindset I know.
- jimbokun 6y agoYes, that's what makes it so terrible. All of the "action at a distance" complexity of Ruby meta-programming, with none of the concise and easy to read code!
- cmrdporcupine 6y agoThis always baffled me -- when Guava came on the scene, and when Spring also adopted annotations... The whole original point of dependency injection was to decouple dependency management from the code, to make it easier to test, and easier to reason about and analyze. DI via annotations goes ahead and sticks them right back in there. And now we have, like you say, magic code that is difficult to reasona bout. XML sucked, but annotations sucked more.
- cmrdporcupine 6y agoYes, I don't do web development. At least not mostly. But I understand that that's what most people out there are doing. But they should also not delude theirselves that the toolsets appropriate for that environment are appropriate every where else. I see this bias a lot, on HN even, that everyone now is a "full stack developer" doing this kind of development. Many of us work in entirely different stacks.