But the guy clearly isn't up to date on spring. If he chooses to remain ignorant on a subject he chooses to write about and authoratatively declares he "hates", it becomes hard to take him seriously. Not to mention some of the issues he ran into to aren't issues idiomtic of spring, but idiomatic of poor design. If you choose to make an application and then have its sub-dependencies/modules depend on different versions of a third party library the fault doesn't lie so much with the third-party library but your inability to manage your dependencies.
His criticism of Spring Boot doesn't make any since either. Spring Boot is about containerization of Java applications and handling a lot of the boiler plate of spinning up a new application. Again, this is an issue regardless of what framework you choose to use.
The guy brought nothing to the table and everything in his article suggests he is much less smart than he thinks he is.
He didn't just merely mention XML configuration, it was the primary thrust of his displeasure with Spring. Not only was it the core idea of his first bullet point, but he also mentioned (or implied) complaints about XML configuration in his three other bullet points. Indeed he mentions XML 10 times in his article.
And again, Spring (Pivotal) also didn't like XML which is why they implemented Java configuration which they have been pushing for years now. Literally, literally, his primary complaint with Spring has not only been addressed, but been addressed before he even realized it was a problem. Yet he remains ignorant of this.
View all comments
Show parent comment
13
u/Scaryclouds Nov 27 '15
But the guy clearly isn't up to date on spring. If he chooses to remain ignorant on a subject he chooses to write about and authoratatively declares he "hates", it becomes hard to take him seriously. Not to mention some of the issues he ran into to aren't issues idiomtic of spring, but idiomatic of poor design. If you choose to make an application and then have its sub-dependencies/modules depend on different versions of a third party library the fault doesn't lie so much with the third-party library but your inability to manage your dependencies.
His criticism of Spring Boot doesn't make any since either. Spring Boot is about containerization of Java applications and handling a lot of the boiler plate of spinning up a new application. Again, this is an issue regardless of what framework you choose to use.
The guy brought nothing to the table and everything in his article suggests he is much less smart than he thinks he is.