This is not a rethorical question. And not because now Delphi targets OSX, iOS or Android, and it applies to those writing Delphi applications that runs on Windows only. There's a real difference, and it's important to understand it especially now the usual lame BorInCodeDero marketing is trying to use the end of Windows XP support to sell Delphi upgrades. But is Delphi today a real Windows development tool? My answer is no.
Today François Piette has written about "Path issue when having installed a lot of software": Windows is having some trouble with very long path environment variable, even in Windows 7. This is true.
In his post Blackberry is Still Ahead of Microsoft, Jim McKeeth uses US numbers only to try to demonstrate that Embarcadero should never support Windows Phone, up to the point to say that Blackberry is ahead of it.
Many developers learnt first to code on isolated machines - DOS ones if they are old enough - or within simple networks. DOS was a single process, single thread environment, almost always on isolated machines. Maybe a modem to connect to a BBS, LAN were much rarer. That meant developers had little to care about "the environment" their application where "living in". Once the application was started, it was the only one running (but some tricks like TSR) and could use all the resources available. Slowly, the environment changed.
If you try to post a comment to Jim McKeeth The Podcast at Delphi.org blog while you're behind a company proxy, you get this error:
Your comment has been blocked because the blog owner has set their spam filter to not allow comments from users behind proxies.
The latest release of MSDN online no longer lists unsupported operating systems in the "Requirements" section, "Minimum supported client" (or server). Now the "minimums" are XP and 2003. 2000, NT and 9x are gone, even if that API is supported by those versions. If someone needs to write software for those systems and needs to know which supports what, it's better he keeps an older MSDN help file around.
And there are some funny changes (highlighting is mine):
The first beta release of Message Compiler Editor 3 is available here. The main new feature is the support of Unicode message files (version 2.x was still compiled with Delphi 2007). Importing already existing message files is planned for this release but not available yet due to some bugs still needing to be fixed in the parser.
Some reactions to some posts of mine on Embarcadero Delphi non-tech forums are interesting. It looks many Delphi users on that forum are victims of a kind of "siege syndrome" and don't accept any critique to Embarcadero behaviour. Let's analyze it.
Everything started when Embarcadero announced the Delphi 64 beta, saying that XE customers would have been given precedence. It looked like a silly decision to me. My reasons are:
A friend of mine pointed me to this post by Nick Hodges. I wonder if it is a hint about what happened at Embarcadero with Delphi XE. It should have been the Windows, Mac and Linux cross compiler, with a new CLX (the 1000 widgets?), which instead just before release turned out to be just an interim release with some third party products integrated, a primitive SVN integration, and some enhancements here and there.
When I wrote the QC entry about Datasnap 2010 HTTP client missing proxy support, I marked it as a bug. It was later changed by a sysop to an "enhancement request". That simple change shows why Delphi is in the actual state. It's a problem of mindset. Embarcadero people still lack the mindset to deliver applications made for the 2010s.