Check out this quick & to-the-point comparison of the leading RAD web frameworks:
http://prezi.com/n9re7-x9guah/django-and-rails-and-grails-oh-my/
by sefi
tags:
border:
In previous posts in the series we discussed new features in Flex 4 that are basic in nature (namespaces, an introduction to the new Spark components architecture and the new mxml tags to name a few).
In the next few posts we will discuss the more interesting stuff new with Flex 4 like FXG, states, layouts, effects and skinning.
So, without further ado, View States!
by sefi
tags:
border:
In previous posts in the series we discussed namespaces, an introduction to the new Spark components architecture and the new mxml tags introduced with Flex 4.
This post is all about data binding, and two-way data binding new to Flex 4 specifically.
by sefi
tags:
border:
Flex 4 added some namespaces, while it still supports the Flex 3 namespaces. This can cause some confusion, more so since some classes are part of two namespaces.
by sefi
tags:
border:
Now that Flex SDK 4 was released, I thought I'd do a series of posts on the differences between Flex 3 and Flex 4 SDKs that will hopefully help migrate your Flex 3 app to Flex 4 or make the transition from SDK 3 to SDK 4 easier. I will be assuming you already know Flex 3 and will concentrate on the new in Flex 4 compared to Flex 3.
This post will serve as the index of the series, and I will be adding links to the different posts to this one as they become available, so come back from time to time to get updated.
by udib
tags:
border:
A recent study measured the productivity of using Python+Django vs. C#+ASP.NET, in terms of user-stories per week. The results are that 1 Django developer is equivalent to 2 ASP.NET developers, productivity-wise:
http://kurtgrandis.com/blog/2010/02/24/python-django-vs-c-asp-net-produc...
The Django team that participated in the benchmark, BTW, had no prior experience with Django, which probably implies that the difference can be even higher.
by yanai
tags:
border:
This article introduces and compares two of the most popular open source persistence frameworks, iBATIS and Hibernate. It also discusses the Java Persistence API (JPA). It introduces each solution and discusses its defining qualities, as well as its individual strengths and weaknesses in broad application scenarios. It then then compares iBATIS, Hibernate, and JPA based on factors such as performance, portability, complexity, and adaptability to data model changes.