Not sure what your point it. I shared my experience working with systems, you can share yours (if you have any).

Yes, you can write any of the stuff in assembly. Erlang, Java, Rust, all can be written in assembly. You can serve web pages in that too, and even create distributed system by twiddling bits directly in the network card's receive buffer.

> This stuff is what frustrates me most about the vocal early adopting crowd.

Lol, early adopters ;-) Erlang turned 30 this year. It is probably older than the median age of people reading this comment.

> Again, this isn't language or framwork-specific.

Again, point to where I said "nothing like this can be done in any other frameworks". Code reload -- can do it in Java. But you'll get paper cuts. Python -- can spawn an OS process to get fault isolation, but, can only spawn so many. Distribution -- spin another instance in AWS, talk gRPC with it, but now you are paying more money and have another library to maintain.

> But citing resilience, efficiency, scalability, and handling traffic spikes seems thin

Well would you prefer a whitepaper? It is an informal conversation. Do you ask for proof / benchmarks / whitepapers every time you talk to someone at a meetup? That must be fun.

But if you want a fun reference, pick up your smartphone, navigate to a web page. Does it work? Good. There is 50% chance it works because Erlang works. There you go, scalability, resilience and efficiency ;-) can share that at the next meetup's beer hour.