Iam writing go and I am having 300 go routines running at the same time.
When one of them crashes the print log becomes incredibly long and I endup scrolling up every time (I only need to see the last line of my log and the first go routine failing).
How are you making your developer experience nicer in go?
You can pipe the output of your program to a file
./program 2>&1 > log.txt
or to a program that lets you view the buffer head first
./program 2>&1 | less
The 2>&1 part combines stdout and stderr, so you get regular program output and error messages in the same buffer.