[yagodragon]

I don't know Ruby on Rails but i would love to learn it at some point. At my job we're creating some internal tools that are 95% CRUD and we're using JavaScript for everything. Vue.js/Nuxt.js/Vuex with express.js(on docker) and a shitty "headless" CMS (strapi) with MongoDB for backend. It sucks. We're writing hundreds of LOC every day just to create some simple forms. Our tech stack is so fragmented that makes it difficult to make changes and cooperate in our team. A simple thing like a <select> or <datalist> html element is re-implemented in a vue.js UI library and across 3 different files in Vuex. On the backend the story is even worse. Strapi is very limiting and it's not designed to be extended with custom business logic so we have to rely on custom solutions from scratch. Rails appears to be the best solution to our problems but our CTO only likes Javascript i guess...

[johntdaly]

I feel your pain (literally since I am currently in the same boat with). Yes Rails would be a perfect solution for the CRUD work you have. Hell Django probably would be a good solution too.

Unfortunately it was “clear” 8 years ago that JavaScript is the “future” and I think at latest 5 years ago everybody got the memo.

Right now I think it is “clear” that the “future” we build with JavaScript has gone horribly wrong and I see some of us reevaluating the tech stacks we came from (Ruby on Rails, Django…) and some doubling down on JavaScript with SSR (server side rendering) and static pages in JavaScript Frameworks.

I’m afraid “the ride” will continue for a while.