The Ruby ecosystem is rich with tools that make us developers more productive at what we do. Both Rails and Sinatra have been used to build web application proof-of-concepts and prototypes. But which one is better?
In this article, I try to explain why a back-to-basics approach is better suited for the ideation and conceptualization phase and how this ties in with an underrated aspect of software development — the design process.
“Sinatra syntax”? There’s no such thing. Sinatra is written in Ruby, so any tool capable of highlighting and autocompleting Ruby will work for a Sinatra app.
Also, the latest commit to the Sinatra repo on Github was made 4 days ago. This is an actively maintained project, and I don’t think that people in charge of it are less cognisant of the “latest ruby conventions” than you are.
The Rack 3 issue says: “dentarg opened this issue on Jul 20, 2022”, as you can plainly see from the screenshot. So it’s not 3 years ago but less than one year ago.
Also if you actually read the thread, there are engineers discussing how best to upgrade to Rack 3 in terms of resolving dependencies, etc. So there might be a reason that they don’t just rush off and upgrade to the Latest Version of Everything as soon as it’s out.
Yes, and my statement comes from the fact that the Sinatra DSL syntax is a subset of the Ruby programming language syntax. Meaning, any editor / IDE that supports Ruby automatically supports Sinatra via the magic (and the beauty!) of set theory.
Resources are partially outdated, but I haven’t so far had an issue to which I wasn’t able to find an answer or solution after doing a little bit of digging.