Post

Digital Ocean calls servers "droplets" Linode calls servers "nodes" Hetzner calls servers... "servers" Just curious how people feel about companies using their own language/vocab?

0 reposts5 likes

It often feels like these companies are trying to Steve Jobs-ify their products but sometimes it ends up just being more confusing and harder to search for answers

Sometimes it's necessary because it's slapping a unique identifier on them so you can refer to them when discussing differences. Otherwise you'd had to say "Digital Ocean servers" vs "Linode servers" which becomes a mouthful.

If you are familiar with self-hosting stuff, you probably heard about these terms. But it's actually quite hard for beginners. It honestly took me a while until I understood that Droplets are servers.

Well, what is a "server" anyway? Bare metal? A VM? A piece of software that "serves"? I'd contest that "VM" is probably the most accurate, but I kind of get it. On the other hand, look at bigger providers like AWS and you wonder if they just throws darts at dictionary pages during Oktoberfest.

AWS definitely requires some cheatsheet to know what they mean. On the flip side of things, props to their team for inventing so much vocabulary (byproduct of launching a lot)

It’s frustrating because you need a cheat sheet for translations. Especially when it’s just the name; no real technical difference. I’m ok with using a unique name to highlight a real differentiator, like how CloudFlare Workers are a slightly different model than Lambda.