I agree in theory, but the problem is that I have been burned over and over again by proprietary tooling. The interests of the dev tool makers often do not alig

I agree in theory, but the problem is that I have been burned over and over again by proprietary tooling. The interests of the dev tool makers often do not align with my interests as a developer, and that's a problem. Proprietary tool vendors are just trying to create shareholder value. If that means firing the entire dev team and never doing another release, they will do that. If it means switching from "pay once, use forever" to "pay $20 / month", they will do that. If it means going from $20 / month to $2000 / month, they will do that. If it means putting ads inside my IDE, they will do that. Just look at what Broadcom is doing to VMware to see what this can look like in practice. OSS developer tooling is usually made by and for the community. The interests of the dev tool makers align with the interests of the developers using it, because they are the same people. There are no incentives to enshittify my developer experience, so I can safely rely on the tooling without worrying about whether it'll still be usable next year. And even if the core team decides they want to make some wildly unpopular changes, the rest of the community can still fork it and continue on their own direction! I really wish it wasn't the case, but there are very few proprietary tool vendors I'd be willing to believe if they promised they wouldn't ruin my day a few years from now by doing a rug pull. Some small just-started firm I've never heard of? Probably not in that list. I would love to cut them a break, but trust has to be earned.