All posts by onlyconnect

The pros and cons of subscription vs perpetual licenses

Adobe has caused a stir with its announcement that Creative Suite will no longer be available under a perpetual license, for versions beyond the current Creative Suite 6.

Given this, the CC applications will be available only as part of Creative Cloud. We will continue to sell and support Adobe Creative Suite® 6 applications, and will provide bug fixes and security updates as necessary. We do not, however, have any current plans to release new versions of our CS applications.

Although the company tends to portray this as a move to the cloud, that is not accurate. Applications like Photoshop, Dreamweaver and InDesign remain desktop applications, though there are some cloud-like benefits like collaboration and settings synchronisation. The big difference is that you will no longer be able to buy the latest versions outright, but only by subscribing to Creative Cloud. Once your subscription lapses, you can no longer use them.

What the pros and cons? Let’s start with the positives:

  • Subscription income is good for the vendor, because it is predictable and continuous.
  • The vendor is relieved from the pressure of the upgrade cycle: having to come up with new features every eighteen months (or whatever the product cycle is) that are sufficiently compelling to persuade existing users to pay for another round of upgrades. Instead, it can take an iterative approach, more inline with Agile development methodology that prefers iterative development to big releases where many things change at once. At best, this could mean that software vendors focus more on what users want to see improved, rather than working with the marketing department on how to design a new look and features that will drive upgrades.
  • Customers can save money if they they do not need the product continuously.
  • Users always have the latest version of the software.
  • While subscribed, users have a relationship with the vendor that includes some level of service. Your software is never out of support (though a product could be withdrawn, as may happen to Adobe Fireworks which is not being updated).

Negatives? There are a few.

  • Customers may end up paying more. Most companies will calculate subscription costs such that the overall income is at least the same and probably higher than with outright sales, otherwise shareholders will not be happy. The kind of user who is happy to skip upgrades for a version or two will lose most.
  • Users have an ongoing dependency on the vendor. If the vendor discontinues the service for any reason, you no longer have the software. Depending on how the subscription is enforced technically, this injects some uncertainty into whether the software you use today will still be there to use tomorrow. Put another way, this is not going to work unless you have a high level of trust and confidence in the vendor.
  • Customers lose the psychological satisfaction of software ownership. No more “it’s mine, all mine”. You are now renting.
  • The vendor, financially secure thanks to continuing subscription income, may lose the incentive to work energetically on improving the software. Of course if there is a rival subscription service with a similar offering, the competitive drive continues, but that is not always the case.
  • Vendors could lose sales if customers are unwilling to buy by subscription, and turn to competitors who still offer perpetual licenses.

Software by subscription is not new. Customers on schemes such as software assurance also have something similar, though it is different because the license in that case may be perpetual – you can continue to use it even if you drop out of the software assurance scheme.

Today though, fast data connections and always-on internet make software by subscription easier to manage for both customers and vendors. Vendors that can successfully move to this model will want to do so, as for the vendor there are no disadvantages other than the risk mentioned above, that customers will not be willing to subscribe. Get used to it.

Creative Pros prefer iOS says Adobe, explaining lack of Android support in new apps

Adobe has shown a new touch app for Kuler, its web application for creating and choosing colour themes, which will be available in June.

image

I asked Scott Morris, Senior Marketing Director of Creative Cloud, about Android and whether apps like this will also be supported there.

“That is coming out to begin with at least only as an iOS app,” he told me. “For PhotoShop Touch and Adobe Ideas we do have those avaialble both for iOS and Android. What we do know is that there’s very few creative pros using Android tablets. There’s many more who are using Android phones, but more still using iPhones.”

Morris says that no decision has yet been made on porting the Kuler app to iPad or Android, but adds, “we are going to start with iOS as we are with most of our apps now because that is the most popular platform for creative professionals.”

Perhaps not surprising given the popularity of Macs among designers, but disappointing for Android users.

A secondary question is whether Adobe is using its own cross-platform app tools, either Flash or PhoneGap, for Kuler and future apps. The web version of Kuler is being converted from Flash to HTML, making PhoneGap a possibility. If it is, then you would have thought extending support to other platforms would be a no-brainer.

Adobe announces next Creative Suite, now called Creative Cloud

Adobe has announced the next version of its all-conquering Creative Suite, now renamed (or subsumed into) Creative Cloud.

