---
title: "Discussion on \"Learning Vue as a React dev\" | Hashnode"
description: "Discussion on \"Learning Vue as a React dev\". Here are my thoughts"
url: "https://hashnode.com/posts/learning-vue-as-a-react-dev/64643001941b10d868a2c75e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Learning Vue as a React dev](https://tresorama.hashnode.dev/learning-vue-as-a-react-dev?utm_source=hashnode&utm_medium=feed)

Here are my thoughts

May 17, 2023 · 10 min read · tresorama.hashnode.dev  
Read the article

-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#vuejs](https://hashnode.com/tag/vuejs)
-   [#learning](https://hashnode.com/tag/learning)
-   [#learning-journey](https://hashnode.com/tag/learning-journey)
-   [#frontend-development](https://hashnode.com/tag/frontend-development)

## Written by

[Jacopo Marrone](https://hashnode.com/@tresorama)

@tresorama

  
[View profile](https://hashnode.com/@tresorama)

## Responses 1

Markdown supported · ⌘↵ to post

[Jordan Brennan](https://hashnode.com/@jfbrennan)

[May 17, 2023](https://hashnode.com/posts/learning-vue-as-a-react-dev/64643001941b10d868a2c75e/comment/64644e19bb615ac11d9953c2)

I find Vue’s Single File Components with Options API to be the easiest to learn, design, code, and test. Its simplicity compared to React or even Vue’s own Composition API is way more valuable than all of React’s exotic stuff that at the end of the day doesn’t help you achieve anything new. It’s just more code and goofy rules to work around. Also, Vue’s real HTML and CSS trump React’s XML abomination and total lack of support for component styles too.

The final nail in React’s coffin is its persistent incompatibility with web standards. To this day it is not fully compatible with Web Components and fails, and has failed many times, to handle certain HTML attributes correctly. If your web framework struggles to work with HTML that’s kind of a sign right?

I have years of experience with both and would choose Vue over React always.

[Jacopo Marrone](https://hashnode.com/@tresorama)

[May 18, 2023](https://hashnode.com/posts/learning-vue-as-a-react-dev/64643001941b10d868a2c75e/comment/64644e19bb615ac11d9953c2#reply-64656bcdeb43c7e4ebcfd813)

Really appreciate your honest feedback Jordan. Vue has the plus to be more similar to HTML and you can use it just in a static file using CDN. In React you can't bypass a build tool.

> To this day it is not fully compatible with Web Components and fails, and has failed many times, to handle certain HTML attributes correctly.

I'm curious, which problem did you encounter with React and WebComponents, and React and HTML attributes?

[Jordan Brennan](https://hashnode.com/@jfbrennan)

[May 18, 2023](https://hashnode.com/posts/learning-vue-as-a-react-dev/64643001941b10d868a2c75e/comment/64644e19bb615ac11d9953c2#reply-6465738d7bd6d2e2dc87012a)

React currently does not support the `inert` attribute or fully support `hidden`. React has a long history of unreliably working with HTML because of its flawed design. React maintainers have forced themselves into a corner where they have to manually update React alongside HTML so if HTML gets something new, like `inert`, developers can’t use it until React is updated, which is often AFTER the browsers support it. React is effectively the new IE.

It also doesn’t understand Web Components without configuration and some extra coding and even then it’s still not perfect. [custom-elements-everywhere.com](https://custom-elements-everywhere.com/#react) shows a failing score compared to virtually every other framework, which all score 100%.

[Jacopo Marrone](https://hashnode.com/@tresorama)

[May 18, 2023](https://hashnode.com/posts/learning-vue-as-a-react-dev/64643001941b10d868a2c75e/comment/64644e19bb615ac11d9953c2#reply-6466591ceb43c7e4ebcff846)

[Jordan Brennan](https://hashnode.com/@jfbrennan) Never heard of `inert` attr. It seems that you can use it like this:

```
<div inert={isInertOn ? "": undefined}/>
```

[github.com/WICG/inert/issues/58](https://github.com/WICG/inert/issues/58#issuecomment-618016847)

But yes, React compiles to html so dev must rely on the compiler support.

---

I don't often use Web Components but I agree that is a shame that an industry leader library lacks in fundamentals.

It seems that something is moving here [github.com/facebook/react/issues/11347](https://github.com/facebook/react/issues/11347#issuecomment-1122275286)

---

Is a shame that an industry leader library lacks in fundamentals.

This is a weird thing, hard to accept honestly, even if 95% of apps never encounter these problems it doesn't mean that these should be ignored.

Great points here Jordan.
