HN user

gerhardhaering

52 karma
Posts1
Comments23
View on HN

Ok, 7%. With all the cost, I wonder if just stopping hiring and letting normal attrition rate play out would have had almost the same effect.

Threema is proven. The ome-time licence fee of EUR 5 are probably very well spent on it. At least on Android, you can skip Google App store and buy a licence directly with threema. And even bitcoin is supported for this.

Current status sounds like Wild West. It's probably because you don't have any people who know about infrastructure on board, yet.

I'd challenge the idea of dedicated infrastructure per developer in the first place. There's little reason why this could not be done locally on a developer machine using Vagrant, local Kubernetes, Docker Compose, whatever.

LXC vs. Docker 4 years ago

This would have been an ok article in 2013-2015. Nothing really has changed wrt. these two technologies since.

Closer as in the price? It is certainly a question of volume, but given that I can get an actual combustion car Dacia Sandero for 8.990,00 € - these prices seem ridiculously high!

This would not affect my decicion to use SQLite, which is still my choice for quick database setups. Not saying that they did it here, but the notion that atheism is synonymous with immorality would be absurd. It is usually quite the opposite, most orthodox religion leads to immorality due to the simple fact that it applies codes that might maybe have made sense centuries or millenia ago to modern day societies.

Apparently I am underpaid and this must be in the valley, right? That should be standard technology for an SRE by now. I have been using Docker since 2013, and I rarely encounter developers who don't have at least basic knowledge. Once you dive really deep into Kubernetes with service meshes etc., that's where it gets interesting.

I use the Neo layout since 2013. In my optinion, it is optimized for the German language and for programming. I really love it.

On Linux this worked perfectly for me, but on Macs there are some (Electron?) applications which have their own idea of keybindings. Notably MS Teams. They have their own idea of keybindings and assume some kind of quertz layout. Which using neo makes typing a questionmark, which works using "layer 3 key" (caps lock) and what is "h" on querty impossible. So I end up mostly just typing :question in chat, which produces a questionmark emoticon. Talk about workarounds. Oh yeah, it does not work because Teams opens the "help" window instead.

I thought about that too, but as far as I see with OpenVPN you have the single OpenVPN server as single point of failure and all the traffic goes through the server, which quickly becomes a chokepoint. If I needed this again, I'd try out tinc first. It does not appear to have the single point of failure issue.

You cannot really compare cloud providers to classic bare metal providers like Hetzner.

FWIW we're in the middle of going 100 % AWS after having used a dual setup with Hetzner for base load and AWS for dynamic load. Using spot instances for base load and autoscaling groups for dynamic load proved to be competitive in machine cost with Hetzner.

Plus there's a lot less management overhead with AWS on our scale (50+ machines). And the security of VPC and IAM cannot be replicated on Hetzner. Plus as always, it's the integration of all AWS services that's hard to beat. And we really need to be multi-region anyways (5 regions and counting).

Apparently all they've announced is that they'll release all their products in lockstep with a unified version number from now on.

I myself have hoped for a Go rewrite of Logstash for a long time, but there are apparently no plans for this. They are creating lightweight forwarders with their *beats, though. But they are only for forwarding to ElasticSearch, not a general log pipeline processor like Logstash.

FWIW there is a thing that's like Logstash in Go, it's Heka by Mozilla. I am very fond of it, but for some reason not many people seem to be aware of it or deploy it.