But here is some advice from an old programmer: once you start making bigger and more complex projects, you will start to make your own convenience libraries. And soon you will realize that you've built your own React-like library. But only less stable and less well thought out, because react has the huge community and maturity.
But if you only do some small functionality, or something specific with the technology, vanilla is perfectly fine.
However, if you are a single page app coder, I would definitely go for something like React.
If fact, huge projects are likely to suffer from using React, because virtual DOMs get out of hand and a lot of resources a wasted by building and rebuilding VDOM and looking for the changes.
Also, for some reason, React brings a lot of cargo-culting. Many don't stop to thing whether they should even if they can. They bring React, then they bring Redux, then all the rest is being dragged in and you get multi MB bundles for some truly trivial purposes. Of course, that's more on developers than on React, but it happens way to often. And for some reason just bringing React and Co. is not enough, it usually ends up in some imressive architecture astronautics. At the end you have a project that is big, but slow and still impossible to understand because the levels of indirection are off the charts.
The sentiment that everybody reaches for Redux is tired, in my opinion. After following many in the web development community and keeping up with online forums such as this, it's fairly clear to me that people have moved on from the heavy armor previously associated with React if they have a choice. For instance, people learned that they were using Redux for prop drilling, which led to many switching over to the context API natively from React. Another good example is Gatsby, for those who realized they have a static site and would like to address the SEO issues associated with a SPA.
Also, a lot of times, companies adopted React and Redux before the inception of these new, more powerful libraries that are obvious choices on the ground as of August 2020. But, have fun refactoring your entire client side state seamlessly if you're tracking state more sophisticated than the status of the application sidebar.
1) That React is a powerful, productive, ergonomic language
2) That high quality resources exist for using it
I have struggled with both of these in React, yet in vanilla JS and html canvas I have no problem writing a 3d graphics engine lol
The last one I dropped was https://www.robinwieruch.de/web-applications which has more than 5000 words (1/6 of a book) of fundamentals in web development -- which took me 3 workdays of writing without anyone paying me for it. Still it gets less attention on Twitter than some random dev meme or inspirational dev tweet; and will probably not be picked up by HackerNews if anyone posts it ¯\_(ツ)_/¯
I do my best to teach people fundamentals. If they like my content on my blog, people buy my books/courses. This and their feedback (e.g. on Amazon, E-Mail) gives me confidence that I am doing the right thing. Without good content I don't get paid at the end of the month ...
Thanks for the shoutout @Pandabob! :)
It is useful, but only because react-testing-library's documentation is horrendous in this front (its documentation is fine as a reference, but not as an introduction/getting started).
However, your post will end up rotting over time as react-testing-library evolves, and will end up being old cruft spam contributing to today's issues (you search for something and find an outdated reference that doesn't work anymore).
If you really want to have positive impact with your documentation efforts, the best avenue would be to work with the software authors themselves on getting your tutorial there. And then helping to maintain it.
Of course you are not in any kind of obligation to do so. I just wanted you to think about it ;)
For sure, the easiest thing as a content creator is publishing (almost) ever green content (see web applications article). However, most often you are looking for topics that solve actual problems of your readers (see react testing library article) which often leads to bleeding edge technology which isn't document well yet.
For what it's worth, there will always be companies with money who pay people to write content to support their products (e.g. SaaS). This makes it harder every day for individuals like me to sustain their livelihoods. However, I strongly believe in the long run quality trumps quantity.
In a perfect world, there would be (1) one perfect learning material (e.g. official documentation) and (2) one unified learning style (e.g. text, video, both) for all students. But we are not living in a perfect world and therefore people look for resources outside of the box.
I'll grant that they probably do like the idea of passing on what they know, but I very much suspect the same thing of the tech lead who was asked to write a blog post by their marketer.
The Logrocket blog is an excellent example of this. Lots of useful blog posts. Another one I've been relying on is the blog of Robin Wieruch [1].
I guess stating this is a little obvious, but one of the upsides of using popular tools is the productivity boost you get from the surrounding ecosystem.
[1]: https://www.robinwieruch.de/blog