| ▲ | victorbjorklund 3 hours ago | |||||||||||||||||||||||||||||||||||||||||||
That is just wrong. > You need Beam and the Elixir. I find that really weird, because I'm used to just the language like in Python, Java, C, Rust. Not something underneath it, too The beam is a VM. You get that Java requires a VM too right? It’s called JVM for a reason. And Python requires an interpreter. > There is no debugger. The way to debug Elixir is to print stuff to the console, like 40 years ago. That is false. https://www.erlang.org/doc/apps/debugger/debugger_chapter.ht... and you have observer. And you have a lot of other debugging tools. I hear Java has a good one and maybe it’s better (I never used it) but it’s not true there exist no debuggers for the beam. | ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | Spixel_ 2 hours ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||
Almost nobody uses it though, which is too bad, especially since multi-head functions sometimes make it difficult to follow the execution path. I'd like to do step by step but I cannot plug the debugger to VScode from inside a docker container. | ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||