All those sound like good points, but it depending on how technical your mid/high level management are, you may want to adjust the wording.
if your audience are very technical, go fmt, and not having to read/learn code style sounds great, if they are not very technical, they will care less about where the developers put an opening bracket, but will care more about the fact that whoever does code review, will spend less time commenting on "small details like bracket position" and more time adding value to the company (by either writing more code themselves or being able to accept new code faster) Good luck on the presentation! On Sunday, April 30, 2017 at 3:41:14 AM UTC-4, Miki Tebeka wrote: > > Hi, > > I'm giving a 1 hour talk on Go to mid/high level management. Here are the > points I thought to bring up (not in order), I'd appreciate any > comments/ideas. > > * The free lunch is over > - threads/async are difficult to work with > * Small language > - Easy to learn > * Simple C based syntax > - Easy to understand > - Static typing > * Forces you to check errors > - Stable code > * import "C" > - Integration with legacy code > * "go fmt" and tooling in general > - The go tool > - The upcoming "dep" > * Static executable > - Easy deployment > * Fast compilation > - Quick development cycles > * Production grade HTTP server > - With HTTP 2.0 support > * Efficient & Fast > - iron.io post on going from 30 RoR to 2 Go servers > > Also, there was a post I read about a company which dropped nginx/haproxy > and started to use the Go HTTP server directly with incoming traffic, > anyone has the link? > > Thanks, > -- > Miki > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
