31 karma · joined March 22, 2012
I'm more concerned about the more enterprise-y products aggressively advertising 'enterprise' security features like Active Directory integration, smoothing over their total lack of transparency in vulnerabilities and bugs.
?? They're just people.
Love this. Too often, conferences & groups that are all about 'openness' and freedom don't make allowances like this to actually expand the reach and the appeal. Linux Australia do a good job of this.
* The dialog was entirely unrealistic- to the point that a 'dialogue' was clearly simply the wrong form for what Tomayko wanted to do
* the 'wife' was portrayed alternatively as infantile, naive and purely reactive.
I follow Ryan Tomayko vaguely and I'd be surprised if this was a reflection of his behaviour. From what little I know he seems to have some awareness of and sympathy with struggles that come under "left politics".
But my knowing that doesn't erase the issues with his original post.
My comment on the original posting was thus:
> So Ryan Tomayko's conversions with his wife are akin in tone and style to a language textbook aimed at tweens?
You can't have that coupled with "wife" and simply wave away the problematic implications, not in our culture as of stands today. It's admirable that Tomayko is mature enough to consider challenges like this - instead of just going on the ultra defensive MRA spiel like some Redditor.
For example: one system I implemented needs to take a few hundred very large CSV files every day, aggregate and sort them, perform some complex processing on them, and output a result in a very different format to many different output files. It's an extremely complex system, and each component is in Go, performing a specific task, e.g.:
* combining the many source files * cleaning the source files * performing some aggregation on the stream * splitting the stream into many parts that other components can read from in parallel ('named pipes' in unix make this very nice) * splitting the stream into many output files
etc. Every component is dumb and does one thing, but a single controlling program is responsible for handling command line arguments that describe the overall outcome and setting up the stdin and stdout stream of all of the components to create the final result.
There's a beautiful simplicity to systems implemented like this, and it means you can take advantage of existing tools like grep, awk, sed, sort, cut, etc. to do a lot of the heavy lifting more reliably and quickly than you could probably implement yourself, while still coding the overall system at a reasonably high level of abstraction. Go doesn't lead to this approach directly, but it's very pleasant working with it as a citizen of this wider environment.
This is great, and I think many of Go's advocates - including devs at Google - underplay it. I don't understand why, particularly given the pedigree of Pike and Thompson.
My approach to building large systems in Go is based around processing pipelines, and tries to be as UNIX-y as possible. The interface types in the io package particularly fit the everything-is-a-file model, where processes can do one thing well while having their inputs and outputs connected to pipes, files, sockets, named sockets, devices, etc.
In short, building complex systems with Go components has made me a better UNIX programmer, a level that I could never quite reach in C due to all the distractions of memory management and unsafety.
Not to say that I think it's bad to have plenty of unixes floating around - just curious.
It's reasonable for someone to be confused about this; my rationale is that these three types are basically where go allows "magic": all of them support special syntaxes (the range operator, optional multi-value context when looking up a map, the select operator on channels), so they have a magic initialiser, ignoring Go's usual "declaration is initialisation" rule.
As others have said, it's not too bad a special case in the context of the language. The problem I have with it is that it introduces the possibility of run-time errors that in a language this advanced and generally so well-designed should probably be compiled-time errors: panics when you assign to keys in nil maps or deadlocks when you send to a channel you forgot to initialise are both errors of a class that the language generally doesn't have.