Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Another I left <dynamic language> for <strong typed language> when faced with performance/large codebase/tooling issues post.

Additionally we are now past Rails wave, Node.js wave and into Go wave.



> Additionally we are now past Rails wave, Node.js wave and into Go wave.

And the narrative is similar as well: starting a new project with the shiny new thing is cool but maintaining it is boring and awful and to quote the OP "I need maintainers!".

Part of the problem is the language of course. Maintaining even a medium sized codebase written in a dynamic language is a challenge. But the other part is the mantra that "coding is easy" and "everyone should do it". And now there's an entire generation of developers whose idea of software development is "writing an app in Node in a weekend". Which of course doesn't require years of maintenance, complicated tooling or even adherence to common best practice.


Erm. If you meant "static", not "strong", then Go is as statically typed as, say, C - fine in theory, but not so much in real world practice.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: