|
|
|
|
|
by technion
634 days ago
|
|
Imagine aws offers a hosted node application service. Then, because aws doesn't give anything back, npm blocks the aws ip range, and suddenly existing aws customers can't install modules or security updates. That's pretty much what happened here. I get the "you should give back" ideal, but make no mistake, this is because wp engine is eating their lunch. |
|
Anyone is still free to use the source, but the services they provide are not free.
> Imagine aws offers a hosted node application service. Then, because aws doesn't give anything back, npm blocks the aws ip range, and suddenly existing aws customers can't install modules or security updates.
It's a good analogy. AWS does it a lot, but it does so with open source projects that do not have much paid services. Reading from the article, Automattic provides many services (possibly paid, in some freemium model).
I'd welcome if some projects manage to get AWS to give back. They do way too little if you ask me.
> I get the "you should give back" ideal, but make no mistake, this is because wp engine is eating their lunch.
Yes. Giving back could be a deal that involves money.