<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for techman2008</title><link>http://disqus.com/by/techman2008/</link><description></description><atom:link href="http://disqus.com/techman2008/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 01 Aug 2008 09:55:23 -0000</lastBuildDate><item><title>Re: Stuck Between a Rock &amp;#8211; and Microsoft</title><link>http://changeforge.com/stuck-between-a-rock-and-microsoft/#comment-1070881</link><description>&lt;p&gt;Ken, Not to preach but that's what you get for relying on MS for your mission critical telephony.   There is no real reason you have to run your system on a Windows OS.   I prefer the appliance approach where the updates are the responsibility of the vendor.  And I am also a little paranoid about putting all my eggs in Microsoft's basket.  A parallel to this is OS running on Printers and MFP's.  MS tried to put windows on this device class several years ago and you see what has happened.  MS will always focus on its core business first.  When partners utilize its OS for other functions than what MS provided it for they are on their own.  The fact that they are would prompt me to have a service agreement that would consider the changes to the core OS effecting the product are the vendors responsibility...because it is what they chose to run the product and therefore a essencial part of the product they sold you.  Your solution is not a windows accessory, it needs windows to operate.  It comes down to the vendors perspective on cost controls and selling you something at a point in time.  The Windows OS is never fixed at point in time.   In my mind opensource is far more logical in how they approach working with applications.          &lt;br&gt;- techman2008@msn.com&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">techman2008</dc:creator><pubDate>Fri, 01 Aug 2008 09:55:23 -0000</pubDate></item></channel></rss>