Availability is set for June 2013. There will not be any perpetual licenses for the updated applications:

Can I purchase a perpetual license for the new Creative Cloud (CC) desktop applications that were announced in May 2013?

No. The new CC versions of the desktop applications are available only through Creative Cloud offerings for individuals, teams, and enterprise. We do not have any current plans to release future CC tools outside Creative Cloud.

Let’s start with the important stuff. I like the new “totems” which are intricate and abstract; but I think it works. Here is Creative Cloud:

image

and here is InDesign, wow:

image

Here is Premiere, can you see the lettering?

image

So what about the technical stuff? Here is quick tour of what’s new.

Adobe always seems to demo Creative Suite on the Mac these days, but says there is feature-parity between Mac and Windows. GPU acceleration of algorithms (such as in the Mercury engine) no longer uses NVidia Cuda but rather Open CL for best cross-platform compatibility.

Typekit Fonts can now be installed on your desktop, and once installed work like any other font – you can use them in Microsoft Office, for example.

image

We quizzed Adobe about what happens to the fonts if you stop subscribing to Creative Cloud. The answer seems to be that you must no longer use them, but whether this is technically enforced is unclear.

Settings synchronisation is a theme across a number of apps including Dreamweaver and After Effects. This touches on a curious aspect of Creative Cloud: despite the name, the applications are desktop applications. Sync settings means you can log in on any machine with the suite installed and get your settings back, including for example web sites in Dreamweaver. The consequence is to bring the make your desktop experience more cloud-like in respect of working from anywhere.

image

Photoshop gets an amazing camera shake reduction feature. Camera shake is a big problem for me, as I rarely have a tripod. The new feature detects how the camera moved during the shot and compensates accordingly. The demo worked great on Adobe’s sample shot, but then it would, so it is not until we get to try this with some of our own images that we will know whether Adobe’s claim of “making unusable images usable” is justified. Still, Adobe has a good track record and I am optimistic.

Other interesting features are a filter for Camera Raw, and a “straighten” effect for perspective distorting in images such as those of tall buildings which look as if they are leaning (though I am sure I have seen ways of handling this in earlier versions too). There is also an rounded rectangle editor, a new artefact removal feature, and the ability to upsample an image so that your low-resolution bitmap magically becomes more suitable for print.

There will no longer be an Extended Photoshop. If you have it, you have it all.

The Kuler colour theme chooser has been rebuilt in HTML.

image

Illustrator gets a CSS properties panel.

Flash has a Publish feature which converts Flash to HTML (We can see where Adobe is going with this). This uses the CreateJS framework; it does not convert ActionScript.

Premiere Pro now includes the engine from Audition for advanced audio editing within the application.

image

Edge Animate is able to animate a sprite across a Motion Path curve for some cool effects.

image

Fireworks is still in the suite, but is not being updated. Bad news for Fireworks lovers.

Dreamweaver has a new CSS designer, and a Fluid Grid Layout for designing adaptive web sites:

image

image

After Effects now embeds the Cineware 4D engine, which is big news if you use both AE and Cineware (as many do).

image

InDesign is now 64-bit with an updated user interface.

image

InDesign also has a “favourite fonts” feature making it easier to manage a multiplicity of fonts on your system.

What have I missed? A lot, no doubt; but I am impressed with how well Adobe has managed its transition from mainly perpetual licences to mainly subscription, how it is rapidly adding features to Creative Cloud, and how it has also managed the transition from Flash to HTML.

Fixing slow network or wi-fi in Windows 8 with Hyper-V

I had an annoying problem with my Samsung Slate running Windows 8. I use it while traveling, and every time I connected to a different wi-fi network, or even woke it from sleep while on the same network, I would get several minutes pause while Windows tried access the network. During this time, applications like Internet Explorer and Outlook might freeze and show “not responding” messages. Patience was rewarded though, and eventually the network kicked into life and everything worked normally. Until next time.

This is annoying so what is the reason and the fix? The high level view is this:

  1. When you enable Hyper-V in Windows 8 it makes changes to your networking, including creating virtual Ethernet adapters, and unbinding TCP/IP from the physical adapter. If you install the Windows Phone emulator you also get a virtual Ethernet adapter. If you have wi-fi you also get a Network Bridge.
  2. The consequence of (1) is that networking might not work so reliably after Hyper-V is enabled.

