![]() The thing that really bothers me about this is the tone. Perhaps there was more at some point? Who knows? But the subclass seems to be used in the Spring AOP stuff. ![]() I had a quick look and found only one use for this: CacheProxyFactoryBean. ![]() If anything, it's probably poor text from someone who isn't a native English speaker.Īs for the layering, it's nit-picking. ![]() It may not have invented DI/IoC but it certainly popularized it.īut long class names? Really? Is that all you've got? Who cares?ĮDIT: I don't care about the description either. Java at that time really was a hotbed for innovation (believe it or not). Jetbrains seems to be going out of their way to make it hard Īnd as far as Spring goes, it's probably long in the tooth now but people either forget or never knew just how influential Spring was in the early 2000s. IntelliJ is but for some reason they insist on making it hard to make plugins as their API changes every major version. And, no, for Java at least, vim/emacs simply are no better. No function references, lambdas, etc (still a year+ away) Type erasure in generics and the consequences thereof (eg inability to create generics of primitive types unlike C#) Something as simple as wanting symbolic links in a Maven build requires a third party plugin, last updated in 2007 (maven-junction-plugin) that requires something no longer in the central repo If you want to criticize Java then at least make some meaningful points. It's the tech equivalent of "You're a stupidhead".
0 Comments
Leave a Reply. |