Re:Go compiler: Initial support for concurrent backend compi...
by rantanplan on Friday April 14, 2017 @09:09AM
(#14114213)
Think vast codebases that were created by many programmers that weren't you :D
Re:Go compiler: Initial support for concurrent backend compi...
by baconizer on Friday April 14, 2017 @01:53PM
(#14115899)
this reflects my team's experience, initially skilled programmers (from C# mainly) complains almost hourly about lack of IDE features, in particular - Debugging. 14 months in now with 9 major services in production, I hear no more conversation on this, and still no one yet bothered to setup dlv. 'Breakpoints', to our surprises, is not actually indispensable. Also I noticed positive cultural change around, we move faster and team talks about business problem solving more than programming itself, to a point I believe rich functionality IDE over complicated things we do here.
Re:Go compiler: Initial support for concurrent backend compi...
by sjellis on Saturday April 15, 2017 @04:52AM
(#14119985)
> Also I noticed positive cultural change around, we move faster and team talks about business problem solving more than programming itself, to a point I believe rich functionality IDE over complicated things we do here.
I think that this point about team conversations is incredibly important. Apart from Ruby, Go is the only language that I know where the technical conversations seem to consistently focus on the problem at hand, rather than coding concerns like the finer points of language features. The company that I work for does both Ruby and C#, and the difference in the conversations around the two is very noticeable.
But I haven't used a debugger in at least ten years. Production Go for the past few.
I debug with good log messages.
Of course, not everyone's problems are exactly like mine, so I will believe you if you say it's necessary for your situation.