The high-level answer then is to remove Hyper-V. That works, but you might want to use Hyper-V, so better still is to fix the problem.

The answer seems to be in a hidden dialog. To get to it, open Control Panel and search for Network , click View network connections. This will show all the stuff Hyper-V has created. Now press the Alt key on the keyboard to show the Advanced menu, and select Advanced settings.

NOTE: if you have a slate without a physical keyboard, this menu is doubly difficult to find. The Windows 8 touch keyboard has no Alt key. Microsoft decided it was more important to have a Smiley key, and could not fit in both. The fix is to go into Change PC Settings – General and enable “Make the standard keyboard available”. It is still not that easy to display the Advanced menu in Network Connections, but it can be done.

Here is the dialog:

image

Now, if you have the problem with slow networking, you will probably find (as I did) that there is an Internal virtual Ethernet adapter, bound to TCP/IP, listed above the external virtual Ethernet adapter. The internal network cannot connect to the internet:

The Internal type is not bound to a physical network adapter. It is typically used to build a test environment where you want to connect to the virtual machines from the host operating system, but do not want to allow virtual machines on the host to communicate with external networks.

It is plausible that if the internal network has priority over the external network, Windows will struggle to connect to the Internet.

I changed this so that the external virtual Ethernet adapter, bound to TCP/IP, comes at the top.

image

This has helped with my problem, though there is still a bit of uncertainty about how to optimise the settings in this dialog. What about the Provider Order, what is the correct setting? Should the Microsoft Remote Desktop Session Host Server Network Protocol really come first in the list, as per the default?

image

Someone asked on the official forum and did not get an answer. I suggest you leave well alone unless you know better, but would be interested in someone has informed guidance.

Finally, note that if you create a new virtual adapter in Hyper-V settings, you may need to revisit the binding order.

I have never come across this issue on Windows Server, though in principle it might be the same. Odd.

Updated with instructions for enabling the standard keyboard layout.

Billion dollar revenue or not, Microsoft Azure is growing fast

Is Microsoft Azure now a billion dollar business? Maybe, maybe not. The milestone was announced by Curt Anderson, CFO for Server and Tools at Microsoft, in this Bloomberg piece:

Microsoft Corp. (MSFT)’s Windows Azure software and related programs have surpassed $1 billion in annual sales for the first time … Microsoft’s $1 billion sales figure includes Azure, as well as software provided to partners to create related Windows cloud services, Anderson said in an interview.

The remarks have prompted discussion of what exactly makes up this billion dollars of sales. In particular, what is this software sold to partners for “related Windows cloud services” and how much is it worth?

Timothy Prickett Morgan on the Register takes the most sceptical line:

It seems likely, however, that the bulk of that revenue figure comes from peddling Windows Server, Systems Center, SQL Server, and any other wares that service providers, telcos, and hosters have bought to build Windows-based clouds.

It’s hard to imagine it being even a 20-80 split for Azure proper versus Azure-alike, and the ratio is probably something on the order of 10-90 if you put a gun to our head and made us guess. And maybe more like 5-95.

He overstates the case though. Context: Server and Tools earned revenue of over $18bn in the Microsoft’s last financial year ending June 30 2012 and is set to exceed that in 2013. As Mary-Jo Foley reports here, System Center (which forms the basis for Microsoft’s “private cloud” offering) was already over $1bn last year, so it seems unlikely that Anderson would now lump System Center revenue in with Azure and call it Azure revenue.

At the same time, the qualification in Anderson’s statement does imply that Azure on its own, without this “software provided to partners” does not quite make it.

It matters little. It is clear to me that Azure is a rapidly growing business for Microsoft, and that the energy put in by Scott Guthrie and his team is paying off. Check his blog for a stream of strong announcements.

Server and Tools boss Brad Anderson told me that Azure is a “massive public cloud that doubles every six months.”

It makes sense too. If your business runs on Microsoft’s platform and you want to scale into the cloud, Azure is a strong contender now that its usability and features are maturing. Azure Virtual Machines, providing infrastructure as a service, are of key importance; note that while they have been available for a while they only came out of preview officially on April 16th, a couple of weeks ago. Azure Active Directory and the possibility of federation with on-premise AD is another critical feature, and so is virtual networking, which became generally available at the same time as the Virtual Machines.

