Code For Web

I was at the book store last night and this dude actually picked up a book on Django, I thought I was the only person around my hood that knew what Django was. Talked to the guy for a bit, a very solid insight to the framework. Something worth checking out. Go Python!!!

Oh, I was at Borders, cause Barnes and Nobles sucks!!! I emailed them a few years back and questioned why they continued to reduce the computer book selection each time I went into the store. Their response was, “our market research shows that those types of books are not being sold in our stores”. Reason, Amazon.com, Bookpool.com… and your discount program sucks. Borders its free and you get some very nice coupons.

Python Django, Python

Shifting from development process to another takes a little bit of time. Currently most of the projects we start are ASP.NET(C#) projects. Why, that is what we know, and can product high quality code with. The shift, to Ruby On Rails. Why, agile practices, development time, and many other small nice additions and features we have come to love.

Yes, with ASP.NET you can practice agile processes, but the ASP.NET MVC Framework is not 100% yet, but it is solid. With ASP.NET you have the joy of compiled code, “speed”, faster loading and so on…

But, with open source being a nice shiny rock to look at we decide it was time to give it a test run. I evaulated RoR, Django and CakePHP. CakePHP, lost instantly because I am done with PHP in general, so it did not have much to stand on. Django, very interesting framework, and some great features like “auto-admin” pages. The Python language is fun to work with and the overall power of the framework is very impressive. RoR, this being the most mature of the three and the most community focused, I felt that this for now would be the framework/development path of choice.

Currently we are various development stages with a few projects, 1 project is ASP.NET MVC, 1 is RoR and the last one is ASP.NET WebForms.

Out of these three, the one that I dread the most to work with is the ASP.NET WebForms. The development style feels old, clunky and just slow. The code-behind-method and the lack of any real separation of concerns is a major downfall to this development process.

ASP.NET MVC is a breath of fresh air, but late to the scene. In typical MS fashion they tend to copy, and no longer be a leader in the field. The team developing the ASP.NET MVC Framework has done an amazing job, and the framework is great to work with. It still has a long way to go, but the overall status of the framework now is very promising. Only issue, many .NET developers will sit on the fence and either stick with WebForms or move onto MVC. There will be a divide in this development space.

RoR is really comminity driven. One thing that is somewhat good about the framework is that they is only one way to do things. Configuration is only in one spot, the Ruby language is refreshing to work with and easy to pick up. Overall the experience has been pleasent. Only issue was deployment, since there is a little more involved in this step. But after working out a few issues, things are flying!

Asp.net, Asp.net MVC, Ruby, Ruby On Rails Asp.net, Asp.net MVC, Django, MVC, PHP, Python, Ruby, Ruby on Rails