Tim Bray was always an architecture astronaut, but this example of cloud services for a toy shopping cart app points to an overengineering pathology in our industry. Complexity bloat is real and it has made the cloud fairly noxious. https://www.tbray.org/ongoing/When/202x/2020/08/09/Service-Fabric-News …
-
Show this thread
-
I complained about complexity bloat in a 2015 talk on the website obesity crisis, but that was nothing compared to what people are having to endure today. https://idlewords.com/talks/website_obesity.htm …pic.twitter.com/py5kAqH9TO
5 replies 7 retweets 31 likesShow this thread -
The problem with complexity bloat is not just aesthetic—it prevents cool stuff from being made, creates a pointless barrier to entry for newcomers, and teaches those newcomers who do make it past ineradicably bad programming habits.
3 replies 18 retweets 59 likesShow this thread -
This stuff infects everything. I upgraded a server OS yesterday and my ethernet port renamed itself from "eth0" to "enp1s0f0", just in case I happen to add three datacenters to the backplane.
2 replies 5 retweets 43 likesShow this thread -
Replying to @Pinboard
That's "predictable device names", to avoid the awkward situation where adding a network card will cause all of the names to shuffle around. While change is always annoying, I don't miss having eth0 suddenly be a different adapter after a reboot.
1 reply 0 retweets 2 likes
Yeah, all of the stuff individually has a rationale. Like my hardware raid card has options for grouping and so on that make sense if you have to manage hundreds of drives. The problem is when there's no option to keep things simple and usable (like mdadm in the RAID analogy)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.