Live data from Hacker News

IceCream – Never use print() to debug again

github.com

11–20 of 24 posts

Re: IceCream – Never use print() to debug again

#13

>Do you ever use print() or log() to debug your code? I haven't written my own code in months at this point...kind of depressing to think about

My first thought as well. Debugging is actually a decent use case of AI.

I have a board with a logic analyzer, debug/flash probe, PSU, and multimeter on my desk being driven and debugged all autonomously by the AI.

While the automation and systems side of my brain is thrilled that all of this id automated and integrated, developer brain is sad

Re: IceCream – Never use print() to debug again

#17
Cannot recommend icecream, way too slow. But the use case of logging shines with realtime systems, or concurrent apps. You won't be able to efficiently debug them without logging. I live in my debugger, but logging is mandatory for the big picture.

Re: IceCream – Never use print() to debug again

#19

>Do you ever use print() or log() to debug your code? I haven't written my own code in months at this point...kind of depressing to think about

i got half way through the readme for this project and had the same thought and got sad and just left the page

Re: IceCream – Never use print() to debug again

#20
post #17

Cannot recommend icecream, way too slow. But the use case of logging shines with realtime systems, or concurrent apps. You won't be able to efficiently debug them without logging. I live in my debugger, but logging is mandatory for the big picture.

hey! icecream author here. what/how/where is icecream too slow for your use case(s)? feedback is how good products become great
Post reply on HN