Clojure has spec now, you can define and "force" your types there.
The best approach is to let that Webpack handle SCSS/JS but still you can create most of the site with old good HAML.
Rails is a very mature set of DSL tools. There is nothing even close to the level of integration, richness, community, and documentation that Rails offers. Ruby by itself is a powerful reason to develop with Rails.
> The downside there is that you're then forced to build your application as a completely separate service and static site. That is not true, you just call what you need from the JS framework and you can still use the…
Webpacker is an anti-pattern: pollute the ruby sphere with JS and pollute the JS sphere with Ruby because you don't wanna read the Webpack tutorial.
Clojure has spec now, you can define and "force" your types there.
The best approach is to let that Webpack handle SCSS/JS but still you can create most of the site with old good HAML.
Rails is a very mature set of DSL tools. There is nothing even close to the level of integration, richness, community, and documentation that Rails offers. Ruby by itself is a powerful reason to develop with Rails.
> The downside there is that you're then forced to build your application as a completely separate service and static site. That is not true, you just call what you need from the JS framework and you can still use the…
Webpacker is an anti-pattern: pollute the ruby sphere with JS and pollute the JS sphere with Ruby because you don't wanna read the Webpack tutorial.