News for hackers. Stuff that matters.
Re:Show HN: Prometeo – a Python-to-C transpiler for high-per... by zanellia on Wednesday November 17, 2021 @01:19PM (#29256723)
For what it counts, I have developed code for this kind of applications exclusively in C for ~5 years (let's say 20% of my working time). I still think that debugging a segfault that you could have avoided is not very productive and that motivated me to look into possible alternatives.
Re:Show HN: Prometeo – a Python-to-C transpiler for high-per... by klyrs on Wednesday November 17, 2021 @03:03PM (#29258180)
FWIW, I almost always use valgrind before a debugger, when tracking down segfaults. It doesn't catch everything, but 90% of the time, it gets me to the right region of code in a single run.
Re:Show HN: Prometeo – a Python-to-C transpiler for high-per... by zanellia on Wednesday November 17, 2021 @03:35PM (#29258504)
sure I use valgrind and gdb too - still hard to argue that a segfault is pleasant to debug though?
Re:Show HN: Prometeo – a Python-to-C transpiler for high-per... by klyrs on Wednesday November 17, 2021 @04:10PM (#29258887)
Good good, just wanted to advocate for my favorite tool there. But, in my experience, segfaults are usually the easiest bugs to resolve. Unlike a sign error in my math, they're impossible to miss!

That said, tooling to get rid of them entirely is not to be sneezed at :)

Re:Show HN: Prometeo – a Python-to-C transpiler for high-per... by kevin_thibedeau on Wednesday November 17, 2021 @02:49PM (#29258019)
99% of the time a stack trace shows the culprit for a segfault straight away. No different than debugging Python.
Re:Show HN: Prometeo – a Python-to-C transpiler for high-per... by zanellia on Wednesday November 17, 2021 @03:37PM (#29258520)
if we are arguing that implementing a numerical algorithm in C is as easy as implementing it in Python - I would disagree. But maybe I am just wrong :)
Re:Show HN: Prometeo – a Python-to-C transpiler for high-per... by kevin_thibedeau on Wednesday November 17, 2021 @06:17PM (#29260144)
The issue is debugging crashes, not productivity.