nouney

Nginx is not one of the building blocks of Kubetnetes. It's just an Ingress controller

GKE can use IPv6 now

But you ARE cool for listening to Kapitan Korsakov!

I don't get it, how do you configure nginx with a YAML file?

Take a look into kustomize

https://github.com/kubernetes-sigs/kustomize

I'd suggest rofi[1] rather than albert, runs like a charm.

[1] https://github.com/davatorium/rofi

Managing a VM vs a managed Kubernetes cluster? I'd choose kubernetes without hesitating

Like everywhere else ...

GKE is free.

Yes it is. You can do more with Kustomize

Read the Dragon Book[0]

[0] https://en.wikipedia.org/wiki/Compilers:_Principles,_Techniq...

- Avoid NIH: There's a very good chance that the code you're writing could instead be imported from libraries/frameworks that already offer it. Avoid the overhead of reinventing the wheel and focus exclusively on business logic (and sometimes even that might already exist in some oss projects you can use).

I partially agree. Sometimes it's better to reinvent the wheel: you got better control and less risks.

(How can I properly quote someone on HN?)

Lille's subway is "driverless".

No they don't.

I guarantee bluetooth headsets suck, all of them.

I've been using Tile38 for over a year now. It is amazing.

It will lock you down, as it's very hard to migrate from go-kit.

IMHO, it only brings problems.

Just another guy speaking subjectively of something he barely know.

Backend:

  - Go, NodeJS
  - Redis, MongoDB, Tile38, Neo4j
  - GKE
  - Traefik

  - React-Native

And for the rest of the world? I always wanted such a kind of service, can't wait to use it.

I don't like the dark header. But StackOverflow changed its header from dark to white and I don't like it either.

That makes me so confused about my likes.

From the README: "mux is a lightweight fast HTTP request router [...] It also scales better."

Where can I find the benchmarks?

No I wouldn't. I can't see any reasons to use Have.

https://hn.algolia.com/?query=boycott%20docker&sort=byPopula...

TL;DR: This is an implementation of strtok() in Go ...

"ActiveRecord is hardly "the depths". After ActiveRecord, your data will probably go through Ruby's I/O system, TCP stacks, IP stacks, low level kernel I/O, firmware on network cards, a database management system (itself comprising multiple layers of semantics), and will ultimately move some electrons around somewhere."

What are "the depths" according to him then?

"How many people can actually write BFS on the spot, without preparing for it in advance?" A lot of people. You should too, even if you're just a front-end.

Ok great, thanks for your explanation!

In which case is it really useful?