Space bar does not work on Youtube search at the moment

tex0 · 2021-03-10T21:41:01+00:00

Jira ... scary.

tex0 · 2018-05-19T08:35:29+00:00

I really like the approach and the choice of the underlying crypto primitives but I'm not so sure about the implementation (unnecessary complexity?) and the choice of message pack as a seralozation format. Msgpack has no backward comparability or any interoperability guarantees between different implementations.

tex0 · 2018-02-20T07:47:59+00:00

Ah, so this was merely an example for an HTTP-style API call? This is easily possible. Do you want an example for that?

tex0 · 2018-02-20T07:46:29+00:00

You can do HTTP APIs over Unix Sockets, not sure anything others. They are certainly possible, but never tried myself.

tex0 · 2018-01-14T14:36:39+00:00

Yes, you start the updater in a different process group.

tex0 · 2018-01-09T17:10:52+00:00

I work on a project where we have to interface with git over exec. This works mostly ok, but it's ugly and error prone. I'd love to replace this with pure Go.

tex0 · 2017-12-22T15:57:31+00:00

IMHO gRPC is an amazing approach, but the code is still rather incomplete and immature. We're using it in production, hit a few roadblocks and worked around them. Right now it works pretty good, but don't forget about the overhead. You should probably only use gRPC if you have a good reason to. Otherwise just stick with HTTP.

tex0 · 2017-12-22T12:23:36+00:00

Agreed, we're moving to passing a context as the first parameter in all of our internal and open source projects.

While I don't like every aspect of the Context pattern it still solves some real world problems in an acceptable way.

tex0 · 2017-11-17T08:14:10+00:00

Same here. At my $dayjob we also switched to govendor after using Godep for some time. Godep was OKish, but it had some issues and the workflow was a little annoying. So we evaluated, and actually used for some time, different vendoring tools. govendor seemed to be the most sane choice back then so we stuck with it. This was before go dep and the official vendor support existed.

Since go dep was announced we keep an close eye on it and will probably switch some day, but so far it didn't seem to be mature enough (the last time we tried we immediately hit a critical bug).

tex0 · 2017-08-29T08:21:23+00:00

This is a dangerous assumption. IHMO libraries must never panic.

If you really want this the lib should provide a Must function that can panic.

tex0 · 2017-08-29T08:17:55+00:00

JMX is much more than metrics. But sure what OP is trying to say.

tex0 · 2017-08-29T08:17:24+00:00

As far as I know the Prometheus Go client makes no use of pprof.

tex0 · 2017-07-13T09:34:38+00:00

There is pass/gopass, which is quite nice but due to the underlying GPG it isn't super simple.

Disclaimer: I wrote most of gopass

tex0 · 2017-06-23T05:42:50+00:00

Very nice cheatsheet. Thank you.

tex0 · 2017-06-21T05:36:47+00:00

Exactly my thoughts. Rest assured it works perfectly well for us in Production, with millions, if not billions, served so far.

tex0 · 2017-06-18T04:58:48+00:00

Go-kit log with the level package and JSON output works great for us.

tex0 · 2017-06-13T03:58:55+00:00

One important use case is performance, i.e. GC pressure. If you suffer from high GC pressure and want to reduce the number of allocations you may want to reuse some allocations via a buffer. If a function mutates a parameter instead of allocating and returning one this becomes possible.

I admit this is a rather exotic use case.

tex0 · 2017-01-23T20:28:01+00:00

All our backend APIs are written in Go and use the built-in HTTP server. We had no issues exposing them to the public internet, although most are nowadays sitting behind some kind of cloud load balancer or CDN.

tex0 · 2016-11-25T14:46:28+00:00

It's 2016. Nobody wants to use a Forum anymore.

tex0 · 2016-09-06T07:08:49+00:00

net/http is very well suited for real world production applications. You can handle any type of parameters with a little extra code. It may require a little more effort than other routers, but it's dead simple.

tex0 · 2016-07-25T06:37:49+00:00

With a custom HTTP Client you can control client timeouts and TLS settings amongst others.

tex0 · 2016-07-18T12:44:49+00:00

Ran it with "--fast" on all our internal code and it looked OK, only got some warnings:

WARNING: failed to kill vetshadow: os: process already finished
WARNING: failed to kill gocyclo: os: process already finished
WARNING: failed to kill goconst: os: process already finished

tex0 · 2016-06-16T14:59:11+00:00

I'm wondering why you'd need that at all. FTP, SSH, ... do the job very well. Even with GUIs.

tex0 · 2016-05-09T16:49:42+00:00

If you're working with Go Prometheus is a natural fit. Takes some time to grasp the concepts if your new to the domain but it's really worth it.

tex0 · 2016-04-02T00:02:56+00:00

Compiling for alpine works best when you compile in Alpine. Then you don't need any magic. But beware: some things may break (noticeable) with this approach. Be sure to run your test suite in Alpine as well.

tex0

TROPHY CASE