Ask HN: Is closed-source software inherently evil?

So, I have been around for a while, and seen most of the OSS revolution from the moment that the ASF was born. I have seen things take-off from Hibernate “being adopted” by JPA, and .Net generics being brought into Java… and then bought by Oracle, and Oracle suing a bunch of companies… Let alone all the mess with AWS vs Elastic vs MongoDB and so on and so forth.

So without giving me a lecture on the history of OSS and how it helped move the industry forward (which I know it did!)... the flat, straight-on questions are (and let’s let alone pricing, assume its “free” comparatively to the business you are applying it to):

Are closed-source solutions inherently evil and risk-carrying? Why is that? Why would you NOT choose a 10x solution for your use case only because it’s not open-source?

I’m very interested in your personal experience and from which angle did you look at it in such a situation (for example: developers unable to run things locally in a light-weight manner -vs- enterprise architects struggling with lock-in concerns).

Your opinion is very important, but real-life examples would mean a world for me to better understand it :)

No, lol.

The people who think closed source software is evil are an incrementally small minority of the population who just happen to be very loud about it.

Developers are broadly on the other hand, super cheap, and generally unwilling to pay for software, believing they could write everything themselves and thinking that is always a good use of their time for the business.

No, intellectual property is as evil as nuclear codes, Coke, or Disney. The free software zealots started out as normal guys looking to save a buck and only later came to justify their cheapness with some insane moral legerdemain.

I think I have a personal sense of unease when pieces of my systems are proprietary, very hard to replace, and under control of a different entity. But it's really not my primary concern. My primary concern is moving quickly and not spending too much money.

I am a satisfied AWS MemoryDB customer. It's not open source, but I feel more comfortable that it implements a semi-standard protocol (Redis) so if I needed to get off it I could.

I am also a satisfied customer of Doppler. I briefly looked at Hashicorp's Vault product, but that was just so complicated to use I think the choice of Doppler (or one of their competitors) over Vault is clearly correct for startups. This would be a pain to replace quickly, but fundamentally not that big of a deal, it's just a reliable key value store with a bunch of integrations.

I am still a cheapskate though, like every other developer, we got a quote for Dagster+ for 20k/yr recently, and decided we'd rather keep using self-hosted Prefect.

I think the main takeaway I have from selling software is that selling it to front line developers is a fool's game unless it's cheap and you're going for huge scale. If you want to charge more, you need to sell to someone who has cash, but very indirect leverage over development.

Well, if you had a closed-source product, let's say a distributed KV-store just to say something ... well, I gotta say Redis in the KV-store example I guess... would you stick with Redis because it's -nowadays "somewhat"- open source even if you could get a several "X" advantage in performance and flexibility for the same buck?

I mean, I understand "why" the rise of "BSL" and similar licenses... some players have been a little bit nasty xD, and that's driving a bunch of younger companies that I have been talking to away from open-source as a mean to protect their products... And I'm curious about the community's perception of running "generous" (as in generally free for small business or tryouts) but not actual "open-source" solutions as part of their stack (as in ASL2, BSD or similar hyper permissive licenses).