3 ms·
Frameworks are not applications. By their nature they are more abstract. Don't judge the code as if it was something it's not.
by SideburnsOfDoom 14y ago
Frameworks are not applications. By their nature they are more abstract. Don't judge the code as if it was something it's not.
- famousactress 14y agoTotally. I've worked on some frameworks, and I get that things get hairy supporting some really crazy general and re-useable concepts. I'm not even saying Spring is shitty, or Java is shitty or anything. I don't really care... but don't you dare tell me that class isn't hilarious, because it is.
- mindcrime 14y agoI don't really care... but don't you dare tell me that class isn't hilarious, because it is. I don't see anything hilarious about it.
- chris_wot 14y agoIndeed, the class isn't hilarious. Perhaps the class name initially boggles the mind, but when you learn what it does not only does it make sense, but you probably would be hard pressed to find a better name!
- d0mine 14y agoIt reminds me: "Why I Hate Frameworks" http://discuss.joelonsoftware.com/default.asp?joel.3.219431 http://discuss.joelonsoftware.com/default.asp?joel.3.219431
- SideburnsOfDoom 14y agoHah. I'm not saying Spring is a good framework, I don't know it that well. But try building an app without any framework at all. Getting frameworks right is hard - they need to be abstract enough to be flexible, but not so abstract that you end up with a "general-purpose tool-building factory factory factory" when you want the framework to give you a hammer.