Developer Choice
This post initially started as a set of notes related to my own research around NHibernate and Linq to SQL. However, it quickly turned into a very obvious "ah ha" moment.
As I have previously mentioned, I have been doing a lot of research lately on various tools. One area I have focused on recently is data access. This is an area of hot debate for many people and can easily turn into a pissing match, so I first want to share my key take away:
The tool in itself, does not matter. It is all about what you are comfortable with.
In hindsight, this is very obvious. It is generally the answer to most developer questions (C# vs. VB, SQL Server vs. MySQL, ASP.Net vs. Rails). There will always be trade offs. The result will never be perfect.
This of course does not mean you shouldn't try anything new. The world of software is in constant flux. I routinely cringe at code I wrote a year ago. However, if you spend all your time looking for the perfect solution, you won't leave yourself the necessary time to build something great.
FYI, if you are still interested in the NHibernate vs Linq to SQL, here is a nice overview by Geoff Bennet.
Similar Posts
- Changing for Simplicity
- ASP.Net Quick Tips - State Management
- Enhancing Desktop Computing with the Cloud
-
WPF WPF UI Update from Background Threads [Via: ChristophDotNet ] Code Camps Charlotte Code Camp -...
-
Link Listing - May 14, 2008
-
I have been evaluating Linq to SQL and Castle ActiveRecord for a small project I am working on. In end I decided to go with ActiveRecord. As part of my experiment, I did a quick prototype of an ActiveRecord like pattern using Linq to SQL.
-
I have been evaluating Linq to SQL and Castle ActiveRecord for a small project I am working on. In end I decided to go with ActiveRecord. As part of my experiment, I did a quick prototype of an ActiveRecord like pattern using Linq to SQL.
Comments
ryhoward on on 5.14.2008 at 10:07 AM
Interesting point Scott, it's interesting to watch the constant debates over which tool is best, or why one language is better than the other. Although some are obviously better than others, sometimes it's better to just use what you like best.
Lee Brandt on on 5.14.2008 at 10:37 AM
Well put. My thoughts:http://geekswithblogs.net/leesblog/archive/2008/05/08/there-is-no-right-answer.aspx
Chris on on 5.14.2008 at 12:23 PM
So where did you end up being most comfortable?
Scott Tucker on on 5.22.2008 at 5:56 AM
I have to agree that it is what you are comfortable with. But honestly I don't see any comparison between NHibernate and LINQ to SQL. Linq To SQL is limited to just one database only and NHibernate is not. But overall the overview by Geoff is decent and highlights some of the differences.