I disagree. There has never been a better markup language. HTML allows precise control of atomic elements that make up a component. It has been the best thing for accessibility we ever came up with.
> There has never been a better markup language.
> It has been the best thing for accessibility we ever came up with.
I observe past tense in both sentences above.
So perhaps we agree, the salient question is: is it the best thing we can come up with? With a focus on the future.
I argue we can do better, while celebrating and building off of what's great about the past & present.[0]
[0] https://docs.pax.dev/intro-priorities-and-prior-art/#:~:text...
Use those same great adobe tools in a vm.
All other content representation infrastructures that weren't text first, like java applets or flash died because they were no match for HTML.
Silverlight sought to do this with XAML, but it had other problems (required a plugin right as plugins were on their way out; CLR was a huge dependency; too locked down and proprietary under Ballmer leadership)
Can you imagine a text-first content representation, which is visually editable with the UX of a vector design tool? This is the rabbit hole that drives our work on Pax.