> My company might have 4 domains on different TLDs
Your CA would have a root cert per TLD. Alternatively, we get rid of non-cc TLD (and leave ccTLD only for truly geography-bound organizations, like governments).
Also if it's the same CA operating a bunch of different roots for different TLDs, they're likely to just make the same mistake that impacts them all. Sadly, I can't see anything like this working.
In another world, Netscape is able to reach a deal with Sun, and the JVM gets integrated into Mozilla. New browsers just need to implement the JVM and bind it with their XHTML's rendering engine DOM API.
It would have been the application platform people ask for, with a separate namespace for application-related tags so you can just switch them up with the OS's native UI controls.
Instead of that, we got Yet Another VM, WebAssembly.
Not trying to throw shade, but I think the number of devs wishing that the web ended up with XHTML + JVM (now owned by Oracle...) may just be you.
Never mind that when Microsoft licensed Java from Sun for IE3 and IE4, Sun sued Microsoft. Sun wanted to be the only distributor of Java, just like Adobe was with Flash. So, browsers wouldn't have actually included a Java runtime out of the box without licensing/paying Sun for it. I'm sure that dependency would have only gotten even better under Oracle.
Those of us old enough to remember the web with plugins, don't miss plugins.
> Not trying to throw shade, but I think the number of devs wishing that the web ended up with XHTML + JVM
I don't necessarily like the JVM, it's just the most popular system-independent bytecode virtual machine (and historically plausible). It's a lot easier to built a bytecode interpreter than a full language. As mentioned elsethread, Scheme would have been even better, with an even smaller base.
XHTML, however, full in. Namespaces and syntax checking alone would have been worth it.
> Never mind that when Microsoft licensed Java from Sun for IE3 and IE4, Sun sued Microsoft.
Microsoft was in their peak EEE era, no wonder Sun didn't want to do anything with that.
> Those of us old enough to remember the web with plugins, don't miss plugins.
That's why I didn't mention plugins, browsers would have a JVM engine, instead of a JS one.
Microsoft was definitely at their peak evil EEE era, but it isn't like Sun didn't want to exclusively own/control Java too. It was Sun that put the Java in JavaScript but wanted to ensure it stayed a toy language.
Think of how truly horrendous it would be if every browser had the JVM built in and Oracle was calling the shots on the language the whole web is written on? How much would they be charging for a license?
Anybody would be able to make their own JVM, thought (they might need to call it the ECMA Virtual Machine). And seeing how the WHATGC works, I don't think they might be able to keep any sort of control.
The EU has their own Mastodon instance, but unless you want to have responses (even if the official instance doesn't show them), it's cheaper to run a static news aggregator.
It would be nice, but it seems most people don't care about this.
I'm at the point where I think you people are just dumb. The amount of people I've worked with my in career who did things totally outside of their major in college or simply dropped out entirely. I'm literally sitting here thinking about how intellectually destitute the so called left has become and it makes me sad.
please tell me ONE app for Android other than Google Messages I can use to send and receive RCS, it surely won't be problem since it's international standard same as SMS, so there must be plenty apps available...
Pretty much all banking apps for Android won't work without Google Play Services, so once again if you are using Lineage or Graphene, you are still stuck with US company to use your European banking services on the phone.
> please tell me ONE app for Android other than Google Messages I can use to send and receive RCS, it surely won't be problem since it's international standard same as SMS, so there must be plenty apps available...
Nice red herring. The number of implementations is irrelevant here, although Wikipedia says Samsung had one too.
Your CA would have a root cert per TLD. Alternatively, we get rid of non-cc TLD (and leave ccTLD only for truly geography-bound organizations, like governments).