The Right Answer

While on the subject of frameworks, think about this. I used to work in Java, and found that my choice of frameworks and technologies was staggering. I had EJBs, Hibernate, Spring you name it, I could use it.

But this I actually found quite daunting. How am I supposed to choose between them? When I made the move to .NET, I found that actually, the Micro$oft monopoly helped me out a bit. Suddenly there was an objective statement: “This is how we expect you to develop software using our tools”. These methodologies were built right into the IDE, ready and waiting.

With The Antitrust Case, building IE into Windows was a good move and a bad one for Microsoft. It got them mass exposure, and IE became the default web browser for the masses. They built their own tools right into the OS, thus making the OS more functionally rich out of the box. This meant that the average new computer user would never have to look past the end of their nose for most things. It was only when the competition realised how difficult it was to get people to make the switch that this began to change.

So with that in mind, surely we should be thinking that the prescription approach is a bad one – after all, it’s hard to argue that NHibernate doesn’t beat the built-in DataSet designer hands-down, but in terms of the all important usability stakes, the DataSet designer takes the chequered flag.

So, another case of wrong is better? It certainly buys time to work out your version 2 with the fancy NHibernate database-independant data access layer, but to get your version 1.0… Well, let me know what you think.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s