I guess what I'd like to see is a breakaway from the notion that there can only be one, universally adopted standard. We should focus on building systems that are heterogeneous, not homogeneous. Ideally, we would have a world where IP packets were routed correctly regardless of version; websites could be programmed in any language; and transactions could be conducted in any cryptocurrency.

One way to achieve that is by adopting a very minimal standard, and then creating new models that targeting that standard (see: IPv6->IPv4 gateways, compile-to-JS, sidechains). The problem is that the standard is often not minimal enough, or is minimal in the wrong ways, or is too minimal to be of practical use. So I don't believe that this is the right approach; it's just too difficult to predict how people will use the standard.

1995 saw Java's first public release. PHP was a CGI-thingie that powered Rasmus' personal homepage. Tcl and Perl was the state of the art of scripting languages. Ruby was released (it would be another four years before it started getting traction outside Japan). The first edition of O'Reilly's "Programming Python" was published in 1996.

Seriously, it's 20 years ago. You're operating with extreme hindsight.