Node js is not an air script, so support is not for existing Air sdk? Subsidiary of a 90 Billion dollar corp doesn't qualify? Please clarify for all of the air users.
Harman Air 1.13.25 SDK Turbo FloatAnswered
Purpose for this follow up is we were asked to change to NODE due to Air being EOL However it's 100% not EOL, according to Associate Director of Harman SDK support. That was a Adobe announcement, not a Harman announcement.
So (Can you provide Harman air version for turbo float?)
The New Air sdk from Harman was just coded to specifically solve issues we're having with video, our Contact is the Associate Director of Harman Support. New SDK Released 13-Jan-2025 https://airsdk.harman.com/download/51.1.3.4
Also Addresses:
NOTE for anyone extracting this release over the top of a previous one, please delete the old 'MainWindow.nib' and 'MainWindow-iPad.nib' files from your old SDK location prior to copying the new files. These names are now used as folder names so you would get an error "Missing objects-13.0+.nib" if these did not copy properly.
Note too that 33.1.1.50 had an incompatibility with Flex applications due to the updated function signatures used in the flash.geom package, to provide the 'object pooling' functionality. To avoid further issues the APIs have been reverted, and object pooling is now provided via new method names that reflect the original names with "ToOutput" appended.
Answer
We already have an example for NodeJS. You can modify it for Adobe AIR.
We won't be doing it in the short term, but might do it after 5.0 is released for all platforms and LicenseChest is released. But supporting Rust and Swift are currently higher priorities (newer languages that currently have large user-bases).
We *will* write an Adobe AIR script. We have not written it yet. You *can* use TurboFloat with adobe AIR right now, however *you* need to write the "bindings" to talk to TurboFloat from their language (Actionscript or flex, or whatever branding they call it now).
You can *also* use the NodeJS example because Adobe AIR support JavaScript in addition to Actionscript.
Or you can “port” the Actionscript to Javascript (the languages are very similar – similar strengths, similar weaknesses, similar dialects).
Subsidiary of a 90 Billion dollar corp doesn't qualify?
Well, google is a 2.5 trillion dollar company and we haven't yet written the Go TurboFloat bindings.
But market cap doesn't mean much. Enron had a similar market cap as Samsung does now (ya know, before the CEO went to jail and the market cap went to 0). Can you draw conclusions from that similarity? No, of course not. Does a large or small market cap mean a language they “support” will continue to exist? No.
There's tons of precedents for this. Getting a vice president of a company to comment on the viability of their product is a silly exercise. (For example “Google Stadia” was a “thriving ecosystem” and “growing product” that Google “fully supported” … before they shut it down and refunded everyone their money).
You want my expert opinion of the Adobe / Harman / Samsung AIR ecosystem? It's on life support now and likely forever.
Will we support it now (and likely forever), yes. Like we still support Visual Basic 6 – a language that's 27 years old and hasn't had a significant update in all that time.
Should you invest more of your time and money developing on a “life support” language? No. But it's your time and your money. You certainly don't have to listen to someone who's been around the block a few times.
I appreciate your professional view, experience and feedback. Thank you. Greatly appreciated!
No you can not draw any relative conclusions from those comparisons regarding Harman or market cap.
My conclusions, being around the block as well, are based on one on one interaction & communication with the leadership of the support apparatus for Harman Air directly. Who are part of the eco system at this level:
*Senior Software Engineer.
*Software Project Manager.
*Director of Media Platform Solutions.
*Associate Director, Digital Transformation Services.
Do have a “ETA” for We *will* write an Adobe AIR script. We have not written it yet.
https://wyday.com/forum/t/32832/harman-air-1-13-25-sdk-turbo-float/#post-54308
Do have a “ETA” for We *will* write an Adobe AIR script. We have not written it yet.
We don't publish roadmaps. But as I stated above:
We won't be doing it in the short term, but might do it after 5.0 is released for all platforms and LicenseChest is released. But supporting Rust and Swift are currently higher priorities (newer languages that currently have large user-bases).
Understand. Path we need to embrace as well. Thank you.