React-ing
About four years ago, I developed a client project using the WordPress Gutenberg plugin APIs, which uses React. However, since then, I haven’t considered picking the React framework up to add to my toolbox. That is, until now.
Most projects I’ve opted to use Vue, Svelte, or minimal vanilla JavaScript for projects instead. There isn’t any particular reason why I never took the time to get proficient in React; it just didn’t happen. In hindsight, it would have been better for me to explore React much sooner.
Occasionally, it was mentioned to me that there were potential project opportunities, but they were in React.
In one instance, I responded by shaking my head and saying something along the lines of “I’m just not a React person.”
How silly! I should know better than to react like that (pun intended).
React is a tool, just like any framework. It has its pros and cons, and it also happens to be what a lot of companies and open-source projects use.
Closing opportunities by closing your willingness to learn something new isn’t good. I personally strive to always be open to new learning opportunities and challenges. After all, programming isn’t about which language or framework you use but the problems you’re solving.
In a larger sense, if I want to be the most useful to Yahweh, our heavenly Father, I certainly can’t close myself off to opportunities that He sends.
By learning React, at least to the point of proficiency, I realize that many more opportunities would be open that are currently not since they unavoidably require knowledge packaged in a box labeled “React and the React ecosystem.”
So, I’m learning React.
5/1/2025 Update: To learn more about React (and to make an idea I’ve had for a while a reality) I created Reference8, a Web-based photo reference tool for artists and creatives.