nsotelo's comments

Not all shows need portability so why stop them all? Desktop applications absolutely, but It's trivial to build, deploy and operate docker containers on servers.

Nothing is absolute, of course if you take it far enough the seams of the argument tear but there is merit to it.

A senior browser frontend developer is likely to pick up mobile development quite quickly.

Likewise someone who's been doing Spring Boot Java backends for years and is proficient with databases, caching, etc. Isn't necessarily going to find it hard to switch to a serverless nodejs paradigm.

The network card person is probably able to handle the embedded microwave oven.

Etc.

Matrix is an open protocol and anyone's welcome to build a front-end, inspired by Telegram, that your mother would be happy using.

Perhaps you meant the Element client?

As English speakers we often take for granted acronyms such as DB or even USA. For foreigners these can also be inscrutable.

There are many scenarios where it's useful, but I will illustrate a simple and important one.

When you do a rolling upgrade, a new service must be assigned to an available port different to the existing one. After starting you'll probably run some health checks, and once satisfied you'll want to switch traffic over to the new instance and halt the old. How do you tell the rest of your infrastructure what the new port is? Service discovery.