Microsoft Phasing Out ESP Simulation Platform?

Ian Lamont writes "Overlooked in last month's news about Microsoft laying off the entire Flight Simulator dev team is the news that Microsoft's ESP development team has been gutted as well, and the future of the platform is in doubt. ESP is oriented toward industrial use, and lets companies build 3D simulations for flight and other applications. Late last year Microsoft announced big plans to expand ESP to other verticals, such as real estate, city planning, and law enforcement. That looks increasingly unlikely. Even though Microsoft declined to comment on ESP's future, companies which invested in the product are angry, judging by some of the comments on an MSDN thread. As noted by one user, 'my company used it for a solution and invested time and money into getting it approved and purchased. Microsoft sure handed us a raw deal for taking a gamble on their platform.'"

Comments

ESP

[Anenome]

Not to worry, with their mind-reading abilities I'm sure they'll find new jobs in no time ;P

VB6

[spectrokid]

Microsoft sure handed us a raw deal for taking a gamble on their platform.

It is as if I hear a million VB6 developers screaming all at once...

Re:VB6

[Joce640k]

.Net, Silverlight, .... all will pass.

Re:VB6

[shutdown -p now]

This reminds me of this classic by Ron Burk:

First, there was the Windows API and DLL Hell. Revolution # 1 was DDE remember how hot links let us create status bars showing the current price of Microsoft stock? About that time, Microsoft created the VERSIONINFO resource, which eliminated DLL Hell.

But another group within Microsoft discovered a fatal flaw in DDE: they didnt write it! To solve that problem, they created OLE (which was like DDE, only different), and I fondly remember a Microsoft conference speaker proclaiming that the Windows API would soon be rewritten as an OLE API, and every control on the screen would be an OCX. OLE introduced interfaces, which eliminated DLL Hell. Remember in situ fever, and how we dreamed of the day that our applications would all be embedded in a (apparently very large) Word document? Somewhere in there, Microsoft got the C++ religion and MFC emerged and solved all our problems again, but with inheritance. Well, OLE wasnt going to take that sitting down, so it re-emerged as COM, and suddenly we realized what OLE (or was it DDE?) was really meant to be all along and it even included an elaborate component version system that eliminated DLL Hell.

Meanwhile, a renegade group within Microsoft discovered a fatal flaw in MFC: they didnt write it! They forthwith corrected that problem by creating ATL, which is like MFC, only different, and tried to hide all those fascinating details that the COM group was trying so hard to teach us. This stimulated the COM group (or was it OLE?) to rename themselves ActiveX and issue hundreds of pounds of new interfaces (even new versioning interfaces, which eliminated DLL Hell), along with the ability to make all our code downloadable via web browsers, complete with user-selectable viruses (ha try to keep up with that, you ATL weenies!). Like a neglected middle child, the operating systems group cried out for attention by telling us all to get ready for Cairo, some weird crud that they could never really explain, let alone ship. To their credit, however, the operating system group did introduce the concept of System File Protection, which eliminated DLL Hell.

Meanwhile, another group inside Microsoft discovered a fatal flaw in Java: they didnt write it! That was remedied by creating J, or Jole, or ActiveJ (honestly, I cant remember the name), which was like Java, only different. That was very exciting, but Sun sued Microsoft under some archaic law that limits the amount of crapulence any one company can ship in a year. This was clearly an attempt to stifle Microsofts freedom to create products that are like other products, only different, and resulted in the creation of The Microsoft Freedom to Stuff Money in the Trousers of Congressmen Network (newsletter and $14.75 T-shirts available). Remember the J/Jole/ActiveJ program manager pounding his shoe on the table and insisting that Microsoft would never abandon his product? Silly wabbit! All this could mean only one thing too little attention for the ActiveX (or was it COM?) group. This incredibly resilient herd of API gushers came back strong with COM+ (shouldnt that have been ActiveX+?), and MTS. (I have no idea why theres no COM or Active or X or + in MTS they totally shocked me with that one!) They also threatened to add yet another + onto all their buzzwords in the very near future.

Around that time, someone was yelling about Windows DNA and the Windows Washboard for a while, but that died out before I ever figured out what it was. At this point, Microsoft had been watching the Internet for several years with growing unease. Recently, they came to the realization that there was a fatal flaw in the Internet: well, you probably know what it was. And that brings us up to date with .NET (pronounced like doughnut, only different), which is like the Internet, only with more press releases. Lets be very, very clear about one thing: .NET will eliminate DLL Hell.

We can't be missing much...

[wjh31]

The microsoft ESP wiki is a red link

I've heard rumours...

[Anonymous Coward]

...that MS is planning on open sourcing the entire code base as abandonware, so customers don't have to worry.

It'll be released right after hell freezes over.

Road Map

[xixax]

Hey, don't worry. Unlike these fly by night open source people, proprietary software has a road map...

a blank page showing Bumf*kt Arizona and a tag, "You Are Here".

Re:Hey, Here's an idea...

[poetmatt]

She's the only one with the balls for the job.