The article is aimed at less experienced developers. The issue with most tutorials is there is a lot of assumed knowledge, which may pose a challenge for less experienced devs. Being popular means that a developer has a higher chance of working with it, so that is the relevance for me writing about it. I was teaching Java recently and I had this conversation with other devs, we decided to introduce Spring as a framework to them for this reason. I may post about different frameworks in the future and that may be of more interest to you
Looked more carefully into article and found it really disappointing. The code which most likely beginners will be following in their applications contains a number of significant issues:
Using mutable POJO for storing users is a poor habit
Using non-synchronized collection for storing data which can be accessed concurrently will result to unpredictable behavior
Modifying collection while iterating over it is a poor habit
No input validation for REST methods
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.
The article is aimed at less experienced developers. The issue with most tutorials is there is a lot of assumed knowledge, which may pose a challenge for less experienced devs. Being popular means that a developer has a higher chance of working with it, so that is the relevance for me writing about it. I was teaching Java recently and I had this conversation with other devs, we decided to introduce Spring as a framework to them for this reason. I may post about different frameworks in the future and that may be of more interest to you
Looked more carefully into article and found it really disappointing. The code which most likely beginners will be following in their applications contains a number of significant issues: