Hacker News new | ask | show | jobs
by pixard 2701 days ago
Your complaint is that in order to understand how to do something, you need to learn that thing first? As an experienced React dev, of course you know "intuitively" how to do things in React. As a Vue dev, your examples do not make sense to me.

FWIW I have found the Vue documentation excellent, and there are plenty of resources online to learn as well.

Both React and Vue are great solutions, the approach is just a bit different. This high and mighty attitude of "my thing is great, the other thing sucks" is a detriment to everyone.

1 comments

You've totally misunderstood the example then. The point is that lots of more advanced concepts in React can be intuitively constructed from the basics. Of course you have to learn something, every tool has an API. That doesn't mean all standardisation and abstraction in the history of computing is pointless because we could all be memorising x86 assembly programming patterns ad nauseum...

And you know what attitude is a detriment to everyone? The attitude that every library in JS land is worthy of praise just for the sole reason of existing. Yeah sure writing libraries is hard, and takes effort, and getting over 9,000 GitHub stars or Twitter follows or whatever the fuck is a great accomplishment, but it's perfectly possible to harm the overall ecosystem by blindly spreading bad abstractions and inferior solutions.

I did not misunderstand it, I don't understand it at all. And I don't expect to. Because I don't know React (nor JSX). Nothing about this is "intuitive" to me (you keep mentioning this word, I don't think it means what you think it does).

There's really a few big choices for a JS framework now (and of course thousands of small ones). Calling fellow developers who use the second most popular JS framework "noobs" doesn't help your case at all.

I don't care about GitHub stars, nor Twitter follows. I do care about a tool which allows me to achieve what I need to achieve. And in the case of front-end development Vue definitely does this, in a simple to understand and performant way. Judging by its popularity many others agree.

And who gets to decide what is and isn't an "inferior solution"? Thankfully not people like you.

What the above poster is getting at is that React allows you to solve complex problems using a few basic principles. Vue has a much wider API "surface area", meaning there are a lot more special cases you need to learn to solve specific problems.
By intuitive he meant that React is mostly vanilla JavaScript, so if you know JavaScript then you know React. Basically when I code in React I never need to open the doc. Even building the most complicated view is straightforward.

With frameworks like Angular (I don't know about Vue), you always keep the doc open in background because you constantly need to look for a function signature, check what's the syntax for something or how this or that works…

As a new JS developer, I found React to be very intuitive as opposed to Vue.js. I remember trying to scour through some mastodon frontend code and it looked much more complicated.

Of course this is anecdata so take it as you will.