<dialog> still has issues to this day that haven't been resolved - <a href="https://tane.dev/2021/02/revisiting-dark-patterns-with-the-html-dialog-tag/" rel="nofollow">https://tane.dev/2021/02/revisiting-dark-patterns-with-the-h... - of course these can be implemented in any framework but this makes is much easier - at the platform level - to make a browser unusable, and as it's platform it's of course never been fixed.
You can have fun with web components (<a href="https://tanepiper.github.io/webc-humour/" rel="nofollow">https://tanepiper.github.io/webc-humour/) but from my experience trying to build UIs with them - they end up becoming an additional abstraction that instead of just using a framework to build the entire experience, it creates annoying boundaries of having to deal with DOM attributes instead of just working with properties.
tanepiper · · focus · HN ↗
You can have fun with web components (<a href="https://tanepiper.github.io/webc-humour/" rel="nofollow">https://tanepiper.github.io/webc-humour/) but from my experience trying to build UIs with them - they end up becoming an additional abstraction that instead of just using a framework to build the entire experience, it creates annoying boundaries of having to deal with DOM attributes instead of just working with properties.