Hi @adroperez, welcome to the forum
yeah I agree that’s why I also see it as an EOL from Adobe
to be honest it is kind of embarrassing for them (Adobe)
when they announced the Flash EOL (circa 25 July 2017)
that was the perfect moment to also announce either the Adobe AIR EOL
or the transfer of Adobe AIR maintenance, update and support to someone else
so it took them (Adobe) almost 2 years, more exactly 1 year, 10 months, and 6 days to realise “hey we gonna pass it to someone else”
maybe they tried to continue it but some internal stuff (whatever) prevented them to do so
maybe it took them that long to find someone else being able to maintain it without doing a butcher job
maybe … many many things
this I don’t know
what I do know is in term of licensing
searching a bit you could find those AIR distribution licenses
but those do not cover source code nor branding
If you digg a bit more you can find
Trade Restrictions on Importing, Exporting, and Using Adobe Products
and there you can find out that there are already licences planed for a company to get and modify the AIR source code
In fact, I do know from the AIR SDK 2.6 / 3.0 era few companies got access to the AIR SDK sources, think “media box connected to a TV”
So yeah if you have the budget and/or the business model for it you can contact Adobe and pay them licensing fee so you can get the sources to publish Adobe AIR on your very specific case (and yes it must cost a lot of money so not accessible to small indie dev).
But those licenses are exactly there to prevent those companies to redistribute their change publicly, or name the thing “Adobe AIR” etc.
Now, what I can guess from the announcements is that Adobe have agreed to license the Adobe AIR SDK and runtime (and so their sources too) to HARMAN, and apparently will also allow them to redistribute it (maybe? to be confirmed) under the “Adobe AIR” name/branding as the current AIR SDK and runtime we are used to get from Adobe.
Off course they will not be allowed to redistribute the source code (don’t dream), besides what is already available in the AIR SDK you already know.
The security fix are not that important when it concern Adobe AIR (those are mainly for the Flash Player).
In fact, removing some security fixes that got added to the runtime because of Flash could make Adobe AIR faster, because different context of usage/distribution etc.
At that point it can go in a lot of different directions, it would be mainly driven by what HARMAN want to do (eg. what is their interest in the runtime); For example, if among HAMRNA products they do need something that work on a specific CPU architecture (that AIR does not currently support) you could see a new AIR target for that specific CPU, or Operating System (Linux!), or really anything …
It could also go in the other direction, let assume it is extremely painful and cost a lot of money to keep supporting Adobe AIR for the macOS desktop, HARMAN may decide to stop supporting it if it does not align with their interest.
It depends on so many things:
- Why HARMAN decided to do that?
Is it mainly to support their own customers? Do they want to show up more on the radar of developers ? Pick any wild guess
- to maintain/update/support Adobe AIR runtime and SDK is not a small job
depends on the size of the team, the skills , cross-platform experience, budget, etc.
maybe they would want to do things but can’t …
- length of the licensing terms ?
Adobe will still own Adobe AIR, they are certainly not selling it
- your guess is as good as mine