Async fixes one problem with microservices. It does not fix the unexpected latency swings, the network timeouts and errors, the service disruptions when the microservice is unavailable, etc.
or the mismatch between request and response when using HTTP, or the overhead of using RPCs to protect against the previous scenario, or the issue of updating one microservice and not updating all the dependents
A separated component does not necessarily mean a microservice. It could be its own process, its own module, or even just its own function, which is fine. But microservices bring their own problems.
Theoretically, if solar did not make much economic sense at all, it would be purely a signalling thing. And those kind of things do spread by the ”catching on” effect. People might then get solar panels just to be seen as the kind of people who have solar panels, i.e. not the wrong kind of people.
I genuinely believe there's an xkcd for everything. I was only reading about the creator, Randall Munroe a few days ago and he's clearly very talented.
I love Emacs, and while that tour doesn't quite look 1978, it sure doesn't look 2026 either. Maybe somewhere in the middle.. yup, 2002 seems about right.
Don't get me wrong, I don't mind old aesthetics, but... yes? Well I wasn't exactly alive in 1978 but all the screenshots look like they are at least 20 years old
Firstly, the original comment was about UI rather than aesthetics. Secondly, as with everything else in Emacs, you can customise the appearance however you want. Those screenshots are from vanilla Emacs which is admittedly rather ugly. Most people heavily customise, or use an Emacs distro like Spacemacs (https://www.spacemacs.org/) or Doom (https://github.com/doomemacs/doomemacs?tab=readme-ov-file) which have more sensible default appearance configs.
