Starting with Rails 7 vs. Starting with React JS
Don't be fooled by high-work single-page app front end paradigms.
These Turbo apps operate at the same speed or faster than traditional single-page apps. This major step forward has reestablished Rails' place in the food chain of tech stacks available today.
React JS is great for many things, but what they don't tell you is that small, simple steps take a LOT of work.
What the React JS world also doesn't tell you is how much work it takes to maintain application state in two separate apps (the frontend and the backend).
After 7 years of doing post-mortems on failed React projects, the situation is clear: the React JS paradigm — championed by Facebook and other Big Tech companies — primarily serves to keep the existing tech monopolies in power and prevent newcomers from disrupting the industry.
React also necessitates a high amount of upfront technical lock-in, which makes it harder to change your mind about your functionality, field names, and/or data tables later. Having the freedom to add and rename fields and tables is absolutely essential in the critical first, second, and third years of your new software project or start-up.
If you fail to achieve significant velocity within this timeframe, you will likely not survive to the next phase of your company's growth.
Choosing the right tools upfront can literally make or break a start-up.
Some of the most successful apps on the internet have been built using Ruby on Rails.
Is yours next?