19 ms·
I think this article missed a key element of where ruby is going: developer productivity tools. It is kind of hinted at with static typing, but the real story
by chucke 5y ago
I think this article missed a key element of where ruby is going: developer productivity tools.
It is kind of hinted at with static typing, but the real story behind a lot of what happened since ruby 3 was released has been the tools and IDE plugins around it. Static Typing via RBS is also the existing LSP integration + VSCode plugin, the Typeprof plugin which allows scaffolding .rbs files for untyped modules, and the new debugger which will ship with 3.1, finally a core-blessed debugger, but above all, a debugger one can integrate with docker and IDE.
I'm expecting more of this in the future, such as a production-ready profiler, better tracing, overall better monitoring.
- joelbluminator 5y ago> but above all, a debugger one can integrate with docker and IDE. Can you expand? We have a kubernetes setup at work and I can't do binding.pry locally to get a breakpoint! (the containers aren't running on the developer's machine just clarifying). I was wondering what it would take for us to have breakpoints at work.
- Axsuul 5y agoWith byebug you can launch a server and connect to it remotely to intercept break points.