this post was submitted on 07 Nov 2023
157 points (94.9% liked)
Programming
17314 readers
24 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Because while you do have control (and "copies") of the source code repository, that's not really true for the ecosystem around it - tickets, pull requests, ...
If Microsoft decided to fuck you over you'd have a hard time migrating the "community" around that source code somewhere else.
Obviously depends on what features you are using, but for example losing all tickets would be problematic for any projects.
Apparently Mozilla won't be even accepting PRs there so it doesn't matter much.
What if you self host in AWS and Amazon decides to fuck you over? What if you decide to self from home and your ISP decides fuck you over? What if? So many what ifs... How do you even live in this world?
Yeah like, wtf
When you use a cloud solution (and especially one with a vendor lock in like Amazon) then yeah, you are fucked there too and I'd question why you did it in the first place.
If you have your own infrastructure - be it a server at home or whatever - then you can always just move it elsewhere, get some other ISP, whatever. There is no lock-in. Inconvenience, sure, but you can migrate elsewhere. That's just not true about all the other things mentioned, or the friction would be much higher.
Have you actually used anything cloud? Because there's literally no friction to move things around. Unless you decide to use proprietary features.
With AWS especially there is a shitton of proprietary stuff. Most of the friction is in knowledge however; the cloud environments differ, are configured differently, have different limitations and caveats, etc. Someone who has only ever worked with AWS will have to learn a lot of things anew if they switch. Hell there's a reason why "AWS engineer" is a dedicated role in some companies.
Now, if you only manually set up some VMs and configure them like you would a regular server then sure, it's easy to migrate. But when you are missing 99% of the features of the cloud environment are you actually using it?
For me the purpose of the cloud is the ability to deploy my projects on rented infrastructure independently of the provider. Tools like Terraform and Kubernetes help with the abstraction of providers.
As for proprietary features I prefer to use open source alternatives like Supabase, which I then can deploy to any cloud and migrate between clouds if needed.
Well then you aren't probably taking advantage of most of the stuff AWS offers and is actually really good for. Which isn't really criticism, but then I wouldn't really call it cloud? It's more like just infrastructure as a service.
Infrastructure as a service is literally the definition of a cloud. Everything is just bells and whistles.
The announcement to drop Mercurial quite clearly states that their workflow won't change and that GitHub pull requests are not considered a part of their workflow.
Also, that's entirely irrelevant to start with. Either you care about software freedom and software quality, or you don't. If you care about software freedom you care about having free and unrestricted access to FLOSS projects such as Firefox, which GitHub clearly provides. If you care about software quality you'd care about the Firefox team picking the absolute best tools for the job that they themselves picked.