I could not agree more with this article. The attitude of "don't even try, there is a solution out there already" is frustrating at best and infuriating at worst, but misses the point 99% of the time. I do write spring-based Java severs. I do use Jackson, Hibernate, Logback, you name it. But I am also writing a custom graph database. It can do things which are not provided by any other graph DB, and only in a limited fashion by the most expensive of commercial SQL databases. And yet... I keep hearing the same darn question over and over and OVER again: "Why didn't you use X, it already has feature Y!" Except that, of course, it always turns out that X doesn't support Y nearly as much as necessary. When it comes to seeing somebody else writing innovative software, suddenly everyone turns into an expert in everything and is pointing fingers.
So yes, there are very valid reasons for re-inventing the wheel.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I could not agree more with this article. The attitude of "don't even try, there is a solution out there already" is frustrating at best and infuriating at worst, but misses the point 99% of the time. I do write spring-based Java severs. I do use Jackson, Hibernate, Logback, you name it. But I am also writing a custom graph database. It can do things which are not provided by any other graph DB, and only in a limited fashion by the most expensive of commercial SQL databases. And yet... I keep hearing the same darn question over and over and OVER again: "Why didn't you use X, it already has feature Y!" Except that, of course, it always turns out that X doesn't support Y nearly as much as necessary. When it comes to seeing somebody else writing innovative software, suddenly everyone turns into an expert in everything and is pointing fingers.
So yes, there are very valid reasons for re-inventing the wheel.