rando231
Learning Java should force you to understand object oriented design, as it is hard to do anything well in Java without it (though some try). While there are signs that OO's domination is nearing an end, there are reams of code out there that require a good understanding of it.
Edit: To clarify, I also don't agree with 'proof' of Spring being 'low quality'. In my experience most who criticize Spring don't understand that it is a loosely coupled collection of things implemented on top of IoC/AOP, and are frustrated when they are forced to diagnose things that go wrong. From the beginning, Spring moved fast because it wasn't bogged down in committee, and it covers huge portions of software development. Quality does vary between the value add sub-projects, but it's amazing what the Spring community has done with IoC/AOP.
Exponential growth of cases and deaths translate into many horrible anecdotes.
It would be interesting to see geographic case density vs. geographic ventilator capacity.
Such a brilliant system.
I was under the impression that HTTP/2 used a persistent connection w/ multiplexing. This seems like it would be very nice in a web-browser to front-end situation, but what about for internal service calls? Seems like persistent connection between services would mess w/ common load balancing schemes.
This maintainer actively ceded control of his library to some random person.