9 ms·
In 2019, multiple open source companies changed course
- Wowfunhappy 7y ago> Since the SSPL forces any SaaS software that is aggregated with the covered software, but not a derivative of it, to nevertheless be open source, it fails this test. Broadly speaking, what is the utility in not allowing this?
- Doctor_Fegg 7y ago> Open source licenses vary, but the gist since the 1998 founding of OSI has generally been as follows: you can take this code and do what you want with it, but you can't make the code proprietary, and if you use it in another project, then that project can't be proprietary either What? No, that's not what "open source" means. Not at all. That's "copyleft" or "viral" or "sharealike", but not a universal definition of "open source".
- gpderetta 7y agoIt is not even the definition of free software. The FSF itself acknowledges that permissive licenses are still free software. (all free software licenses are open source and viceversa, the different nomenclature is only a matter of principles).
- KaoruAoiShiho 7y agoErr yeah of course it's the right move. The article says that the other alternative to pure open source is proprietary. Well obviously proprietary is bad for society, so if there is a way to construct a license that's at least partially open that's way better than completely proprietary. It's sad but I feel that AWS in 2019 has completely killed a business model.
- ThrowawayR2 7y ago> "It's sad but I feel that AWS in 2019 has completely killed a business model." AWS didn't "kill" anything since everything they did is allowed by the terms of FOSS licenses and was known to be possible for many years. It would be more accurate to say that there was never a valid business model in the first place. People originally wrote FOSS to "scratch an itch", not make money.
- foobiekr 7y agoAmazon can have killed the business model even if that model was fragile.
- AlexB138 7y agoI'm a big fan of open source, but why is it obvious that "proprietary is bad for society", exactly? I'd venture to guess that most of the people that frequent this site work for companies that sell proprietary software in some form or another. People being employed is pretty beneficial to society.
- tastythrowaway 7y agoMy guess would be that the long tail of proprietary (due to existing market, mergers, de-facto standards, etc.) favors a greedy incumbent, which has basically never in history worked in the favor of the many. But published, open standards allow for greater adoption and participation, as well as a longer support lifespan.
- ahnick 7y agoThe FSF provides a fairly long (strongly worded?) list of reasons on this page. https://www.gnu.org/proprietary/proprietary.en.html https://www.gnu.org/proprietary/proprietary.en.html IMHO proprietary software is better than no software, but open source software is better than proprietary software in terms of societal benefit. My favorite open source business model is the "Free Software Product" model. (Best articulated here -> https://sfosc.org/docs/book/business-models/#free-software-product https://sfosc.org/docs/book/business-models/#free-software-p...) The core ideas are: 1. Free software products have trademarked, proprietary distributions, with commercial terms attached. 2. Free software products (may) have 100% open source distributions, but they must use different trademarks and naming conventions, and receive no direct customer support or interaction from the upstream. They are strictly downstream repackaging of the proprietary upstream distribution. This is true regardless of which source code repository is being committed to - the user relationship is defined in terms of the commercial product, not the free software project. By either using this model on its own or combining it with OpenSaaS, I think it is entirely possible to run a profitable business, while providing public access to the code that benefits society.
- quantummkv 7y ago> As Perens puts it, "we have to draw a line between 'open source' and the right to make money with open source. The open source definition allows, but does not support, your right to make money. We're not going to change the rules because you can make money better that way." This right here. When you open source something, you are basically volunteering to write code. By the very definition, volunteering to do something does not entitle you to anything. Imagine how weird it would sound if people started asking money to volunteer in soup kitchens. If you think you are entitled to something for your work, don't volunteer. Make it a service and charge. If you think writing some code used by someone entitles you to some money, make it proprietary code and start charging like Microsoft does. No one is going to stop you.
- coldtea 7y ago>Imagine how weird it would sound if people started asking money to volunteer in soup kitchens. That's basically what NGOs are...
- lostcolony 7y agoSlight nit: when you open source something, you're not even volunteering to write code. There is no obligation on your part to continue supporting it at that point. You're simply giving out something that cost you some time (no materials). Which may explain why people can feel entitled to getting paid for their efforts; we tend to feel that if we give something to others they owe us something back (this is why we have a bunch of laws against giving and accepting gifts in certain situations, because of the societal pressure to make it an equitable exchange), and it sometimes takes intentional reminding of ourselves that that's not how giving works, and that there is no actual quid pro quo obligation.
- bonoboTP 7y ago> Slight nit: when you open source something, you're not even volunteering to write code. There is no obligation on your part to continue supporting it at that point. You're simply giving out something that cost you some time (no materials). Whether you offer paid support or not has no bearing on whether you release your code under an open source license. Many companies offer support contracts for their open source software. Many paid employees work on open source software, not only volunteers (Google, Facebook, Canonical, Red Hat, SchedMD and so on). Open source and commercial are not antonyms.
- branon 7y agoAh, feross again. This is the guy behind the npm 'funding' fiasco. He wants to (and did) put ads in your terminal: https://github.com/standard/standard/issues/1381 https://github.com/standard/standard/issues/1381 _Some people_ might have you believe that if free software isn't generating ad revenue, or isn't being relicensed for cloud deployments to make gobs of money, then it's somehow "unsustainable." I disagree, and choose to disregard most projects that behave this way.
- dang 7y agoYou appear to have posted this just because he is the submitter of the article. Is that true? If so, that's crossing into personal attack, which is not allowed here.
- branon 7y agoNot meant to attack. I thought it was funny to see an article of this specific tone. Made sense after I realized who OP was. I don't dislike the guy, I just know his views, and choose to contest them.
- dang 7y agoOk, that's fair. But intent doesn't express itself in internet comments, unfortunately, so if you don't disambiguate up front, you're likely to be interpreted through the most common filters, which alas are the nasty ones. I know it's extra work, but the burden is on each of us to do that. feross has submitted a ton of great articles to HN and is often the first user to find them. From that we all benefit, regardless of our views on ads, etc.
- xvilka 7y agoI am rooting for two Rust alternatives to Elastic stack - Sonic[1] and Vector[2](logstash alternative). Too bad they currently cannot work together[3]. Java is a poor choice performance-wise, and in a scaled applications it can make a huge difference. [1] https://github.com/valeriansaliou/sonic https://github.com/valeriansaliou/sonic [2] https://vector.dev/ https://vector.dev/ [3] https://github.com/timberio/vector/issues/988 https://github.com/timberio/vector/issues/988
- pstuart 7y agoThis looks interesting as well: https://nbsoftsolutions.com/blog/replacing-elasticsearch-with-rust-and-sqlite https://nbsoftsolutions.com/blog/replacing-elasticsearch-wit...
- edsiper2 7y agoLogstash alternatives with Elasticsearch support: [1] https://www.fluentd.org https://www.fluentd.org (Ruby Language) [2] https://fluentbit.io https://fluentbit.io (C Language)
- jbk 7y agoWhat’s wrong with the AGPL, that they cannot use it, as a software license?
- zeckalpha 7y agoWhy can’t they use AGPL?
- ausjke 7y agoenlighten me here, how AGPL can protect Mongod been AWS-ed? i.e. AWS makes money out of it without paying Mongo
- ausjke 7y agoso even asking a question here got downvotes these days, how can I improve... "would you please enlighten me here, how AGPL can protect Mongod been AWS-ed? i.e. AWS makes money out of it without paying Mongo, I just do not know much about the difference between licenses honestly and am genuinely interested in it. I did check tldrlegal.com" -- will this be enough to not hurt the downvoter's feelings?
- colejohnson66 7y agoYou’re probably being downvoted for coming off snarky with “enlighten me”
- ausjke 7y agothanks. I often got downvoted without a clue to myself, everything has to be perfectly 'politically correct and grammar perfect' these days, maybe because I was not a native speaker per se. I do feel that some people here are so sensitive these days, to the point I sometimes think their mental health is probably not that great, I know this is going to trigger more downvotes, you're welcome.
- zackbrown 7y ago
- zubspace 7y agoA very interesting article. As I read it, SaaS providers can integrate GPL code in their service without opening up any of their code, competing with other, similar services. But, isn't that what open source is about? Providing an utility for everyone to use, even in a corporate setting? It's like someone providing a Linux distribution with a license which says, that you're not allowed to make money with it. I think MongoDB from the article simply provided a SaaS service, which was too simple too copy without any unique features. Ain't this their own fault?
- tsimionescu 7y agoBasically, open source software that has stood the test of time has either been supported by non-commercial entities (e.g. GNU, Firefox) or has been a collaboration of many commercial entities (e.g. Linux, clang, Java). Trying to sell a free product that you are developing does not seem like a workable business model. Open-source products which are developed almost entirely by a company with a questionable business model are unlikely to remain healthy in the long run.
- gpderetta 7y agoAs pointed out elsethread, it seems to be working for Qt.
- _frkl 7y agoI think open source software providing (free) utility for everyone is just a side effect, not the original intend behind it. The original intent, as far as I'm aware, is to let users use and modify the software without restrictions. This obviously leads to the free utility, but if there was a way to achieve the former without the latter, it would be ok. There isn't, and so my argument might sound a bit silly. I do feel it's an important distinction to keep in mind when talking about the politics of it though.
- dimitar 7y agoMost of the examples appear to be NoSQL datastores. Now it is kindof obvious why Datomic is not open-source. And yet software like Wordpress has thrived for many years without their creators being tempted to change licenses (Wordpress.com wasn't crushed by AWS, shared hosting or even WP-as-a-service vendors). What is different about these DBs?
- ohazi 7y agoConsumers don't really care whether the software they use is open-source, they'll just use whatever looks good and works. So hosted WordPress does well, but Medium also does well. Engineers are rightfully wary of using proprietary databases. Decades of bugs leading to integrity issues on decades worth of data. They're not willing to relive those days. Luckily, the world of open-source, battle-tested, academically reviewed databases is large and mature. So any upstart peddling funky "throw out all that academic rigor and try this nosql shit" is rightfully squinted at. Open-source has essentially become table stakes for DBs, since no engineer will look at you otherwise. These nosql companies are trying to be proprietary while still meeting the table stakes. Given the other expectations around open-source, the whole thing has a "two kids in a trenchcoat" look to it.
- kemonocode 7y agoAt this point I have yet to work on something that absolutely needs a NoSQL database so I may be a bit biased, but my general impression is they're a solution looking for a problem- or rather, the wrong solution to the wrong problem. I have used things like key-value stores such as memcached but it's also the kind of tools you don't use liberally unless you absolutely must. Perhaps a bit of obscurity isn't that bad of a thing after all. Doesn't help that people have been talking about the issues with NoSQL for quite a few years now [0] [0] http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/ http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-ne... (although I do wonder how much of these points still apply)
- ohazi 7y agoAs far as i can tell, NoSQL is a reasonable way to store data that would otherwise go in a directory of files. If the lookup is anything more complicated than "I know exactly which file I want because I saved the relevant key in a real SQL database," then you're probably doing something wrong. Too many people start with NoSQL because "we gotta be cloud scale" without actually thinking about their data model, don't want to redo everything the first time they realize they need to do a join, and end up bolting on a slow, broken, inconsistent query system on top that ends up being orders of magnitude slower and more expensive than postgres running on a laptop.
- microcolonel 7y agoThe Action Button thing is cool. Seems like it could multiply the political importance of the publication.
- lacker 7y agoSometimes it feels like the conventional wisdom is that open source is struggling for a business model. But despite the competition from AWS, MongoDB is now a public company worth $7 billion. Quarterly revenue is $90 million. It seems like they have found a decent business model, to me. The formula: make popular open source software, get an audience of people who happily use that software, sell related services to that audience.
- cycloptic 7y agoMongoDB is not open source software anymore. The article even mentions it so: "The SSPL is not an open source license and it never will be."
- bitwize 7y agoIt looks like open source in the traditional sense is on the wane. Powerful forces demand license stipulations that conflict with open source licensing. The social justice crowd doesn't want their software used by ICE, and big companies don't want their code releases to undermine their business model. In the future, hackers sympathetic to Extinction Rebellion may want to deny access to their software to organizations who contributed to global-warming denialism. Eventually the OSI leadership will resign; they may be pressured to do so very soon. There are too many powerful interests for whom the OSD as it is poses significant problems.
- zby 7y agoOpen Source is about licenses - Saas is making licenses obsolete. I think the story is more about universal cloud providers dominating specialized Library as a Service providers (AWS dominating MongoDB) - the fact that the smaller providers publish their software as OpenSource is not relevant to the story, Amazon could publish their solution as OpenSource and still kill MongoDB. https://medium.com/hackernoon/aws-and-mongo-and-open-source-efcdcfb00514 https://medium.com/hackernoon/aws-and-mongo-and-open-source-... It all leads to very big and probably monopolistic cloud providers. To have more competition maybe what we need is mandating Open Source for Saas. We would also have some positive externalities in the form of code. Businesswise this would not be a big deal - exactly because selling the full package (i.e. cloud provided Saas) is dominating selling licenses. There are some technicalities to overcome - like how/where it should be published, what should be published (what is the source? what code is really used in Saas and what is internal code?) and when it should be published (immediately upon going live?). It can also be justified on the grounds of people should know what they are buying.
- na85 7y ago>Saas is making licenses obsolete Exactly this. I don't see the point of, say, the AGPL because it can't possibly be enforced: Short of a whistleblower or other leak, have no way of knowing if I'm connecting to AGPL software, or merely something that's API-compatible.
- _frkl 7y ago> >Saas is making licenses obsolete > Exactly this. I don't see the point of, say, the AGPL because it can't possibly be enforced: Short of a whistleblower or other leak, have no way of knowing if I'm connecting to AGPL software, or merely something that's API-compatible. I don't think that is people's main concern. As a developer I'd trust that most companies will honour the terms of a license, and if they don't it'd be unknowingly in most cases. It's too much of a legal risk, and not worth it in most cases. The issue is that GPL licensed software can be legally used in Saas use-cases because it needs to be distributed for the gpl to get triggered. In the case of AGPL that loophole is closed, but it's still possible to use AGPL software in a Saas product in the case where it is not used directly, basically. For example, in most cases it's legal to call an AGPL command-line application you modified from a backend service, without having to share your modifications. At least that is my understanding. Either way, my point is that the concern is about legal use-cases, not illegal ones.
- BFatts 7y agoUnfortunately "you can take this code and do what you want with it, but you can't make the code proprietary" is not the Open Source definition AT ALL. This applies to software released under the GNU licenses, or copyleft licenses. Open source can MOST DEFINITELY be made totally proprietary.
- flurdy 7y agoIs there a new license in use that allows fairly open use but not as a for-profit SAAS? Is that what SSPL tried to do? For years I hoped the LAGPL (Lesser Affero GPL) would turn popular. [1] But I guess it needs a bigger organisation behind to get real lawyers to write it and promote it. In essence I'd just want MIT+NOSAAS or Apache+NOSAAS. [1] http://mo.morsi.org/blog/2009/08/13/Lesser_Affero_GPLv3/ http://mo.morsi.org/blog/2009/08/13/Lesser_Affero_GPLv3/