Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Frameworks are not applications. By their nature they are more abstract. Don't judge the code as if it was something it's not.


Totally. 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.


I 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.


Indeed, 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!



Hah. 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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: