Do you think that not considering Russia a main cyber threat is a wrong decision? Why?
Article gives no clear answer to why would it will make everything worse.
It does, however, speculate on how it may be a bad decision, but no one knows for sure.
> Your Markdown- based content generates semantic HTML
HTML is far more expressive in semantics, so using markdown to get html means you will never be able to get most semantic things you actually wanted.
React couples the structure, styling into js components only if you make it so. You can just write style.css, import it and refer to it is classname as `className="my_custom_class"`.
And there is no clean separation of concern when it comes to html, css and js. You can force to separate them, but that would be a separation of technologies, not concerns - they are too intertwined to be separated.
And the example of island on the tutorials proves that:
```
<form @name="contact-me" @submit.prevent="submit" autocomplete="on">
```
There is no way to create a standard-first framework without introducing some form of DSL. This doesnt look like html, this doesnt look like js, and it is def not primarily css based anything.
___
The project is nice, using new features like starting style, view transition - instead of js based solutions is cool. There are a lot of experimental features, like popover api. The browser support is low and those things are not production-ready for everyone (maybe for some).
The approach is good, the site is good, the docs are good, but I dont like the distinction from competitors. Like I can use all those features in react/vue/astro/qwik. What makes you unique? Being able to apply web standard solutions? How about something along the lines - we create better primitives so you can create you website faster/easier?
Opened a website.
Already got `Welcome to our website!` modal that block the content.
Through the modal's overlay can see the banner `Your product could be here`.
Well, that is annoying. Thank you so much, I would rather use anything that is less intrusive.
It is the same div soup for a screen reader, because there is no behavior attached to those new tags.
They can not be a landmark, there are not marked as headings, they have no roles.
Just a container with a text.
And to attach the behavior you need to use javascript.
So without js it wont work.
Why bother and try yo create half-baked non working solution if you can just use html?
Well, it easier to style, maybe. But hey, there is a class attribute.
No, they don't.
Aria roles are not for making one tag to work like another. (Otherwise what is the point of having different tags with different semantics?).
Aria is for making inaccessible html more accessible.
Links can not be disabled (buttons can) - so they dont rely on js to work;
Buttons rely on js (except for submitting the form).
There is no way to interchange one with another without sacrificing usability.
Article gives no clear answer to why would it will make everything worse. It does, however, speculate on how it may be a bad decision, but no one knows for sure.