3 ms·
I've been creating the same webapp (a simple bug tracking system) over and over again in different frameworks to learn the stuff I care the most: -Localization
by eldelshell 12y ago
I've been creating the same webapp (a simple bug tracking system) over and over again in different frameworks to learn the stuff I care the most:
-Localization (amazing how many web frameworks suck at this, specially, client-side frameworks)
-Learning curve
-Authentication / Authorization
-CRUD, REST, TDD, LoC
-Template language
-Fragments/Tiles/Panels support
-Deployment (i.e. grails WARs are amazingly big)
Over time I've made this webapp in Grails, Play, CakePHP, RoR, Django, Flask, Wicket, SpringMVC, Struts1-2, Hibernate, jOOQ, Angular (ugh!), ExtJS, Express and Meteor.
What I like about this is that I don't have to think about how the product will work, no design, and I can reuse most of the HTML structure (header, footer, menu, etc) and I can compare and reach a conclusion about the framework pretty fast. If I can't make the freaking thing work after two days, the framework sucks or I'm simply too stupid to use it.
- cujo 12y agoSo based on your experience with this process, what are your comments on the listed (or unlisted) frameworks?
- aaronem 12y agoAngular gets an "ugh!" but ExtJS doesn't?
- eldelshell 12y agoYeah, it's a personal opinion, but Angular is weird, and ExtJS was easier to get a hold off five years ago, so go figure.