eviks

Why wouldn't their review system see a published extension and determine the very second it's published that it didn't match the results of a standard workflow?

It was safety-contrained from being able to realize its full potential.

What would be the careful way of installing the official extension?

That's literally impossible, with all the access to the frontier software development tools at their disposal they can ship features securely at 100x

> Points of correctness are useless without points of connection.

There are two points in a connection, and one way to sever it is to follow author's advice to "ignore them". Or you could try to learn and maybe even engage.

(also, the "non-coward" way would be to actually link to the comment so that we could try to understand how toxic / irrelevant expert peons are)

You forgot to exclude the "not usual" factors that allow monopolies to hold their position to rule Google out of the group.

For example, non-regulatory attempts at blocking of competitors, which Google does engage in due to their dominant position in mobile (of course, that's also just another better product)

How is this constructive when you're offering nothing to construct? Just saying not to be surprised.

Kid, to keep you safe I need to keep a secret. Mommy loves you, go back to sleep!

What % of all opinions of a given group are opinions about reliability, durability etc

What does it have over WT worth waiting for?

One relatively easy set of metrics - resource consumption driven by migration to resource hungrier stacks.

But in general sure, it's not like we have good databases that count and classify bugs and track their numbers and severity and determine causes so we can compare the dynamic

They don't say that because you didn't write the tests, AI did, so who knows what behaviors it thought of and wrote tests for. That's the reason these type of metrics are very bad, especially in this context when bad tests are easier to write

Give it a few centuries of evolution and maybe we'll get there

The alternative to ribbon is not menu+ quick access, it was easily customizable toolbars where you can simply drag and drop only the buttons you need in the toolbars you need at a fraction of screen space that the ribbon wastes. And no user is ever exposed to that XML garbage only a dev could love

No they don't, they appear every time you scroll even if you never use the bar. And flashing of ui elements is in many cases worse than wasting that space permanently.

It's a tragedy decades of UI research/design can't get any of the fundamental design elements right