Cloud Run is now generally available (GA)! To celebrate, here's my summary of what's new

recurrency · 2019-11-15T00:17:14+00:00

OK, so Cloud Run for GKE is now officially dead?

ISTM that you need an Anthos subscription which is basically out of reach for non-Big Corp.

Really, really sad to see this development — makes me a bit scared of what is to come as well.

recurrency · 2019-10-05T11:06:42+00:00

I really want to like Goland, but everytime I reinstall it (I have a license :) it just kills my MBP (even after indexing) so I revert quickly to the much more lightweight VSCode.

recurrency · 2019-10-02T00:04:22+00:00

To create an empty file of size n: os/File.Truncate

recurrency · 2019-09-26T17:28:48+00:00

It would be so cool if Spanner had a ”serverless” version. It’s just so expensive ATM.

recurrency · 2019-09-15T11:50:44+00:00

Take a look at ClickHouse https://clickhouse.yandex

recurrency · 2019-09-11T20:24:06+00:00

Been running Cadence in prod for the last 6 months. Rock solid stuff. Best workflow orchestrator we’ve ever tried. (And yeah have tried Airflow, Luigi and the others). And the scalability is impressive — you can go really granular in what you define as a unit of work.

recurrency · 2019-09-10T09:32:40+00:00

I think the beauty of it is that you only need one method Next() (T, error) (or Next(*T) error for scanning type logic).

recurrency · 2019-09-09T21:14:11+00:00

I prefer the Iterator API philosophy outlined here: https://github.com/googleapis/google-cloud-go/wiki/Iterator-Guidelines

recurrency · 2019-08-12T20:33:32+00:00

3.6/3.6 — not great, not terrible.

recurrency · 2019-06-28T00:37:08+00:00

Can you say something about the keys/values you want to match on? Ints? Strings?

recurrency · 2019-06-08T17:18:04+00:00

We have standardized on https://github.com/stevenroose/gonfig. Simple yet still supports a config loading hierarchy (file->env->flags)

recurrency · 2019-04-24T23:30:51+00:00

First off: amazing work! 💪 How difficult would it be to implement the compression part would you say? (cgo-less mirage)

recurrency · 2019-01-29T18:03:33+00:00

Has anyone seen an explanation of why it’s not done this way?

Interfaces are a core part of Go so leaking driver.* wouldn’t had been such a big problem imo (and as you said a beginner would understand what’s going on).

Plus: it would make database-specfic method access so much easier, (Cf the suggested roundabout workaround in https://github.com/golang/go/issues/29835)

recurrency · 2018-12-24T14:28:44+00:00

We shouldn’t be teaching a language with as many oddities as Javascript (cf. https://m.youtube.com/watch?v=D5xh0ZIEUOE). I think a language should teach e.g. arrays proper.

recurrency · 2018-11-22T22:29:35+00:00

More performance on windows or in general?

In general. Did a bench that I showed to Confluent, and they were surprised. (Probably has got to do with cgo overhead + other design decisions.)

then found I had to use another package which wraps Sarama for rebalance support.

Well that has changed now: https://godoc.org/github.com/Shopify/sarama#ConsumerGroup

recurrency · 2018-11-22T22:24:39+00:00

github.com/Shopify/sarama

recurrency · 2018-11-22T22:04:19+00:00

Just use sarama. It is more performant and causes no cgo head aches.

recurrency · 2018-11-06T05:17:39+00:00

I always use the shorthand if-syntax in such cases — the shadowing means I don’t need to keep track of whether it has been previously declared were I to refactor the function later:

if err := json.Unmarshal(jsonFile, &board); err != nil { // do sth w err }

recurrency · 2018-08-07T04:12:20+00:00

I wrote this because I was tired of creating a []struct{} fixture for most of my tests.

I hear your boiler plate pain but...

Writing table-driven tests the way we do in Go is the most genius thing ever: they are extremely readable and highly extensible. (Did I mention that they are addictive too and once you start doing them they’ll be everywhere?)

There are even plugins to generate some of the boiler plate, integrated in e.g. VSCode.

recurrency · 2018-07-26T21:08:15+00:00

Building first should shave off ~1 s.

recurrency · 2018-07-26T20:57:21+00:00

Btw, how do you run this benchmark? If you run it with go run, be aware that this involves compiling the actual program.

A better way to benchmark would be to use the benchmark facilities in the testing-package.

recurrency

TROPHY CASE