The whole stack is a dumpster fire filled with footguns.
Where “show me where this function is defined” turns into an impossible task.
The whole stack is a dumpster fire filled with footguns.
Where “show me where this function is defined” turns into an impossible task.
It's a terrible experience. No auto-generated specs. Can't even look at the code to know what some request parameters are supposed to be (had to go digging through pagy docs for that one). One day, a value in a response that is normally a string was suddenly an array on certain queries.
The whole approach is so haphazard move-fast-nobody-cares that it grinds my gears and I'm not even contributing to their code, just consuming it.
My kingdom for a better experience.
On top of that, the number of bugs that could have been avoided with static types is a bit depressing- the only true way to avoid them entirely is duplicating what you get from a static language, but manually with extra unit tests.
There's plenty of really nice things about Ruby and rails, but you don't actually get features faster without sacrificing something.
The team puts out code at more or less the same pace as I would have expected from teams working with other languages, though I haven't seen so many nil errors since working with a bad Java code base.
Overuse of dynamically generated functions is possible in any high level language. The worst offender that I had seen was a PHP wordpress plugin that stored a custom function per row in the DB brought to life via `eval`.
Those were the days.
A large number of high-level languages resolve functions at compile time, rejecting programs containing references to functions that don't exist.
I will agree that dynamically generated functions are not overused in languages in which they cannot be expressed at all, but...
Second, what happens when the code is in a different repo and there are zero imports so you have no clue where it’s getting loaded from?
We’ve got multiple gems and microservices so I can’t even grep one codebase, I basically have to grep our entire gh org to find the function because ruby has terrible tooling to help with “go to definition”.