Don't make me think, or why I switched to Rails from JavaScript SPAs (reviewbunny.app)

Article summary

The author switched from JavaScript SPAs to Ruby on Rails for building their application, Reviewbunny, and found the experience to be more enjoyable and efficient. They attribute this to Rails' strong opinions and conventions, which reduce the number of decisions they need to make. In contrast, the JavaScript ecosystem offers many choices, leading to decision fatigue and increased setup time. The author argues that the JavaScript community could benefit from more guidance and conventions.

Main themes

• JavaScript ecosystem complexity
• Rails and conventions
• Framework choice and decision fatigue
• JavaScript vs Ruby
• Community and innovation
• Development efficiency and productivity
• Framework dominance and standardization
• Cross-platform development and tools

What commenters say

• The JavaScript ecosystem's lack of conventions and numerous choices lead to decision fatigue and increased setup time.
• Some argue that NestJS and other opinionated frameworks can provide a similar experience to Rails, but others disagree.
• The abundance of frameworks in the JavaScript ecosystem is seen as both a blessing and a curse, with some arguing it promotes innovation and others seeing it as a source of confusion.
• The comparison between JavaScript frameworks and Rails is considered unfair by some, as they are solving different problems.
• Others argue that the problem lies not with the language or framework, but with the community and its tendency to reinvent the wheel.
• Some developers prefer a more minimalist approach, avoiding custom types and objects, and instead opting for a synchronous-blocking, functional-reactive, event-driven, immutable, stateless, data-driven, declarative manner.
• The idea of a single, dominant framework for JavaScript, similar to Rails for Ruby, is seen as desirable by some, but others argue that this is not necessary or even possible.
• The use of WSL and other tools can mitigate some of the issues with developing on Windows, but may not entirely solve the problem.