Today The Register pointed out a Microsoft's document about "Configure telemetry and other settings in your organization". It has a scary passage. When in "Full telemetry level" - the default level in the Home and Pro versions, it allows Microsoft:
Embarcadero (recently acquired by Idera) announced AppMethod, its cross-platform only development tools, available only under a subscription model (Individuals $299 per year, per developer, per platform. Enterprise $999 per year, per developer) and launched less than two years ago, will be no longer be available, and "will be merged into RAD Studio 10".
BusinessWire posted this news about the no-longer-so-secret sale of Embarcadero to Idera.
On September 24th, Moody's acted on Idera rating, citing "The rating action follows the announcement of the company's pending acquisition of Embarcadero Technologies, Inc. ("Embarcadero")" and "integration challenges associated with the Embarcadero acquisition which will more than double the company's size" (see https://www.moodys.com/research/Moodys-assigns-B3-CFR-to-Idera-Inc-outlook-stable--PR_335231).
A colleague of mine was using the "modernized" service implementation I wrote about some time ago. His services needs to be notified when a user logs on/off or locks/unlocks the machine. Everything was fine for a while, until he started to complain it worked for a while, but then, "randomly", notifications weren't triggered any longer.
Resident Embarcadero wizard of Oz, David Intersimone, has been so bold to write about Delphi "security". You know I already wrote about the utterly lack of security in Datasnap (but relying on web server security using https), but there are some true pearls in that article.
Despite what promised, Embarcadero wasn't able to meet the February 1st, 2015 deadline for 64 bit iOS apps. Not a surprise. Just another warning Embarcadero is trying to do too much with too little, and aligning someone else deadlines and releases with your own is difficult and usually not worth the effort.
No, the title of this blog post is not a mistake. Delphi, including XE7, only implements services using NT APIs obsoleted since Windows 2000. Windows NT was EOLed in 2004, 2000 in 2010, and XP last year, yet Delphi still doesn't take advantage of the new APIs. What are the advantages? Well, using the "extended" RegisterServiceCtrlHandlerEx() and its HandlerEx() callback, services can receive more and useful notifications (control codes). The new control codes allow to be notified of and handle:
Today a colleague of mine was trying to import VMWare 5.5 WSDL into Delphi. When he tried to compile the application, it got:
[DCC Error] vimService.pas(60427): E2575 RTTI for 'VimPortType' is too large; reduce scope with $RTTI or
reduce type size
Delphi Doc Wiki says (XE7 too):
This occurs when the generated RTTI is too large (greater than 64kB).
In the past days, I bought a Netgear WNCE3001 wireless adapter to connect my pay TV decoder to the Internet. To configure it, you need to connect it to a PC Ethernet port, and use its configuration wizard to perform the initial configuration - which is just configuring which wireless LAN you want to connect to, and its encryption parameters. In my case, the wizard was unable to complete.