Todo App in Vue.js - The Hard Way (Ep17)

Episode 17: Building a todo app front-end.
Reading the Vue.js documentation, page by page.
⭐️ Support the channel on Patreon:
/ christopherokhravi
► Playlist:
• Vue.js - The Hard Way

[@mahmudurrahman9052]

Must say this video has quite inspired to me to dive into Vue more. thanks a lot man ! great stuff.

[@codewithfrenchy]

love this series!

[@ChristopherOkhravi]

Larger font size?

[@psybitcoin]

Loved it!

[@ChristopherOkhravi]

Glad to hear! Thanks for watching :) and thank you for the comment :)

[@cadfoot568]

I’m in love with the shape of Vue lol

[@ChristopherOkhravi]

🤣

[@Gonza2432]

thanks genius!!

[@ChristopherOkhravi]

And thank *you* for watching :) :)

[@yashjain6945]

Which code editor do you use??

[@ChristopherOkhravi]

Vim in iTerm. I would warmly recommend Vim Adventures if you want to learn vim. That’s what I used 😊 Thanks for watching and thanks for the question!

[@ChristopherOkhravi]

vim-adventures.com/

[@skillfulactor09]

are you liking vue js so far

[@ChristopherOkhravi]

I find the simplicity of it really compelling. It seems to me that it's a very suitable "first" framework to build many apps in to get it out the door as quickly as possible. Whether you will have to move to something else further down the line as you grow is the question though. Two main things worry me: (1) I'm afraid that as the app grows this embracing of mutation will come back and bite us. (2) Templates/components don't trivially compose as well as functions do. The second argument is quite well explained by FunFunFunction ua-cam.com/video/EmGfdlixQHo/v-deo.html (around 24:38). But again, for prototyping or getting up and running as fast as possible, Vue seems like a great option. But I'll have to see how my opinion develops further down this series :) Thank you for the question and for following the series! :) :)

[@zeocamo]

i feel bad when i see you use != or == in Javascript, that is for other language and is a bad feature of javascript that should not be used, use !== or === instand, and so if(thing) if you want to make should you got a truthy value, and also use ===/!== on null and undefined, there is to many cases where != or == can mess you up, if you are new or do not understand JS, and i know a lot of peoples say you can use != null to check for both null and undefined in the same time, but i think we should all write code there is easy to read and understand for all on the team, also for the poor guy who get your "100K line code base after you stop" task