[dmitriid]

> Sure you can

No you can't.

> we’re back to why vendor lock-in is bad.

Ah yes. There are some unknown theoretical HIGs that you can follow which don't exist and don't reflect the actual platforms that people, you know, actually use.

This has nothing to do with blindly parroting "vendor lock in bad". Because Apple's HIGs for a long time were light years ahead of anything else, and yes, I would expect a well-designed app to follow them on the Mac (anything from accent colors, secondary focus and humane modal dialogs to affordances, accessibility considerations etc.)

Whereas "sure you can" web implementing some bogus HIGs can't even do a modal dialog right.

[wiseowise]

> No you can't.

Why and what you can't achieve from HIG?

> Ah yes. There are some unknown theoretical HIGs that you can follow which don't exist and don't reflect the actual platforms that people, you know, actually use.

Sorry?

> Because Apple's HIGs for a long time were light years ahead of anything else, and yes, I would expect a well-designed app to follow them on the Mac (anything from accent colors, secondary focus and humane modal dialogs to affordances, accessibility considerations etc.)

What does this have to do with native vs web argument? The topic is here what and what you can't achieve with both technologies.

> Whereas "sure you can" web implementing some bogus HIGs can't even do a modal dialog right.

???

[dmitriid]

> Why and what you can't achieve from HIG?

I gave you examples, and you dismissed them because "vendor lock in is bad" and "I don't see what this has to do with native vs web".

> ???

There's no modal dialog on the web that conforms to any of the existing HIGs. And while you can implement one, the amount of effort is ridiculous. Compared to native.

And that goes for almost literally everything. For example, there's a reason 99.9999% of the thousands of dropdown re-implementations fail even the simplest of accessibility checks.