4 ms·
Yeah, and then it won't step you through your code but through unintelligible abstractions and Effect internals. Good luck debugging.
by noname120 2y ago
Yeah, and then it won't step you through your code but through unintelligible abstractions and Effect internals. Good luck debugging.
- epolanski 2y agoThat's a typical issue when debugging the JS ecosystem, it's not really an effect problem per se, albeit since Effect comes with a runtime there's way more noise as you noticed. It doesn't help your example has only library code to test.
- johnfn 2y agoIt is actually Effect-specific, because Effect modifies control flow in JS. For instance, if you pipe 3 functions in Effect, you'll have to step through the pipe function to get from the execution of the first to the execution of the next. Working around this adds overhead every time you debug your application. In vanilla JS, `a = foo(); b = bar(a); c = baz(b)` might not be as pretty, but it is trivial to step through.
- galaxyLogic 2y agoPlus if you are able to debug it somehow, and discover the bug in your code, can you fix it right there in your debugger? Or do you need to figure out what is the place in your original unprocessed source-code that corresponds to the code you see in the debugger, and then switch from the debugger to edit the original file and then rebuild and rerun everything and see if that fixes the problem? I wonder if that is a solved problem in plain TypeScript either?
- wetpaws 2y ago[dead]