On the other hand, Prickett Morgan’s response and other exclamations of surprise around the web (Say What? says Gigaom) show the extent to which Microsoft botched the Azure launch back in 2008 and 2009, and how far it has to go before it is perceived as a strong cloud platform contender beyond the circles of Microsoft partners.

Amazon Web Services on the other hand won its cloud reputation years ago and shows no sign of letting go of its lead, with energetic development of its platform that at least matches Microsoft’s efforts as well as commodity pricing.

Still, with both Office 365 and Azure now booming, it seems to me that the time when you could laugh off Microsoft’s cloud efforts has passed. Expect an unqualified $1bn revenue for Azure before too long.

RAD Studio XE4 with Delphi for iOS is here. Who will use it?

Embarcadero has released RAD Studio XE4, its suite of development tools for Window, Web and for the first time, Apple iOS. iOS support first appeared in an earlier release, but in preview, and the current effort works using a new LLVM-based ARM compiler so is somewhat unlike the preview. Individual products such as Delphi XE4 are also available separately.

Looking at what’s new in Delphi and C++ Builder in XE4 it is apparent that iOS support is by far the main change since RAD Studio XE3, though there are two other significant changes:

  • Prism, a version of RemObjects Oxygene that compiles a Delphi-like language to .NET (and soon other targets) has been removed. Oxygene lives on at RemObjects.
  • FireDAC, a data access engine acquired from DA-SOFT, is now part of RAD Studio.

I ran up the new RAD Studio on a Parallels VM on a Mac, a VM on a Mac being the best way to try cross-platform development for OS X and iOS. The new IDE immediately presents you with instructions on setting up for iOS development (though I am not a fan of videos, preferring clear text instructions) but I no problems configuring the Mac agent (called PAServer) which makes this work. Start a new mobile app and you can pick a starter template or begin with a blank canvas.

image

I picked the Tabbed Application and was soon trying out my new app on the iOS simulator

image

So far so good, though the ability to run up a quick app is no proof of the quality of the development tool. Still, a few reflections.

As I noted earlier, it seems to me that Delphi developers are either Windows developers using the tried and trusted VCL (in which case there is very little for them in XE4), or developers who are targeting mobile platforms and using the cross-platform FireMonkey framework in order to share code between Windows, Mac and mobile. I guess it is also possible that developers targeting iOS alone will be so taken with Delphi or C++ Builder that they will come in as new users.

VCL developers now have 64-bit compilation and a mature framework, and given that the efforts of Embarcadero are now focused elsewhere, and that even Microsoft is going slow on new features for what it now calls “desktop Windows”, there is little reason for such developers to upgrade.

The key questions then are about the quality of the FireMonkey framework and the iOS support. It is hard for me to be objective, since I know Delphi from of old and it is a familiar environment. Delphi or C++ Builder for iOS has obvious attractions for such developers. I would be intrigued though to know what an Objective C or even a JavaScript developer would make of Delphi, coming to it fresh. I am sceptical whether an Xcode developer would find enough productivity benefit in Delphi and FireMonkey to want to move over, and suspect also that many would not be impressed by the FireMonkey approach to iOS controls, which are generally custom drawn rather than true native, or faked completely like the Segmented Control which you are meant to put together from SpeedButtons with segmented styling, as explained in the Delphi iOS tutorial:

image

Embarcadero is making a big play of being “true native” but native is not just about the executable code (I have written more about this elsewhere) and cross-platform always involves compromise.

There is also some disquiet in the developer community about the cost of keeping up to date with RAD Studio. The full RAD Studio XE4 Architect edition currently costs £2,892.60 ex VAT for a new user, or £1,927.80 to upgrade. If you just want basic Delphi, Delphi XE4 Pro is a more reasonable £642.60 for a new user, or £352.80 to upgrade – but you do not get iOS support for that, that is another £320.40 for the Mobile Add-on, and FireDAC if you need it a further £285.00. When XE3 came out, Embarcadero promised that iOS and Android support would be available later at a “low cost”; of course that is a relative and subjective term, but I can understand if some feel that the price is on the high side. Or you can buy software assurance and get upgrades free; I don’t have prices for that but the cost is significant.

It is unfortunate for Embarcadero that there is intense competition in the iOS tools space, not only from Apple’s excellent and free tools, but also from the likes of Xamarin and Titanium.

None of the above is intended to detract from the achievement of bringing Delphi to iOS, with Android promised, which is considerable.

