41–50 of 129 posts
Vue is the one js framework that was really a breeze to learn. In most cases, your first attempt at doing something in Vue will just work the way you intuit it to work. Docs are fantastic as well. Congrats to Evan You for a stellar job
>Another important thing is that I take long breaks (several weeks) whenever I feel I need to — which is probably harder to do if I’m a full time employee at a company. A "Patreon-funded full-time job position" and the ability to take weeks off at a time? What an amazing career path Evan has taken. He sounds so passionate about Vue and he is fully funded to be able to do it. And what a good project to fund, always mo…
Isn't running a project more about the outcome than putting in as much time as possible? Also taking long breaks could potentially mean being AFK but still obsessing about next steps in the project. Maybe you're imagining him being on a tropical island drinking mochito's during the long breaks?
As far as I understand, he's not really running a company though. It's mostly a solo endeavor.
So it seems like in this case time put in ~ outcome.
Earlier quoted context omitted.
The Docs take Vue to a league of its own. I'd contend that no other JS ecosystem has docs that are as lucid, concise and beginner friendly as Vue's. This intro to VueX (Vue's state management library) is a good example: https://vuex.vuejs.org/
Are you guys all using ad blockers? I open Vue docs — and the right-hand column of the screen is a wall of ads. For comparison, I open React docs — and there are only docs there (unless you count the obligatory BLM header). With a larger font, too, because there, docs don't need to compete for page space with the ads.
Check what extensions you use, and use uBlock Origin as your adblocker.
I was turned off of Vue when they put a big "Join BLM" banner on the top of their site. In my vue, that is mixing politics and personal opinions into a public coding project. I believe this to be a non-no. It implies that those that don't share your [unrelated] views are not legitimate. In this example, it implies that those who are pro-minority rights but anti-protests are in some way less committed than their pro-r…
So I recently had the opportunity to use the new composition API, which will come in V3, in a project and want to share my two cents. The project had some limitations tho: no webpack and no typescript (so basically inline x-templates and pure browser JS). Starting of with the composition API was great. No "this", easy reuse of logic via react-like "useXYZ" hooks and a general fast development. But two things really b…
I used to prefer (and by a lot) Vue more than React because of its simplicity and completeness (router + store + everything you need). After trying to use v3 for a new project and trying out the composition API, I've gone back to React. With v3, and the composition API, to me, it lost all of its appeal (being simple, easy and complete). Now to me it has the worst of both worlds... it's not as easy anymore, has a lot…
The Options API is still the default and remained pretty much the same.
I was turned off of Vue when they put a big "Join BLM" banner on the top of their site. In my vue, that is mixing politics and personal opinions into a public coding project. I believe this to be a non-no. It implies that those that don't share your [unrelated] views are not legitimate. In this example, it implies that those who are pro-minority rights but anti-protests are in some way less committed than their pro-r…
The Django, React Router and React docs all definitely had BLM stuff.
Earlier quoted context omitted.
The Docs take Vue to a league of its own. I'd contend that no other JS ecosystem has docs that are as lucid, concise and beginner friendly as Vue's. This intro to VueX (Vue's state management library) is a good example: https://vuex.vuejs.org/
Are you guys all using ad blockers? I open Vue docs — and the right-hand column of the screen is a wall of ads. For comparison, I open React docs — and there are only docs there (unless you count the obligatory BLM header). With a larger font, too, because there, docs don't need to compete for page space with the ads.
Vue is the one js framework that was really a breeze to learn. In most cases, your first attempt at doing something in Vue will just work the way you intuit it to work. Docs are fantastic as well. Congrats to Evan You for a stellar job
So I recently had the opportunity to use the new composition API, which will come in V3, in a project and want to share my two cents. The project had some limitations tho: no webpack and no typescript (so basically inline x-templates and pure browser JS). Starting of with the composition API was great. No "this", easy reuse of logic via react-like "useXYZ" hooks and a general fast development. But two things really b…
I used to prefer (and by a lot) Vue more than React because of its simplicity and completeness (router + store + everything you need). After trying to use v3 for a new project and trying out the composition API, I've gone back to React. With v3, and the composition API, to me, it lost all of its appeal (being simple, easy and complete). Now to me it has the worst of both worlds... it's not as easy anymore, has a lot…
I've primarily moved over to Django with server rendered content and sprinkles of JavaScript where needed.
Earlier quoted context omitted.
I used to prefer (and by a lot) Vue more than React because of its simplicity and completeness (router + store + everything you need). After trying to use v3 for a new project and trying out the composition API, I've gone back to React. With v3, and the composition API, to me, it lost all of its appeal (being simple, easy and complete). Now to me it has the worst of both worlds... it's not as easy anymore, has a lot…
As far as I understand the Composition API is purely opt-in and aimed at cases where you want to trade simplicity for power/control. The Options API is still the default and remained pretty much the same.