I am just about to graduate from Flatiron Coding School in San Francisco.
One of the reasons I originally began this adventure in coding is because I am a linguist. I’ve studied (mostly on my own) about 12 languages and speak several of them fluently. I’d say one of the reasons I’ve been able to learn so many languages is because I’ve developed my own methods for approaching a new language, whether it’s Hebrew or Chinese. I thought that skill might be useful in learning how to code.
Along those lines, I was particularly inspired by what the founder of Flatiron School, Avi Flombaum, once told us in a lecture. He said his goal was not to teach us to be Ruby developers or Javascript developers or any other “x” kind of developer. He was more concerned in giving us the capacity to be any kind of developer and be able to pick up whatever knowledge and skills an eventual job somewhere might require.
So I decided to put the pedal to the metal. I’m in my 13th out of this 15 week course at Flatiron and have gone through the basics of Ruby, Ruby on Rails, vanilla Javascript and React.js. I’m currently working on my final project which consists of a Rails backend with a React frontend. Yesterday, I decided I needed a break from coding as well as a theme for this blog post. After perusing YouTube during a lunch break, I came across the channel of one of my favorite coding teachers, Brad Traversy, and was attracted to his 1-hour Vue.js crash course. Having never studied Vue, I decided it would be fun to go through his video and make the video’s Vue.js to-do list app.
Click here to see Brad’s 1-hour Vue.js beginner's crash course
React vs. Vue: A Comparaison
Overall:
The first thing I notice is that the file structure between React and Vue are very similar: each has the usual public and src folders. Inside the Vue src folder you find the components and layout folders. Both React and Vue use the Virtual DOM.
Just like React, Vue treats everything as a component. As I worked for the first time with Vue.js, I noticed Vue seemed to feel “lighter” than React with not so much “back and forth” between files as React seems to have.
I think this feeling of lightness in Vue compared to React comes from the fact that Vue still separates HTML, JavaScript and CSS on a single page. It feels like the way I did websites years ago where you had to distinctly separate out the HTML, CSS and Javascript. If you have never used React or Vue, you’d probably find Vue easier and more intuitive to use.
Documentation:
When I first started with React, I really appreciated how well-written and complete the official documentation was. However, I have to say that Vue’s is even better. The language in Vue documentation is simpler, clearer and includes free video kick-off lessons.
Learning Curve:
Although I only spent about 90 minutes with Vue, I had the feeling that besides being a “lighter” framework, it would be easier to master were I to spend more time with it. Between the very good documentation, the more “intuitive” code structure, I was feeling quite comfortable with Vue after finishing Brad Traversey’s crash course you-tube video.
Can We Have a Drumroll Please?.....
So which do I think is better after making my little foray into Vue.js-land: React or Vue?
The answer is: it doesn't matter which is better! Because that’s not the point! The point of this exercise was to prove to myself that I am now empowered and given leave--after 15 weeks of Flatiron Coding School--to learn and use any software technology I want. That is the gift, the gold and the grace I take with me as I leave Flatiron and take my next steps as a Software Engineer.
May all of you feel just as empowered--in your own way--to code out your dreams…
Namaste and Blessings,
Donny
Top comments (0)