Changes in the Delphi language for ARM and mobile support

Delphi developers should note changes in the Delphi language coming as a result of the move towards the LLVM compiler for mobile support. Embarcadero has released a paper describing these in detail. The just-released RAD Studio XE4 includes the ARM compiler for iOS, with an Android compiler to follow later this year.

It seems to me that Delphi developers will now fall into two broad camps:

1. Windows VCL developers for whom the new FireMonkey cross-platform framework is of little interest, either because they are not developing for Mac or mobile, or because they prefer other tools for those platforms.

2. Developers who are embracing the new platform targets, migrating code to FireMonkey or starting new projects there, and planning to share code across all platforms as far as possible.

If you are in the first camp, you need not worry too much about language changes yet. I believe it is Embarcadero’s long-term intention to unify Delphi’s compilers around LLVM on all platforms, but when or whether this will happen for Win32 and Win64 is moot; my guess is that what the company now calls the “classic compiler” will be around for a long time yet. However the Mac compiler may migrate to LLVM sooner. (I am speculating).

Currently, RAD Studio XE4 includes five compilers:

  • The Win32 compiler (DCC32)
  • The Win64 compiler (DCC64)
  • The Mac compiler (DCCOSX)
  • The iOS Simulator compiler (DCCIOS32)
  • The iOS ARM compiler (DCCIOSARM)

Of these, only the last one currently uses LLVM, though the iOS Simulator compiler behaves as closely as possible like its ARM cousin. In general the language changes are currently only applicable by default for the LLVM and Simulator compilers as far as I can tell.

What are the language changes? My quick summary of the biggest changes is as follows:

  • One string type only: UTF16, reference counted, immutable (though this is a point of confusion; reading the paper it seems it is not yet immutable as it describes modifying in place, but may become so).
  • 0-based strings. There is a compiler directive $ZEROBASEDSTRINGS, which is off for Delphi XE3 and Delphi XE4, but on for the mobile compiler in XE4.
  • Automatic reference counting. Objects are destroyed automatically when the reference count hits zero. MyObj.Free; does not destroy the object, only reduces the reference count (and destroys it if zero). You can create weak references (which do not increment the count) by using the [Weak] attribute. If you really want to destroy the object, use MyObj.DisposeOf;.

In addition, the With statement is now deprecated.

The language changes are described in detail in the paper The Delphi Language for Mobile Development, which you can find here.

Key Easy Assist feature of Microsoft InTune disabled on Windows 8, when will it return?

Microsoft’s cloud PC management service, InTune, is aimed at smaller businesses and the resellers who support them. It brings some of the features of System Center to organisations who are too small to justify deploying it, or who want a simpler solution.

One of the features of InTune is remote assistance. End users click a link on their InTune Center and it fires off an alert to an administrator.

image

When the adminstrator responds they can open up a chat session with the user, with other features including the ability to transfer files and (crucially) to view and control their desktop to troubleshoot problems.

This feature is not the same as the Remote Assistance built into Windows 7. Rather, it is based on Office Live Meeting 2007 (yes, 2007). It is tailor made for remote support, and easier for the end user to initiate.

Those who have tried to use the standard Remote Assistance (which is fine when it works) will be familiar with an intricate dance that starts with helping the user to find it, then talks them through trying Easy Connect, then when that doesn’t work, emailing an invitation file, then quoting the secret password, then verifying it when it doesn’t work, then giving up and blaming firewall issues.

Easy Assist by contrast is straightforward. At least, unless you have Windows 8 on either end. If the administrator is running Microsoft’s latest and greatest they get this message from InTune:

image

It says, “Launching Remote Assistance is not available on this operating system.”

Bewildered admins turned to the forums for assistance. The answer from Microsoft is a classic piece of support doublespeak:

Your account was likely upgraded to our latest release last week, which includes some changes for users on Windows 8. We made some changes to ensure the best experience when supporting customers.  To ensure the best experience on Windows 8 it was necessary to disable support for providing and receiving remote assistance.  This is a feature we want to implement in a future release as we know how valuable it is.

Note that the admin in question says “I often use this feature several times a day.”

This is Microsoft at its worst. It is not just that an important feature was removed without notice. It is also that there is no indication of when it might return, or any guarantee that it will return. The support company now has to explain to its clients why they now have to struggle with the standard Remote Assistance, or else pay extra for a third-party solution like the excellent but expensive LogMeIn. This, of course, will no longer be integrated with InTune.

