Rails is better low code than low code (radanskoric.com)

Article summary

The article compares the development of a simple CRUD application using a low-code platform and Ruby on Rails, highlighting the trade-offs between the two approaches. The author argues that while low-code platforms can be faster for initial development, they often lack flexibility and become cumbersome as the application grows in complexity. In contrast, Rails provides more future flexibility and options, making it a better choice for applications that may require innovation or customization. The author concludes that Rails can be a better low-code solution than traditional low-code platforms.

Main themes

• Low-code development
• Ruby on Rails
• Flexibility and customization
• Application complexity
• Development trade-offs
• Programming languages

What commenters say

• Low-code platforms are suitable for simple applications, but become impractical as complexity increases.
• Some developers prefer to use full programming languages from the start, rather than switching from low-code platforms.
• The choice between low-code and traditional development should depend on the team's experience and the application's requirements.
• Dynamically typed languages, such as Ruby, are considered to have limitations compared to statically typed languages.
• Low-code platforms can be useful for internal tools and prototyping, but may not be suitable for large-scale applications.
• The concept of 'strongly typed' languages is subjective and can be defined in different ways.
• Some developers argue that dynamically typed languages are not truly typed, while others see them as having a different type system.
• The use of ORMs can be seen as unnecessary and overly complex, with some preferring to use SQL directly.