@Egon: and how would you go about creating said statistics?

The primary maintainer of SubSonic is a Microsoft employee, but SubSonic is open source, and was started before said employee was a Microsoft employee.

About 90% yes.

Hi Nick.

I'm mostly with Scott, but I wouldn't shoot...I'd medicate.

That rant was more in line with a delusional mind with the barest if knowledge of TDD. This is evident in the continuous confusion of Agile and TDD (they are different things). Seems like the work of a developer who doesn't like interacting with people.

Singletons are a nice easy pattern, that even if done correctly, can destroy code if used improperly.
The fundamental problem is when you try to unit test code that uses a singleton. One of the tenants of unit testing is code isolation.
Without spending some serious cash and buying TypeMock, you cannot isolate out a singleton (the correct word is Mock). This makes developing a test strategy VERY difficult.

Case in point, about bad singleton usage, NEVER-EVER implement your database layer (also called a repository) as a singleton. If you do, it will be impossible to isolate your database code from your business logic. This makes tests take longer to run, and you are having to test two sets of code. So if there is a failure, you can't be sure which set of code had a problem.

Singletons are evil. Really. They cause more issues in software than any other single pattern.

Seriously, don't use them. If you really (think) you need one, make your IOC container do it for you instead.

You having 2 out of 14 is excellent...for me.

@everlast: How about the ability to change the title? That would work as well.

Agree with Aquinas (but I still prefer Calvin :D ). This type of site should be banded completely.

On a related note: When are we going to get a down mod?

Good tool, nice update. I like the extension methods.

http://elegantcode.com/2008/06/29/looking-at-rhino-mocks-35-rc1/

Personally, I agree that Asp.Net developers (myself included) need to wake up...just not for the same reasons.

What I want Asp.Net developers to learn is JavaScript. I can't tell you how many times I've seen perfectly decent developer cower at the thought of writing a bit of JavaScript on the browser. It isn't healthy.
Better yet, learn a JavaScript library like JQuery, Prototype, MooTools, YUI, or even the AJAX Library JavaScript extensions ($get() anyone?).

This is something you can use right NOW, not 2 years from now when technology xyz has hit critical mass to be useful.

Because blogs, DotNetKicks, Digg, MSDN, user groups, and various other outlets just aren't sucking up enough of your free time.

But it is rather amusing to listen to Scott Belware rant in 140 characters or less.

Me three. Digg has a "Bury" option. Can we get that here?

@foobar > I'm sure that'll work out well. I mean, who needs indexes when you've got NHibernate?
No, that is being stupid. There is nothing about ORM that trumps Relational theory. Actually, I think you are talking out of your ass because I doubt you've ever used an ORM. They still create SQL, but in a more programmer friendly way. The reality is that you can write really bad queries in either one -- a good ORM will just help you from creating super bad queries.

And you can take your 1,000,000 entry tables. If your database fits on a laptop hard drive it just isn't that big of a deal to me.

>Relational databases were created by computer scientists. ORMs were originally created by Java developers.
ORMs predate Java, go back to SmallTalk. And if you are thinking those guys are Computer Scientist you are out of your freaking mind.

Here is a different one for you: SQL is the Assembly of programming languages. I've said that one before too.

I'm sorry, most of what this guy is saying is crap.

1. learn about single responsibility
2. GridViews are fine for many applications
3. ObjectDataSource can be used effectively, but you should know when not to use it.
4. Everything this guy says about store procedures is pure and utter crap. I don't think he has even tried doing a performance comparison, and doesn't mention parameterizing ad-hoc queries. That is misleading as all get out.
5. You shouldn't be writing SQL anyway! It is called an ORM. Lookup NHibernate, SubSonic, LLBLGen, LINQ2SQL, and pick the one that works best for you.