WTF Moment: Cloud Computing

Has anyone heard of Microsoft's cloud computing initiative? And if so did it set off the same alarms that occurs when a 747 Air Jordian Jet Liner accidently flies into the White House Air Space? If it didn't let me break down for you what is happening here.

Microsoft first killed off Visual Basic which opened the door for them to kill off Visual FoxPro. This was not done because these were bad products (actually both are far better then Visual Studio/.BLOAT) nor because the communities were dying. This was totally a self serving Microsoft base decision .After completing this objective, Microsoft introduces cloud computing which basically means the great folks in Seattle want to house YOUR data for you on their servers.

Now you might be saying, Mark what is so bad about this. Well first off I predict the cost of SQL Server is going to SKY Rocket over the next 5 years to a point it will no longer be economically feasible for you to own the SQL Server software licenses and we will be forced into the cloud programming paradigm. If that does not work, Microsoft will simply stop offering SQL Server licenses exactly like they did with VB and VFP as that precedent has been set. Thereby Microsoft can implement it's subscription based pricing model to access "YOUR" data.

Then Microsoft is going to develop an airtight EULA for CLOUD SQL Server which basically will permit Microsoft to own YOUR data. The power this will give Microsoft is enormous and Microsoft will then have the leverage it needs to compete against Google. For example Microsoft will be able to access this data for targeted browser search engine advertising or mandate this data can only be accessed by Microsoft based browsers.

Microsoft did not become a Monopoly due to their innovation, their development group of programmers are not that good just look at VISTA not even Microsoft's marketing team could save that software disaster. Microsoft does excel however in business as that is what got them to where there are at today and don't be fooled this is strictly a business decision not a programming one.

Unless developer's completely rebuke this idea, which given the level of the cheerleading that is currently occurring, I doubt that will happen. The "CLOUD" that is coming is Microsoft's perfect storm which will unleash yet another Microsoft attempt at a monopoly and raise share holders divdiends in the process.

Till Next Time

.Mark

By The Way... A developer named Mr. Robert Wray has taken the time to post a blog entry about my blog. Which is kind of cool unforunately he took what I had to say out of context and obviously moderating comments. Therefore just to set the record straight below is my comment to Mr. Wray.

Hey Robert,

One question for you have you ever used Visual Basic or Visual FoxPro? My thought is you haven't otherwise you would have been aware VB and ASP can consume VFP middle tier DDL files therefore providing a far more robust N-TIER implementation with complete seperation between the UI, Middle Tier Code and either SQL Server or FoxPro Database files. We can also go the other way create a reusable activex control in VB and consume it in the VFP UI layer.

Something else really cool that VFP has and VS doesn't is a true data centric language with native data access which means it is doesn't suck at building middle tier components that follows N-TEIR standards which not even linq can do right. The only disadvantage is DLL hell syndrome which is more an operating system issue addressed completely with installshield.

The current production release of VS is nowhere near able to pull N-TIER off as cleanly as the above stated implementation maybe when/if MVC is ever released that might be close have to wait and see as currently MVC is in a state of disarray.

Moveover if my assumption is correct how do you know VS is better then VB or VFP? Curious if you read about it on GU'S blog and just following blind faith ?

With all due respect, I alway mention VB with VFP together when talking N-TIER design patterns. The rest of your post about my older is blog is equally inaccurate and probably will make little sense unless you thoroughly understand the C++ or VFP inheritance models therefore you were reduced to grasping at toolbox icons as being my issues therefore missing my entire point. Perhaps in the future do your research before flaming other developers and get your facts straight.

Best Regards,
Mark Gordon