3 ms·
As a dyed-in-the-wool print debugging advocate, and a Gleam-curious Erlang/BEAM enthusiast, this is very interesting for me. Thanks for all your work, great to
by spinningslate 2y ago
As a dyed-in-the-wool print debugging advocate, and a Gleam-curious Erlang/BEAM enthusiast, this is very interesting for me.
Thanks for all your work, great to see how well the language and tooling are maturing.
- giacomocava 2y agoprint debugging is the best debugging <3 Thank you for the kind comment!!
- IshKebab 2y agoNah it's just the easiest and most reliable way. Usually anyway; sometimes you have extreme timing or space constraints and can't even use that. On microcontrollers I sometimes have to resort to GPIO debug outputs and I've worked on USB audio drivers where printf isn't an option.
- hayleighdotdev 2y agohello fellow print debugging enjoyer, rejoice!
- reddit_clone 2y agoIndeed, for me, the IDE debuggers became useless when we started writing multi threaded programs. Printf is the only way to reliably debug multi threaded programs.