AWS is a company made up of human beings, with the capacity to choose to do good. If they do things that we would consider to be immoral, we can absolutely blame and judge them for that, regardless of whether it's "what they do".
I was wrong to say that you can't blame Amazon for doing what they do -- what I should have said was that people shouldn't be "surprised". Work yourself into a fit over it if you want, but the next time it happens, you shouldn't be surprised.
My point was meant to be that sharks do shark things, and companies that are Amazon's size do things that companies at Amazon's size would do. Both happenings should not illicit much surprise.
> AWS is a company made up of human beings, with the capacity to choose to do good. If they do things that we would consider to be immoral, we can absolutely blame and judge them for that, regardless of whether it's "what they do".
This is great in theory, but there are such things as shareholders, fiduciary duty, and binding financial covenants. Companies have a capacity to choose to do good, but they have a stronger duty to produce profit for stakeholders. Companies can be ethical, but there is no reason to believe that they will be unless it's written into their bylaws, or they are structured differently from the outset (ex. Mozilla Foundation).
Another article hit the front page from 2019 about Google vetoing the power of a privacy-focused W3C working group to prevent technical changes that would hurt privacy. This is another instance -- you can blame and gnash your teeth all you want, but Google is going to do what Google does, and that's offer technological advancement and ease at the cost of privacy (sometimes) if it helps them sell more/more expensive ads.
However, there has been a perspectives of seeing organizations as a form of AI (I read it on HN somewhere), and if you look at it from that perspective the ethics become bureaucratic which opens a whole can of worms of what that means :)
Don't _exploit_ the generosity of other people. Use it and contribute back to it. Framing it as something to exploit really emphasizes the need for the GPL.
I did not disparage F/OSS, the exploitation was about what is happening right now and will continue to happen -- corporations (and have started to realize that they can leverage F/OSS for their own ends, whether it's releasing open core stuff, or using CDDLs and getting people to sign over commits (which are IP), or making the code permissively licensed but controlling the development through other means.
I also believe F/OSS is a beautiful thing, which is why I try to look at what is happening with it optimistically and cynically.
P.S. Example of "other means" -- I personally think this is the model that Kubernetes and some other large single-company-backed F/OSS projects is doing, they've essentially built bureaucracy which replicates the internal politics you'd find at a large company, and I think it'd be quite difficult for a regular contributor, no matter how ardent, to get a "board seat" if not backed by some large company. Kubernetes was a better tool than others, but Google also spent a lot of money to propel it forward.
The way I see it in the way my grandparent meant it, exploitation is a capitalistic word and frame/narrative. For example, all companies are exploiting employees (by gaining a profit on them) and certain business opportunities in some shape or form. That doesn't mean it's necessarily bad as "giving back" might be part of that exploitation. Many businesses have incentives to keep the exploitation sustainable.
If you have an issue with this, then you have an issue with capitalism, IMO. And that's fine, but I wouldn't frame it as having an issue against exploitation.
If you can't hear the issue with your language, go tell your reports that you've decided to exploit them.
Communication is key!
Definition of exploit: transitive verb
1: to make productive use of : UTILIZE
exploiting your talents
exploit your opponent's weakness
2 : to make use of meanly or unfairly for one's own advantage, exploiting migrant farm workers
The article is about definition 2 folks.
Perhaps you're confused because of the order the comments appear in? You might have to see the time stamps, and track the numerous replies I made in the tree of comments.
The word "lead" also has several definitions, among them: the metal, and the thing you use to walk your dog. A dog needn't be involved in the former, nor the metal in the latter.
I'm simply using the least charitable language to describe what I'd like to do (and what AWS has already done) -- there's no need to sugar coat. If someone (normally a group of people) has worked hard to create some software, and released this software as open source, and I take to hosting it for profit, I am exploiting their efforts without a doubt if only in the most literal definition-driven sense.
As one would "exploit" natural resources, I would be taking the product of their effort and used it to generate profit. Whether they were kind or noble has nothing to do with it, though of course I agree that F/OSS is one of (if not the) largest and kindest sharing of knowledge in human history. I owe my career to F/OSS and the community that powers it (and of course a few schools and teachers along the way), I haven't forgotten.
What I was trying to point out is that it's relatively easy for me to make a decision to give back 10/20/30+% of revenue (never take % shares of profit, see the movie industry) as a bootstrapper, where companies who are VC funded may not be able to make such a choice easily because they have other capitalists to answer to.
> Don't _exploit_ the generosity of other people. Use it and contribute back to it. Framing it as something to exploit really emphasizes the need for the GPL.
This is very close to my point -- if you don't want this to happen (no matter what someone calls it), pick the appropriate license -- BSSL or a similar license. Do not depend on the kindness of strangers, it's not a good long term strategy -- the GPL was invented to give that ideology teeth and it's been outrageously successful.
Sentry, a well known and liked player in the error reporting space does so[0]. People use Sentry, and contribute to it, and love it. People who think picking GPL licenses will offer the same protections are somewhat misguided, the closes you can get is AGPLv3 which to be honest isn't even right, because hosting unmodified versions seemed to be permitted.
I call it exploitation because that is what you have to assume that companies (which exist for a very specific reason in just about every economy in the world) will almost certainly skew in the direction of exploitation, they are basically duty-bound to do so.
[0]: https://github.com/getsentry/sentry/blob/master/LICENSE
As much as I dislike AWS's heft (which I think allows it to muscle in on spaces it isn't the best at, and people will happily choose worse products because they're "backed" by AWS), I also think there's a lot of value in the F/OSS world to be exploited, and I'd like to do the exploiting someday. I'll leave it to others on whether it's right to draw the line at size of corporation, but I'd be just as "in the wrong" as AWS is.
There's no reason both the community and the corporate interests trying to profit (entrepreneurs who want to offer hosted versions included) can't have a symbiotic rather than parasitic relationship -- all it takes is returning some of the revenue to the appropriate open source projects and supporting them. Postgres and the related companies have been making it work for a long time now. I think part of what's exacerbating this parasitic relationship might be the VC model -- if you make some open-core software, take a bunch of VC money (or don't and simply overstretch your reach), and now need to find some hypergrowth (tm) to keep the house of cards the right side up, maybe it makes more sense that the relationship would be more parasitic than symbiotic.
A lot of newer developers are about to find out the difference between F/OSS and shareware.