![adobe coldfusion builder 2 adobe coldfusion builder 2](https://i.pinimg.com/originals/5c/47/44/5c47441940095af6cecd3692f31c3682.jpg)
You come back to say not all of Windows XP entered it’s EOL in 2005 from your previous post that goes ‘XP entered it’s EOL lifecycle in 2005’, that is a change in the *FACT* already. Microsoft clearly states that it will support Windows XP till April 8th 2014. But felt it is nothing but a waste of my time.
Adobe coldfusion builder 2 how to#
There is surely a scope of improvement for us and we will see how to better it during the next cycle of Windows I contemplated replying back to you with the same insolence that you showcase in your response. I am not trying to justify the time of release for the Windows support. Your statement did not sound that way until you clarified it. We do have few companies stuck in older versions of ColdFusion 5/6/7. In closing, pls shelve your patronising attitude and address the point, rather than attacking the person making said You are right. Especially if contextualised by observing you don’t even support your OWN products that are much more recent than that. So I question what the logic is behind you wasting resources continuing to support anything about XP on ColdFusion. This is, I hasten to add, not because MS had any desire on the part of MS to prolong support for XP, but just that the clientbase weren’t interested in shifting from it.
![adobe coldfusion builder 2 adobe coldfusion builder 2](https://screenshots.macupdate.com/JPG/19497/19497_scr.jpg)
It’d be even more dead even sooner had Vista not stumbled off the blocks. The fact of the matter is – in almost any way one comes to measure it – XP has been being phased out for the best part of a decade, and is basically dead technology these days. I didn’t say MS didn’t / don’t offer any residual support on XP, and that’s not really relevant to the point I’m making. And we’re now 7.5yrs after that timeframe. Sure they continued to support various patched releases after that, but that’s not so relevant to the point I was trying to make. Support for the initial releases of XP ceased in 2005. I – likewise – checked the dates on the other things I mentioned. This is borne out by the link it cross-references. what you are saying hardly makes any sense.”), whereas I was simply making a fairly reasonable observation. You were being patronising and dismissive of what I said (“Get your facts right.
![adobe coldfusion builder 2 adobe coldfusion builder 2](https://mac-cdn.softpedia.com/screenshots/ColdFusion-Builder_10.jpg)
![adobe coldfusion builder 2 adobe coldfusion builder 2](https://s.getwinpcsoft.com/screenshots/53/53993_2.jpg)
What insolence, Rakshith? You told me to check my facts, and I was asking you to clarify which you meant, because I *had* checked my facts. 5 years of core support is a standard that we have followed for many years now across multiple releases.įinally, get rid of your disrepectful quotes that you seem to throw once in a while to make your point, if your point needs to be considered at all. If Microsoft intends to support XP for a longer duration that doesn’t mean that we will have to match that with support for our products. But having said that, we will surely get rid of XP and Vista in the upcoming versions. And for all you know, you would be the first one to jump out and ask us why XP support was removed without any notice. If we had taken off XP back when we came out with CF10 in 2012, that number of CF developers using XP would only be higher than this if not lesser. XP is still supported by Microsoft and I have recent data to believe that good amount of developers still use XP. I will be keen on addressing a point, but I will not take any random statement that you make that turns out to be on the lines of your statement quoted above! Let me quote the remark that you made “WhyTF are you still pissing around …” Looks like you need to be reminded.