Are any of these newer templating languages worth me switching?
Of course, you'd need to get over the lunacy of loading a full DOM transformation library into the browser DOM.
but that just aside. the last time this was discussed a year ago i actually tried to find a working solution to load xslt through javascript and could not find any.
i only got as far as verifying that js can be loaded from an xml mimetype. xslt implementations in js also exist. what's missing is the wrapper code to load the xslt library and run it over the xml and xslt files.
perhaps now with this seriously being needed by a few sites someone will have the time to get this working.
It would be conceptually nice to me to use wherever the puck is going in terms of a templating language that can work in the browser also.
The problem is that XSLT has so few users that the browser writers don't want to waste any more time on it. Those few people who wrote their site around it will have to either rewrite it to use something else or add some third party webassembly implementation themselves.
So an XML document would be parsed and processed by the XML engine, trigger XSLT processor, which would then trigger again the XML processor again and the HTML processor.
So XSLT processing for XML/XHTML is deeply embedded. Dropping it removes a lot of corner cases that AI is good at exploiting.
Step 1: Gain browser monopoly
Step 2: Generate fake security scare
Step 3: Gaslight everyone that only way to mitigate is to get rid of it completely like Flash.
Step 3a (corollary): There isn't anyone available that can fix the bugs because we spent all resources on UI/UX experimentation
Audio however was a crapshoot for years, especially for games.
Even basic WebAudio took until 2015, and the final piece to match Flash being AudioWorklet was only first available in 2018(Chrome) and took until April _2021_ land in Safari.
So before 2021 you needed to either write your own abstractions to support multiple API's with different execution models with so-so capabilties to be somewhat on-par with what Flash provided or even for years resort to simpler solutions (ie just samples).
I wouldn't say poor. Adobe had its own creative-software empire to up-keep. Photoshop, Illustrator, After Effects, and its web-authoring products gave it enormous influence over creative professionals. Macromedia's Dreamweaver and Flash were serious competitors in web design and interactive media. Adobe needed the missing monopoly cards; Flash, Fireworks and Dreamweaver were them.
Flash was security ridden yes, Flash required a plugin, yes; I don't think supported AppleOS at the time. These could of all been solved but I would agree that to refactor the software would of been an expensive take.
Jobs + HTML5, WebGL, JS all had entered the ring and finished the blow.
I miss it. Growing up with the internet in 2003, 2010's was the end of the wild world web. 2020's was the era of walled gardens for which we now have LLM's for the theme park and we're now entering 2030 where the internet is on fire with creativity now wrung between Yes Ai and No Ai.
Domain name:
lordsephiroth.co.uk
Relevant dates:
Registered on: 18-Nov-2003
The only good thing about flash were the authoring tool but it only appealed to content (games, websites) producers, never the users.
Is that good accessibility ?
You're half right.
Yes, Jobs killed Flash. But he did it because Flash on mobile was a battery killer. And when the original iPhone came out (one of which I still have), battery technology wasn't as advanced as it is now.
Before I got my wife's hand-me-down iPhone, I had one of the few mobile phones that supported Flash. On the few occasions when I used the web browser, I lived in fear that I'd land on a web site that was using Flash because I knew it would tear through the phone's battery in less than 10 minutes.
Ever notice that the people on HN who pine for the good-ol'-days of Flash only remember games? Never the Flash ads and intrusive videos.
Jobs did the future a favor.