Rails has always been about best practices in web development, not what's popular. If this were the case, why didn't rSpec make it as the default test suite in Rails 2?
Unfortunately now, Rails 6 will contain bloat. But more concerning, leave most web developers vulnerable, as most will unknowingly install Node with sudo, making node_modules owned by root, allowing for some fun executions <https://snyk.io/blog/malicious-code-found-in-npm-package-event-stream/>.. For a moment, Sprockets allowed us to align our Javascript with our MVC resources, it was maintainable, good design, that put Rails developers on the same page. But starting with Rails 6, we will divide - some into Angular, some into React, or Vue, or any of these other exotic front end frameworks that *r*epeat *y*ourself in generating HTML. I guess we never really cared about being efficient. It turns out all we cared about was job security. - Dominic https://linkedin.com/in/dominicson http://twitter.com/deezzer -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
