3 ms·
Are you being ironic? If not: Rails is most certainly an option, if building web stuff is your goal. I think it's lame how bad the documentation around it is 4
by jstummbillig 3y ago
Are you being ironic? If not: Rails is most certainly an option, if building web stuff is your goal.
I think it's lame how bad the documentation around it is 40 years in, which I can kind of forgive because of how well thought out and complete pretty much everything is, once you figure it out.
That is not to say that there aren't very sensible JS options – for example AdonisJS is well long running, constructed and feature complete TS backend framework, that has little traction – only that the community seems to value excitement and Apple marketing techniques to the point, where even their darlings core concepts are so absurdly unstable, that it feels insane to start any reasonably sized project with it.
- ushakov 3y agoThe problem with Rails is that I don't know Ruby. It's a different ecosystem than the one I'm used to (Node). I'm also not aware whether Ruby comes with built-in type-safety, which is a requirement for me. Another requirement besides type-safety is JavaScript on the frontend and TailwindCSS for styling