3 ms·

I agree on the responsiveness part and would like to add that the fact that BeOS dropped you to a debugger shell when it crashed is something missing from moder

by snazz 8y ago

I agree on the responsiveness part and would like to add that the fact that BeOS dropped you to a debugger shell when it crashed is something missing from modern desktop OSs. Just like the Lisp Machine (Genera, at least), introspection is something that’s present in Haiku and BeOS that was cut out of many modern desktop operating systems for “security” and “ease of use”.

erikpukinskis 8y ago
In the JavaScript world, debugging is almost a bad word. It’s almost impossible to maintain a sane debuggable trace though a “modern” JavaScript application. I find I have to ignore basically all of the standard frameworks and transpiration pipelines and just write old school PHP-like code in Node. I say all of this because I feel that my community has lost control of the debugging pipeline and I applaud Be and Haiku for making that a priority. I find the benefits of committing to an always-running, always-traceable-in-production execution thread is an EXTRAORDINARY productivity gain (vs console.logs and connecting to IDEs manually via various witchcraft)
- porker 8y ago
  > In the JavaScript world, debugging is almost a bad word. It’s almost impossible to maintain a sane debuggable trace though a “modern” JavaScript application. I felt this last week as I tried Webpack 4 on a new project. The source maps weren't correct, and instead of debugging my app I had to debug multiple Webpack plugins and work out which one was breaking the source maps. Never did find out, but I fixed my app by debugging it mentally. It sure made me wish for a developer-first language.
int_19h 8y ago
> The fact that BeOS dropped you to a debugger shell when it crashed is something missing from modern desktop OSs. Windows has that - if you have e.g. Visual Studio installed (or any other app that registers itself as a system-wide debugger), then application crash dialog will immediately offer to attach the debugger at the point of the crash.
- pjmlp 8y ago
  Since Windows 3.1 actually, famous Dr. Watson.
dpg23 8y ago
Check out GuixSD if you like Guile Scheme REPLs when something breaks! I also recall OpenBSD and FreeBSD dropping to debuggers on kernel panics.

by snazz 8y ago

erikpukinskis 8y ago

In the JavaScript world, debugging is almost a bad word. It’s almost impossible to maintain a sane debuggable trace though a “modern” JavaScript application. I find I have to ignore basically all of the standard frameworks and transpiration pipelines and just write old school PHP-like code in Node. I say all of this because I feel that my community has lost control of the debugging pipeline and I applaud Be and Haiku for making that a priority. I find the benefits of committing to an always-running, always-traceable-in-production execution thread is an EXTRAORDINARY productivity gain (vs console.logs and connecting to IDEs manually via various witchcraft)

porker 8y ago
> In the JavaScript world, debugging is almost a bad word. It’s almost impossible to maintain a sane debuggable trace though a “modern” JavaScript application. I felt this last week as I tried Webpack 4 on a new project. The source maps weren't correct, and instead of debugging my app I had to debug multiple Webpack plugins and work out which one was breaking the source maps. Never did find out, but I fixed my app by debugging it mentally. It sure made me wish for a developer-first language.

int_19h 8y ago

> The fact that BeOS dropped you to a debugger shell when it crashed is something missing from modern desktop OSs. Windows has that - if you have e.g. Visual Studio installed (or any other app that registers itself as a system-wide debugger), then application crash dialog will immediately offer to attach the debugger at the point of the crash.

pjmlp 8y ago
Since Windows 3.1 actually, famous Dr. Watson.

dpg23 8y ago

Check out GuixSD if you like Guile Scheme REPLs when something breaks! I also recall OpenBSD and FreeBSD dropping to debuggers on kernel panics.