116
Death by a thousand microservices
(renegadeotter.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Sep 2023
116 points (96.0% liked)
Programming
16670 readers
92 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
If you've ever followed the C++ committee discussions you'll see they put a lot of time and effort into considering legacy code when introducing language changes. For better or worse existing languages are on a trajectory set from their inception that can't always be easily redirected. New languages are free of this baggage and can wildly experiment.
I wish languages were more willing to release breaking versions, like a C++ v2 or such. That's not to say languages don't already have breaking changes between versions (Python comes to mind), but it would allow people to start fresh and clean up obsolete designs and libraries.
You know the cleaning up probably won’t happen. If some dependency doesn’t work anymore because Python introduced a breaking change, then you stick with the old Python version.
Python is actually a good example of this: see the mess that the transition from 2.6 to 3 generated.
Python 3.7 is another good example. The new await and async keyword broke a lot of programs.