tag:blogger.com,1999:blog-5650649138973583402.post522185658567148036..comments2023-09-20T07:28:27.572-05:00Comments on Linux in Exile: Why "We're a Microsoft shop" is badJim Hallhttp://www.blogger.com/profile/11598443864678006773noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-5650649138973583402.post-66779377654715190932009-10-08T09:53:17.353-05:002009-10-08T09:53:17.353-05:00Anonymous said:
some features that you know are co...Anonymous said:<br /><em>some features that you know are coming can easily justify the wait.. Heck the xeon 5500 processors and fast memory ( big iron) to make virtualization more viable just came into the world... i think microsoft had great timing on this and knows when to get into the game.</em><br /><br />Anon, are you saying that virtualization hasn't been "viable" until just recently when the Xeon5500's came out?<br /><br />We've been running ESX systems where I work for several years now. It's rock solid. We have partners that we regularly meet with, and every status meeting there's always a conversation about how we are continuing to move systems to VM.<br /><br />But I guess our years of success running VMWare ESX wasn't "viable" because the Xeon5500's weren't out then? I don't think I follow you.JHhttps://www.blogger.com/profile/05264061238864151815noreply@blogger.comtag:blogger.com,1999:blog-5650649138973583402.post-10948053195881261922009-10-08T09:36:16.803-05:002009-10-08T09:36:16.803-05:00"There is something to be said in having the ..."There is something to be said in having the kiss method.. if i tried to take every little piece of technology that might be better i would have a big, complicated mess of technology that requires much expertiece to operate... i think microsoft had great timing on this and knows when to get into the game... Yes i am a microsoft shop."<br /><br />Wow, you must be really behind the curve with thinking like that. HyperV has been out only since June of 2008 (according to Wikipedia). VMWare ESX has been there for YEARS doing this kind of thing. Companies have been moving to virtualization for a long time before Microsoft came to the scene (late, as usual) with their HyperV product.<br /><br />With your comments, are you saying that you KNEW Microsoft would eventually come out with a virtual machine system? So while everyone else was lowering their total cost of operations, consolidating hardware, especially dev and test systems, YOU WERE WAITING for Microsoft to eventually release something.<br /><br />VMWare actually had a product out that people were using, and demonstrated it was stable. But you waited because Microsoft might come out with something later? ("Some features that you know are coming can easily justify the wait..") So you waited a few years based on a promise or assumption that Microsoft would come out with something.<br /><br />Vapourware was made for YOU, my friend.<br /><br />I'm glad you're not my IT guy.some guyhttp://www.google.com/noreply@blogger.comtag:blogger.com,1999:blog-5650649138973583402.post-8016455152446326542009-10-07T20:33:47.717-05:002009-10-07T20:33:47.717-05:00this article is pretty narrow minded..
yes other ...this article is pretty narrow minded..<br /><br />yes other companies come out with great features and new features get incorporated all the time into various products.<br /><br />To suggest that the decision fool hardy based alone on the fact that this one feature was needed is a little short sighted.<br /><br />There is something to be said in having the kiss method.. if i tried to take every little piece of technology that might be better i would have a big, complicated mess of technology that requires much expertiece to operate... some features that you know are coming can easily justify the wait.. Heck the xeon 5500 processors and fast memory ( big iron) to make virtualization more viable just came into the world... i think microsoft had great timing on this and knows when to get into the game...<br /><br />Yes i am a microsoft shopAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5650649138973583402.post-63493923536890724712009-10-07T19:36:09.609-05:002009-10-07T19:36:09.609-05:00Microsoft's definition of "critical syste...Microsoft's definition of "critical system" appears to have come from the same dictionary as Amtrak's definition of "on-time".<br /><br />Where I work, it's a "Microsoft shop" too.george.whttps://www.blogger.com/profile/10893495384863805805noreply@blogger.comtag:blogger.com,1999:blog-5650649138973583402.post-24178205206917266672009-10-07T19:11:10.311-05:002009-10-07T19:11:10.311-05:00Wow - I guess MS redefined "critical system&q...Wow - I guess MS redefined "critical system" to mean "will sometimes run and sometimes has to be stopped for maintenance." One day MS may discover how to implement failovers and how the same tricks (and others) can be used to migrate a virtual machine without shutting down. Ever hear of how that MS HPC stuff is going? I'd love to hear some stories; I'm in the mood for a good laugh.<br /><br />Thanks to MS I'm currently wasting a lot of time and money with their software which does not work as sold. I really don't understand how anyone can have a "good relationship" with MS. Just the other day I had a long discussion with an electronics engineer and I convinced him to choose either Linux or FreeBSD as he works on Rev.2 of one of his products. I showed him how using XPe would simply result in a lot of unneccessary costs. Now if I could only convince my clients never to waste time with MS crapware...MadScientistnoreply@blogger.com