Ask HN: Is closed-source software inherently evil?
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 :)
13 comments
[ 3.8 ms ] story [ 43.1 ms ] threadThe 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.
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.
Did I grossly misread something?
Good value is probably the most important thing; the value could be speed or efficiency or whatever, but that's obviously the first bar.
Open source is not high up on the list of questions.
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).
Where is the added value for the end user in your opinion?
Absolutely not.
> Why would you NOT choose a 10x solution for your use case only because it’s not open-source?
Because software being open source (in the general sense) gives that software an enormous advantage all by itself. Even if proprietary software is "10x", it's still burdened with the rather large disadvantages of being proprietary.
I buy and use proprietary software, but only when it enables me to accomplish something I can't accomplish with open source software. And even then, I'm keeping an eye out to be able to ditch the proprietary solution as quickly as possible.