{"id":1778,"date":"2019-06-13T21:28:23","date_gmt":"2019-06-13T12:28:23","guid":{"rendered":"https:\/\/n8finch2024.local\/?p=1778"},"modified":"2019-06-13T21:37:16","modified_gmt":"2019-06-13T12:37:16","slug":"learning-react-so-i-can-i-can-hang-out-with-other-things","status":"publish","type":"post","link":"https:\/\/n8finch2024.local\/learning-react-so-i-can-i-can-hang-out-with-other-things\/","title":{"rendered":"Learning React… So I can I can hang out with other things…"},"content":{"rendered":"\n

Maybe it’s FOMO (fear of missing out 😮), or I’m finally starting to see the benefit, but I’m finally getting down and dirty with React, compiling everything I need to be proficient with it, and start using on the regular. <\/p>\n\n\n\n\n\n\n\n

Wait, but why… now…???<\/em> <\/h2>\n\n\n\n

This has been a long time coming. I’ve definitely been dragged to React kicking and screaming, “I WANT TO USE VUE IN ALL THE THINGS!!!!” VueJS<\/a> is super nice and easy to use, the View\/Model interaction is intuitive, and they’ve made the hard things easy and the complex things more simple. My first 🤯mind-blown🤯 moment with JavaScript was back in the KnockoutJS days. Seeing that two-way binding work was like… fairy dust magic sauce… 😋<\/p>\n\n\n\n

BUT, there are three projects that I want to be a part of and use on the regular, which all use React under the hood:<\/p>\n\n\n\n