3 ms·
"They didn't take a patch on one occasion, and then we had a couple never-diagnosed bugs that we think could have been in the framework." Fair enough, but I wo
by hp 15y ago
"They didn't take a patch on one occasion, and then we had a couple never-diagnosed bugs that we think could have been in the framework."
Fair enough, but I wouldn't switch to an inferior framework over it.
- stcredzero 15y agoIf that shop is stuck with debugging into a method in HashMap, then they aren't qualified to evaluate whether or not it's in the framework. That said, the developer community needs to address the problem though education, if it's user error (most likely) or come up with enough manpower to be more active in support. After having seen their video, I have to say that the Play! framework folks seem very insightful in their design goals. They hit the nail right on the head in terms of the major usability problems of most Java Web AppServer software.
- burningout 15y agoWe use play in all our projects and hit some bugs as well. (Like different versions of classes being in jars and in code -> signature mismatch) It's a great project and no software is without bugs.
- stcredzero 15y agoIt's a great project and no software is without bugs. What makes or breaks great software is community and culture.