Scholarly has had a fruitful year, securing investments, growing its customer base, and sticking to a simplified technology stack of Rails, Stimulus, and MySQL. Moving away from React has improved the testability of their application, resulting in more reliable Capybara-powered system specs. The emphasis on server-rendered content has led to fast route change times due to Turbo prefetch. JavaScript is viewed as a liability, with changes in JavaScript costing more time and risk than in Ruby. Moving forward, Scholarly plans to continue with Stimulus and Turbo, as their current approach has proven to be effective and well-received by both engineers and customers.
https://kellysutton.com/2025/01/18/moving-on-from-react-a-year-later.html