One thing I really like with Vue, is that it makes very clear what is specific to Vue. You migh call the props/component/data/methods object boilerplatey, but when you come to a code base you clearly have the This part is Vue and This part is regular JS.
It also provides shorthands for the most common tasks, as part of the same "We're not afraid to be a framework" philosophy.
Reach though, with its it's just JS approach, it's harder if the other dev has done something because of React or some other purposes. This leads to an unecessary amount of constructor(props) { super(props); this.state = {… for trivial things for exemple.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One thing I really like with Vue, is that it makes very clear what is specific to Vue. You migh call the props/component/data/methods object boilerplatey, but when you come to a code base you clearly have the This part is Vue and This part is regular JS.
It also provides shorthands for the most common tasks, as part of the same "We're not afraid to be a framework" philosophy.
Reach though, with its it's just JS approach, it's harder if the other dev has done something because of React or some other purposes. This leads to an unecessary amount of
constructor(props) { super(props); this.state = {…
for trivial things for exemple.