Live data from Hacker News

Etcd, or, why modern software makes me sad

roguelazer.com

41–50 of 648 posts

Re: Etcd, or, why modern software makes me sad

#43
post #30
post #5

Earlier quoted context omitted.

What are some of the arguments against `systemd`? I've used it in several production systems and don't really have an opinion on it.

Here's a good article that I saw on HN a few months ago: https://blog.darknedgy.net/technology/2020/05/02/0/index.htm... Also: https://suckless.org/sucks/systemd/ Personally I avoided it for a while because of the hate, but haven't really had issues with it since using it.

Similar opinion here. I put it off for when I could learn it better, and so far it's been fine... sometimes nice too when it has a feature I want that's already built-in (depending on version level and all that).

Re: Etcd, or, why modern software makes me sad

#44

> HTTP/2 a.k.a. SPDY is a comically bloated Layer 4/5/7 mega-combo protocol designed to replace HTTP. It takes something simple and (most importantly!) comprehensible and debuggable for junior programmers and replaces it with an insanely over-complicated system that requires tens of thousands of lines of code to implement the most minimal version of, but which slightly reduces page load time and server costs once you…

https://github.com/cloudflare/quiche

Re: Etcd, or, why modern software makes me sad

#45
post #39
post #18

bai

> This guy used to run infra at uber and was incredibly salty about every single new technology. There were a lot of bad ones, but every conversation was about as constructive, free of evidence, and bitter as this blog post. I'm going to assume you're a developer? Infra people are usually much more apprehensive to take on new technology. Crucially I would describe classically trained sysadmins as 'pessimists to the c…

> I'm going to assume you're a developer?

No, but thanks for explaining my career to me and helping me empathize with toxic people.

Re: Etcd, or, why modern software makes me sad

#46
post #39
post #18

bai

> This guy used to run infra at uber and was incredibly salty about every single new technology. There were a lot of bad ones, but every conversation was about as constructive, free of evidence, and bitter as this blog post. I'm going to assume you're a developer? Infra people are usually much more apprehensive to take on new technology. Crucially I would describe classically trained sysadmins as 'pessimists to the c…

saying "no" does not a devops engineer make

Re: Etcd, or, why modern software makes me sad

#47
I run k8s in production and I think this is a really bizarre axe to grind that sort of smells like someone who got upset by how steep the kubernetes learning curve is. Which, in a way, is understandable.

> 1) Add hundreds of new failure modes to your software

In my entirely anecdotal experience, it removes error modes. It turns out that just because k8s offers a feature (it offers many!) doesn't mean you're required to use it.

> 2) Move you from writing portable software configuration to writing thousands of lines of k8s-specific YAML

Portability, put another way, is a requirement to maintain n different deployment mechanisms because you have no meaningful control over the system on which your software is deployed. This is unavoidable depending on what it is you're deploying and where, but for those of us who have the ability to make those decisions the old notion of portability described by automake and others is actually a bad contract to agree to.

That said, the YAML but is horrible and should be abolished. This is a great criticism.

> 3) Ensnare you in a mesh of questionably-good1 patterns like containerization and software defined networking

The author isn't considering that I am not, and never will be, Google's entire SRE team. I consider it a general win to be able to apply some subset of their encoded knowledge to the problem of keeping my services running with minimal downtime even if you pick up some k8s-specific baggage along the way.

Re: Etcd, or, why modern software makes me sad

#48
post #11

This seems rude and also dishonest/revisionist, eg "In 2015, an unrelated tool called Kubernetes was released by Google (but, really, by Xooglers)".

What is dishonest/revisionist about the statement you have quoted?

How about that Kubernetes was released in 2014, not 2015? It's the first thing that shows up when you Google "Kubernetes" - Initial release: 7 June 2014; 6 years ago.

Evidently, OP couldn't even be bothered to gather basic facts about the tech he trashes.

Re: Etcd, or, why modern software makes me sad

#49
post #45
post #39

Earlier quoted context omitted.

> This guy used to run infra at uber and was incredibly salty about every single new technology. There were a lot of bad ones, but every conversation was about as constructive, free of evidence, and bitter as this blog post. I'm going to assume you're a developer? Infra people are usually much more apprehensive to take on new technology. Crucially I would describe classically trained sysadmins as 'pessimists to the c…

> I'm going to assume you're a developer? No, but thanks for explaining my career to me and helping me empathize with toxic people.

> thanks for explaining my career to me

I'm explaining that the majority of the people who were sysadmins in 2005 are more likely to be pessimists than optimists and are change/risk averse, I don't think that's controversial and definitely is a meme.[0]

> [thanks for] helping me empathize with toxic people.

You're welcome. :)

[0]: https://books.google.se/books?id=0VRnDwAAQBAJ&pg=PA490&lpg=P...

Re: Etcd, or, why modern software makes me sad

#50
post #46
post #39

Earlier quoted context omitted.

> This guy used to run infra at uber and was incredibly salty about every single new technology. There were a lot of bad ones, but every conversation was about as constructive, free of evidence, and bitter as this blog post. I'm going to assume you're a developer? Infra people are usually much more apprehensive to take on new technology. Crucially I would describe classically trained sysadmins as 'pessimists to the c…

saying "no" does not a devops engineer make

What is a devops engineer? Devops is a culture as originally defined. With sysadmins and software engineers.

And, yeah, sysadmins used to say no a lot but younger ones tend not to because they haven't been rubbed wrong by the silo's of yore.

Post reply on HN