Yep, this post is awful in many aspects, throwing rants here and there w/o ever making a point.
I have no idea how this got so many upvotes!!.
In a few years we'll hopefully be out onto the slope of enlightenment, with microservices applied where they're useful and not applied where they're not. If we don't get there, then we'll just run the whole hype cycle over again with yet another rebrand of the same concept.
And in general, putting a network boundary between function calls is gonna add a whole bunch of complexity.
That being said, splitting services so that teams could deploy independently definitely also had a lot of benefits at FB, but I could never understand why so many much smaller companies took the micro services approach.
My opinion is that the default should be to keep things in one service and only split them out if there's a very good technical or organizational case to be made.