DomBlack

I saw this blog post title and wanted to read it, as I thought this is something we really wanted when I worked back at Encore - and lo and behold what website I ended up on!

Great work lads, seeing those old shell scripts brought back memories, but this is awesome to see you've solved the problem now to make your own lives easier!

Any plans to open source crackling? I was looking into cross platform microVM's after reading about sbx recently.

You can use oauth tokens with the permissions of auth_key write to use long lived tokens to permission ephemeral nodes

Hi folks,

I just wanted to share that the latest release of Encore automatically captures a trace of every test, providing much more visibility into what's happening and making it easier to understand why a test failed.

The test traces automatically include everything you expect: API calls (including mocked calls with Encore's new mocking support!), Database queries, Pub/Sub messages, HTTP requests, etc.

And it does all of this without the user having to change or add any code outside what they would normally write for a Go test.

This has been my first technical blog post in a long while, so any constructive feedback is greatly appreciated.

I agree; there are entirely different ways to achieve this same goal without generics. I mentioned using a struct and including the data from the struct in the post. However, what I wanted to show within the post is how generics can make this problem easier for us.

> As boilerplate goes, if you look at it, it isn't even that much more. Interfaces can still be used to ensure that the correct methods are guaranteed to be implemented.

Yeap, we implemented many different interfaces on our ID types, and the resource type also implements a couple of interfaces (such as methods to get the Postgres type information). Unfortunately, this means we still need to create receiver methods for each of these interfaces so we can use the ID types with those underlying libraries (such as `JSON` or the `SQL` scanners) which ends up being 14 methods per resource type (and we have quite a number of resource types). We would have ended up code generating these, and generics just saved us that work.

> Underscores are too common in identifiers.

We picked underscores, as they are not included in the base32 encoding of XID. They're also safe to put in URLs without needing to perform any encoding. Our static analysis tools during CI check that all code generation has been completed and prevent the prefixes from having underscores. That means we don't need to worry about escaping as we can always unambiguously split it. However, even if your prefixes allowed underscores, you can always just split the string at the last underscore; as the XID portion of the string cannot contain it.

I'd be interested to know how you were bitten by it in the past?

> Always build your architecture in a way that will avoid becoming trapped into a specific service. Amazon’s AWS Lambda sitting between any services and your app is a strongly recommended path!

Isn't using AWS Lamba as your gateway, trapping you into using a specific service, just as much as firebase was?

We spent a good hour or two when Chrome 56 came out trying to work out why our .eu domain didn't work but the .com did. Even though it was the same startssl cert on the same IP. Turned out our .eu wasn't popular enough to remain allowed even though it was our primary domain up until last year.

I had read the original blog post but my original understanding was that existing certificates would remain trusted and simply newer ones would not be. Hidden in the paragraph was the parts out then staring to distrust existing certificates. Very poor communication from Google

Two others in my office read the front page, but quite none of us have yet found invites (not that we've looked hard), but the idea of an invite only community sites feels counter productive

I'm interested in what you're looking at which says that. Against the dollar 2.5-3 years ago GBP was never below 1.47, since the referendum, the highest it has been is 1.34 and that was the lowest we got in the 2008/2009 crash.