1,215 karma · joined March 16, 2009
I design and develop websites and apps.
The JSTL is not a factor in speeding up development. A lot of people even prefer a Velocity or Freemarker template engine when they are using Java. And I've never worked with MyBatis but have done plenty of projects with Hibernate/JPA and let me tell you: I've often come at a point in a project where I was wondering how much time I had saved by not writing the easy SQL queries and how much time I had lost by trying to work around some random restriction in the Hibernate API. For all the "hate" Django's ORM gets, I've never run into the same obstacles.
With all that said, the Play! framework addresses a lot of these issues and is a lot more fun to work with.
As mentioned in the comments of the article, this would mean the first to implement a new feature would be able to define how it works. Not a good idea. We need some form of consensus.
And also mentioned: some things do change. The definitions of border-radius for Gecko and Webkit are not the same at all.
I guess there's a lesson here: don't try to chase a higher conversion rate by getting in the way of "savvy" visitors. Still, it's a good idea once you cover all the edge cases.
(Though they look a lot like the Silk icons.)
If you don't want to do Java projects in the future, I suggest getting comfortable enough with other languages and frameworks on your own time.
For now: what's wrong with "RESTful" URLs? And you do understand you're not required to use 4 different layers in Java either, right?
But if you want it right now: create a custom command to do it your way and wrap it in an app that you add to the path. When you start a new project, the first thing you do is add the application to your installed apps and you can use it over and over again.
Loosely coupled objects will allow you to do that, but how would you redefine the behavior of something static?
Sure, that's not something you can simply show in a five minute conversation, but mockups are great for this purpose.
In the average JEE project, that's all you'll be using as far as Spring goes. Or maybe add Spring Integration or Spring Batch.
It would be nice to see something like this incorporated into Django itself, but I guess you can't expect it to bake you a cake, manage your finances and provide you with an easy way to build websites all in one single package. But a man can dream.
I have to agree with the article up to a certain point though: creating mockups helps me find out what I need to build. Of course, creating a graphic design is something entirely different.
Edit: because a simple link to the website won't tell you a whole lot about the idea behind it, here's a shot at explaining the basic premise of the core of the Spring framework.
Instead of hard wiring objects, you let Spring handle it for you through dependency injection. You simply specify that you want an "authentication" object and the framework will go ahead and look it up. Whether it's an LDAP authentication object or something for a different backend is determined by the context, which you can specify in XML or annotations.
I like it. Nice and clean, the charts are exactly what I'd need and the options to view daily and monthly reports are good. Maybe it's a bit too minimal: use a bit of a gradient on buttons, use alternate background colors for the expense list; get a bit of color in there. And I'd change the "Reason" label to "Category".
Err... how exactly would that work? Just because you know the username and/or email address you should be able to reset the password?
Does anybody here have an idea that could work?
Edit: to clarify: I'm not a huge fan of the "Your question/Your answer" approach either.