3 ms·
>This is like comparing apples and oranges, or at least, like comparing apples and apple-orange hybrids :) >Just saying that Rails (RoR) has a command like bye
by treis 8y ago
>This is like comparing apples and oranges, or at least, like comparing apples and apple-orange hybrids :)
>Just saying that Rails (RoR) has a command like byebug that opens an in-context REPL, seems to ignore the fact that compiled languages like Go catch many errors earlier, at compile time, so you don't even need an in-context REPL or a debugger to find those.
I definitely liked the type system of Go and the compile time errors it found. It gives you a lot of peace of mind and reduces some errors. However, those errors aren't the things I use byebug for. Byebug is for things like figuring out why your code went down Path A when you expected it to go down Path B. Or if you don't know how to do something it's a sandbox to try a few different things until you get the output you were looking for.
- vram22 8y ago>Byebug is for things like figuring out why your code went down Path A when you expected it to go down Path B. Got you now. The classic use case(s) of an REPL. I may have misunderstood your earlier comment, which is why in my own earlier on, I had said "seems".