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.
It looks my efforts to convince BorCodeDero to design a sound security model into Datasnap are doomed to fail. The main reason is it looks only me is worried about the actual fake secutity model. Known speakers and writers about Delphi look totally unaware about sound security. Look at this post by Bob Swart.
Many "news" about the imminent death of PC are appearing around despite its 30th birthday, replaced by smartphones and tablets. What's true in that? Let's look for a moment at the past history, and the personal computer revolutions. Before that there was centralized systems from which you could rent some processing time and highly proprietary systems using software paid yearly (clouds, anyone?), and consumer electronics were made by highly specialized devices that could usually only consume proprietary contents.
It's now confirmed and made public that FireMonkey (let aside its ill-fated name, for now) will be the Delphi cross-platform GUI framework. FireMonkey, aka KsDev VgScene/DXScene is a vector based GUI framework. So it looks after two attempts failed to build a cross platform library first on Qt (CLX) then on .Net (VCL.Net) Embarcadero selected the Java Swing approach and decided to develop its own proprietary GUI framework. It's a dangerous approach, for several reasons.
Recently my mail server started to deliver an increased spam volume. Inspecting the logs I found Spamhaus blacklist was no longer effective. After some tests, it turned out that the DNS used by my (virtual) server at Aruba non longer resolved Spamhaus queries correctly:
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:
This post is in Italian because it is about issues with my Italian ADSL provider, it could be interesting to an Italian audience only.
Dopo dieci anni di felice uso della mia linea ASDL Infostrada, improvvisamente, a metà aprile, la velocità passa da una media di 4-5 Mbit (con punte vicino ai 7 massimi, essendo a poche centinatia di metri dalla centrale), ad appena 0,5 Mbit (con rare punte attorno al megabit), non rararamente la velocità in upload è maggiore di quella in download.