Prove as in statistical evidence that code and teams working with Go yield software that has lower rates of runtime defects, has faster time to debug runtime errors, has improved the productivity of developers because of its obviously superior design and philosophy of error handling, etc.
These are all measurable. Productivity is measurable. Defect rates are measurable. Time to debug is measurable.
If there's a peer reviewed paper, let's see it. If there's not, you should produce it and get hired by the Go team!
If this is indeed the superior way of handling errors:
and not just excess key strokes and preference of style, then there will be some statistical side effect that can be measured to prove its superiority. If you can't prove it, all you're saying is "I prefer purple because purple is obviously superior to blue! Can't you see!"...O...K.
These are all measurable. Productivity is measurable. Defect rates are measurable. Time to debug is measurable.
If there's a peer reviewed paper, let's see it. If there's not, you should produce it and get hired by the Go team!
If this is indeed the superior way of handling errors:
and not just excess key strokes and preference of style, then there will be some statistical side effect that can be measured to prove its superiority. If you can't prove it, all you're saying is "I prefer purple because purple is obviously superior to blue! Can't you see!"...O...K.