Coming to Go from C#, I was shocked at how poor the debugging experience was, even inside Google itself (I worked at GCP for less than a year).
I don't get the mentality of people who don't feel the importance and satisfaction of being able to step through their code line-by-line and see everything coming to life in a debugger window, even if its for sake of watching it, not for finding a code bug. Some people seem to never have used one for years and they take it as a sign of weakness if someone says they need one to find a bug rather than looking at the code.
I haven't and if its up to me, I would never use Go again, just because of the piss poor debugging experience in a language that's so new. Google engineer's mentality is very old school and anyone who enjoyed the beauty of conditional breakpoints and step-through debugging in modern IDEs will know exactly what I am talking about. Go is so new yet built with incredibly ancient mentality.
You should try Jetbrains Goland if you're looking for a modern IDE with a great debugging experience [0].
If you're talking about visual studio being modern, i don't think that's true. I have used it recently and i was surprised by how outdated it is (maybe i'm not used to it). Also, I can't seem to do any changes while the code is running. That's very annoying.
You should have a try at Android NDK's, it is exactly that kind of experience, they only started changing it due to the backslash of game developers.
Not even game consoles are as bad.
Nowadays it has gotten much better versus the Android 2.1 days, and after 10 years it still isn't where Apple, Microsoft, Sony, Nintendo platforms are today.
Comments
Coming to Go from C#, I was shocked at how poor the debugging experience was, even inside Google itself (I worked at GCP for less than a year).
I don't get the mentality of people who don't feel the importance and satisfaction of being able to step through their code line-by-line and see everything coming to life in a debugger window, even if its for sake of watching it, not for finding a code bug. Some people seem to never have used one for years and they take it as a sign of weakness if someone says they need one to find a bug rather than looking at the code.
I haven't and if its up to me, I would never use Go again, just because of the piss poor debugging experience in a language that's so new. Google engineer's mentality is very old school and anyone who enjoyed the beauty of conditional breakpoints and step-through debugging in modern IDEs will know exactly what I am talking about. Go is so new yet built with incredibly ancient mentality.
You should try Jetbrains Goland if you're looking for a modern IDE with a great debugging experience [0]. If you're talking about visual studio being modern, i don't think that's true. I have used it recently and i was surprised by how outdated it is (maybe i'm not used to it). Also, I can't seem to do any changes while the code is running. That's very annoying.
[0]https://www.jetbrains.com/go/
You should have a try at Android NDK's, it is exactly that kind of experience, they only started changing it due to the backslash of game developers.
Not even game consoles are as bad.
Nowadays it has gotten much better versus the Android 2.1 days, and after 10 years it still isn't where Apple, Microsoft, Sony, Nintendo platforms are today.
Delve works just fine.