Object Relational mapping - the Vietnam of computer science - Ed's Blog
in

dotnet.org.za

South African .NET Developer Portal

Ed's Blog

Object reference not set to an instance of an object

Object Relational mapping - the Vietnam of computer science

Ted Neward made this post on the state of the Java world. In it he describes ORM as the Vietnam of computer science, meaning that massive effort is being put into this area without much progress. He also calls on Microsoft to forget about the whole idea of ObjectSpaces.

I don't know if they already have, because I can't find much on ObjectSpaces on the internet, and it seems not to be included in the Visual Studio 2005 Beta. I don't however agree that MS should give it up. I recon although there are many tools, it's nice to have one built into ADO.NET. I think ORM defnitely has it's place, and although I agree that effort should not be wasted on this, it should not lag behind either.

There are some other things Ted says in his post on CORBA that worry me, especially the part that OO is not the way to go anymore, I cannot disagree more. It's a shame that he gives so little explanation for his opinions.

Published Oct 05 2004, 08:30 AM by eduard
Filed under: ,

Comments

 

Armand du Plessis said:

objectspaces was dropped from vs2005 after the pdc tech preview.
it's now merged with WinFS and will ship when WinFS ships.

The funny thing that no-one mentions is that there was a version of something very similiar to ObjectSpaces that was shipped by Microsoft in the .NET 1.0 Beta 1 timeframe. That kinda just dissappeared after Beta 1. I think that package was also called objectspaces. I went looking for it again a while after .NET 1.0 was released but there was only a couple of mentions of it on some newsgroups. So a O/RM has been in the pipeline for quite some time.
October 5, 2004 8:43 AM
 

TrackBack said:

October 5, 2004 9:37 AM
 

TrackBack said:

October 5, 2004 9:42 AM
 

Senkwe said:

I can sort of, kind of, perhaps etc understand where Teds coming from. He's talking about Enterprise systems. The Enterprise systems of tomorrow will likely be modeled using SOA principles (if you take the latest buzzwords as gospel). Now, when I listened to Clemens Vasters DotNetReocks episode, something just sort of clicked. OOP implies you're worried or are at least interested in object state. But a service in my mind, though it can be built using OO principles, the end result doesn't HAVE to be modeled after a stateful object. This is clear when you consider that services are likely to be invoked asynchronously anyway. And in fact, because the service just kind of sits there, pretty much self hosted, I have a hard time believing that you need anything more than a bunch of static methods that return whatever it is you were after, less complexity and just as easily extensible/flexible.
October 5, 2004 12:17 PM

Leave a Comment

(required)  
(optional)
(required)  

Enter the numbers above:
Add
Powered by Community Server (Commercial Edition), by Telligent Systems