standards-compliant

Chrome is super fast, finally has some ad-blocking, syncs my bookmarks (though that's not perfect), and is standards-compliant.

With only a bit of extra state-machine glue, you'd have a clean and standards-compliant websocket -based VPN.

First problem is that the SQL standard provides no way to make this work portably on any standards-compliant database.

Also, when it came out, IE6 was the most standards-compliant browser and generally performed better than its main rivals.

Seriously, folks, making a standards-compliant browser is a critical path item to not losing the 21st century to Google.

We now get the ability to change transports based on client (so our API clients get the very fast standards-compliant node `ws` library, while browser clients get engine.io).

Nice one but: >It's not standards-compliant Why?

But honestly, I can't know because he's not naming anything specific anyway, just an anecdote about how IE8 was great at being standards-compliant and safari wasn't.

It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch." Sidenote: Anyone had any experience using postgrest?

Even the most literal "new Internet Explorer" -- Edge -- is a more standards-compliant browser than Safari, which has stagnated far behind every other competitor in the list.

Is there an implementation method for the decentralized web that doesn't require individuals to become web administrators (with concerns about security, SEO and "proper standards-compliant page architecture", storage and bandwidth costs, etc.)?

"It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch." If you are using this as a web server persistence backend, I would agree with the first, more or less accept the second and reject the third.

Standards-compliant C is more portable than autotools.