Blogging the days...

My first impact with the MVC concept was through the book by Hans Bergsten JavaServer Pages . Without realizing it I had a working MVC framework that did it's part in getting me a excellent grade on my Web Application exam, and that makes you think and note even subtle differences between what's out there. Then an opportunity came out to build a real-world money-making J2EE app and I hopped aboard. The choice was made to lean on the Struts framework 1.2.x which was fine by me because I always wanted to go deeper in it's architecture to better understand it and to improve my own framework (no pretensions here, I did it for fun, not because I thought it was better). FFD to this day. Today you can see many new things coming into place; Beehive builds ontop of Struts and brings in the concept of Page Flow and Components and uses annotations, however there's some clunky code gen that needs to be done as well. Spring MVC does some incredible things in keeping stuff framework

I've read this article in which Linus gives his point of view on GPL v3. I must say that I'm with Torvalds on this issue, not that I am pro-DRM oriented but because you shouldn't really impose restrictions on other people that you wish your software/hardware would need to work with. On one hand GPL does give you some rights but it also locks you to GPL-compatible alternatives as well and I really don't think it's the best developer licence there is. The tragicomic thing about this is that we see GPL fighting GPL and I don't see it leading to anything positive. That said, if one can afford the time and thinks that he can strike a adopter/abandoner balance the GPL v3 might be a valid alternative. I just don't think it's in Linux's interest and the current user and developer base to pass over to GPL v3.