121–125 of 125 posts
Earlier quoted context omitted.
Rust only protects from a very small subset of bugs (memory corruption issues and data races) but not from logic bugs which are far more common.
Rust protects against undefined behavior. This is enough that programs either panic in a well-defined way, or continue to run well enough that logging works.
Earlier quoted context omitted.
As a non linux expert I always wonder where to put crap - most places seem not fit for purpose.
There is a standard which you should follow. Here you go https://specifications.freedesktop.org/basedir-spec/latest/
>Debug information tends to be large and linking it slows down linking quite considerably. If you’re like many developers and you generally use println for debugging and rarely or never use an actual debugger, then this is wasted time. Interesting. Is this true? In my work (java/kotlin, primarily in app code on a server, occasional postgres or frontend js/react stuff), I'm almost always reaching for a debugger as an…
Earlier quoted context omitted.
when you write async JS code the debugger essentially adds no value over printing
Not in my experience, async JS/TS code is perfectly fine debuggable (at least with setting a breakpoint here and there).
Earlier quoted context omitted.
are there debugging tools specifically for situations like that? do you just write code to test manually? How do you ensure dev builds don't break stuff like that even without considering debugging?
The most useful tool is a full tracing system (basically a stream of run instructions you can use to trace the execution of the code without interrupting it), but unfortunately they're quite expensive and proprietery, and require extra connections to the systems that do support them, so they're not particularly commonly used. Most people just use some kind of home-grown logging/tracing system that tracks the particul…