One might also ask: why does the relatively new InTune product still rely on a feature of Office Live Meeting 2007 for this key functionality? Why is it not part of Lync, which is its replacement now in its second version?

I guess this will eventually be fixed. In the meantime, pleas like this go unanswered.

Easy Assist fix it for Windows 8 Already!!! This is ridiculous Windows 8 was available on Intune back in September of 2012. It more than six months and only the agent works correctly now. Easy Assist is a big selling point for clients to get the Intune Service. I also have a large number of existing Windows 7 customers on Intune who refuse to go to Windows 8 because they will lose functionality.

Microsoft shrugs off Windows 8 issues with record revenue

Yesterday Microsoft released its financial figures for the first three months of 2013.

Quarter ending March 31st 2013 vs quarter ending March 31st 2012, $millions

Segment Revenue Change Profit Change
Client (Windows + Live) 5703 +1070 3459 +480
Server and Tools 5039 +508 1979 +293
Online 832 +125 -262 +218
Business (Office) 6319 +477 4104 +307
Entertainment and devices 2531 +913 342 +570

Note that the figures for Windows and Office are boosted by deferred revenue from upgrade offers. The PC sales decline will be reflected in Windows client sales next time round.

CFO Peter Klein spoke of hoped-for improvements in Windows 8 device fortunes based on refinements coming in Windows “Blue” as well as more power-efficient CPUs coming from Intel. “We are confident we are moving in the right direction,” he said.

He also discussed the new subscription-based model for Office. Office 365 has added five times more subscribers this quarter than in the same period last year, he said, and revenue exceeds $1 billion.

Suh said that System Center revenue is up 22% and that Hyper-V has gained 4 points of market share in the year. Lync and SharePoint are also growing.

In answer to a question about Surface, Microsoft’s own-brand tablet, Klein spoke about a coming “broader array of Windows 8 devices including lower price points.” 

The deferred revenues disguise what would otherwise be a decline in Windows sales, but in other respects these figures are remarkable, particularly in a difficult economy.

Isn’t Windows 8 a failure, and won’t declining PC sales take Microsoft down too? It is possible, but so far the company has proved resilient. Perhaps the most significant positive here is that both Office 365 and Azure are working for the company, which means that cloud computing is not killing Microsoft’s business in the way that some speculated.

No more Delphi for .NET: Prism removed from RAD Studio XE4

Embarcadero is removing Prism from the next version of RAD Studio, XE4, expected later this month.

Prism is actually a third-party product, based on RemObjects Oxygene. Prism and Oxygene let you code in Delphi and compile to .NET or Mono.

Marc Hoffman from RemObjects explains the change here:

Starting with the upcoming release of XE4, Embarcadero Prism will no longer be part of the RAD Studio SKU, and there will be no “XE4″ branded edition of Prism.

But worry not. As you all know, Prism has been nothing more than a re-branded version of our Oxygene for .NET product — and Oxygene will keep going on, stronger than ever.

In fact, Oxygene has long outgrown its Prism-branded edition, first when we introduced full native support for Java and Android to the language over 18 months ago, and of course with our upcoming support for truly native iOS and Mac apps, shipping next month.

The disappearance of Prism is the final chapter in the story of Delphi for .NET. Borland’s Delphi was first released in 1995, and combined a visual interface builder superficially similar to Visual Basic with a native code compiler, enabling full access to the Windows API  as well as better performance than Microsoft’s VB.

Delphi built up a strong following, but in 2002 when Microsoft brought out the .NET Framework Borland worried that Delphi would be left behind. In 2002 it brought out CSharpBuilder, an IDE for C# targeting the .NET Framework, and in 2003 Delphi 8 which also targeted .NET.

Other .NET versions followed, but whereas native code Delphi was a compelling alternative to runtime-based platforms like VB and .NET, the .NET versions of Delphi were less distinctive. Developers coding for .NET preferred Microsoft’s Visual Studio, while Delphi developers preferred to stick with native code.

When Embarcadero acquired the Delphi tools from Borland in 2008, it dropped .NET support from Delphi itself and replaced it with Prism.

I doubt that the disappearance of Prism will cause much consternation. Prism developers will simply switch to Oxygene instead.