715 karma · joined December 19, 2008
Totally concur with this. I feel like all these people complaining about "bloated test frameworks" either haven't written a lot of tests, or are just fine with repeating themselves in test code, or they end up writing their own version of a test framework anew in every project. So much simpler and sane to grab an off the shelf solution for test code.
expected
func someFunc() {
aSlice := []string{}{
}
}actual
func someFunc() {
aSlice := []string{}{
}}
The end bracket on the slice's initializer never indents correctly when you type it and hit <enter>. It always defaults to the first character of the next line. It seems insertNewLine somehow is not able to grok the idea of more than one set of matching brackets.
Edit: issue filed https://github.com/atom/bracket-matcher/issues/209
This makes the whole solution fairly similar to just using auto-scale to spin up a new EC2 instance per app.
I know this is a major gripe right now with ECS, and hopefully Amazon is working on a solution.
Other than a few other frustrating gotchas, ECS has been pretty nice. I do like the idea of putting central config in S3 and copying config files over to cluster instances with a user data script (how they recommend you pull from private docker repo).
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...
http://www.nytimes.com/interactive/2015/10/01/business/cost-...
Replace porn with '*' and now we're really cooking...
Tried the Graph plugin also -- after installing it and clicking on it, it shows a blank page.
The HipChat integration works well, but they've had that for some time now.
I'm sure you get used to it. Every language looks horrible the first time, then you learn to live with it and maybe love it, but on first glance that looks pretty awful.
client, server := net.Pipe()
var buf bytes.Buffer
client = &recordingConn {
Conn: client,
Writer: io.MultiWriter(client, &buf),
}
While it seemingly works, it seems confusing to assign client to an internal field of a new struct, and then overwriting that same client variable with the newly created struct...not to mention passing it into MultiWriter.Anyway, I like those short posts like this. I've done similar things with embedding and struct "reconstruction" in order to elicit more testable code. It's powerful and useful, indeed.
Your other options on Mac are Vagrant's docker provider -- which is nice, but I agree in general with the sentiment that it is even nicer to just use Linux natively.
> I don't want to spend my whole life on this.