@dkf said in You know WPF, but do you know .Net Core?:
I note that this matter seems to be much more of a debate in C#-land than when working in Java. I guess it's because Java's got a very good DI/IoC container framework and everyone just uses that rather than spending effort on debating the bleeding obvious.
I think it's just a product of different culture. J2EE server were always insane overcomplicated and overpriced mess (I believe I have already mentioned IBM today, have I?), which created strong incentive for alternative solutions; this is combined with Java being completely free, which created strong culture of FREE alternative solutions. Microsoft's offer was better and less convoluted, plus the whole developer culture was completely closed. I distinctly remember the first time I have worked with C# developers; they genuinely refused to use anything that was available in Windows Update
IMHO it's just a coincidence that the IoC idea came about the same time and Spring jumped on it. But there are other (and arguably better) IoC containers; Spring just comes with "batteries included". So, basically, it's popularity is similar to popularity of python in some areas.
Yes, people make fun of Spring's internal naming conventions, but as a user of it, you hardly ever need to look into the cesspit (and convention is that you shouldn't!)
This is actually very interesting; the whole AbstractSingletonProxyFactoryBean
meme is usually used to mock Design Pattern or even OOP in general. But it does not have anything to do with that, except some naming convention maybe taken from GOF book. In reality, it's and internal class and part of very convoluted magic used to circumvent the lack of metaprogramming in Java. Yes, the very need mucking around with reflection is a , but it's completely different .
is that the mainstream languages still use design from 1980s.