3 ms·

They only added Zappa to the README after the nagging, but were kind enough to do so: https://github.com/awslabs/chalice/issues/27 https://github.com/awslabs/ch

by Mizza 10y ago

They only added Zappa to the README after the nagging, but were kind enough to do so: https://github.com/awslabs/chalice/issues/27 https://github.com/awslabs/chalice/issues/27 I don't have any grudges against Amazon for doing this, but it's kind of a shitty feeling to work on something for free for a long time and then see a corporate giant widely publicize an inferior product without even acknowledging your efforts. Imagine how the guys (I don't remember their name now) who sold hosted MySQL instances on EC2 felt when RDS came out! That paragraph was just to get that off my chest, I guess. Now that I've written this to clear up the confusion (people were constantly me asking about the differences), I think I can move on.

talawahdotnet 10y ago
I get where you are coming from, but things are often less Machiavellian than they seem, even if they feel that way. The Chalice team seems to have their own ideas about how to approach the project, some may overlap with yours and some may differ, from the conversation in the issue you mentioned (https://github.com/awslabs/chalice/issues/27 https://github.com/awslabs/chalice/issues/27) it seems like they were open to discussing ideas, but they wanted the freedom and control to experiment in their own project. As with most ideas there is room for different projects and approaches and the landscape is constantly changing so it will be hard to tell which will survive. Even API Gateway's recent addition of the proxy integration feature makes things a lot simpler and probably made some code from all these frameworks less relevant. So yes the internal AWS "team" has advantages in terms of being able to post to their blog and perhaps being privy to internal developments before you are, but that is just the way it is. Looking at GitHub the team appears to really just be one person https://github.com/awslabs/chalice/graphs/contributors https://github.com/awslabs/chalice/graphs/contributors. I just think we should have an open mind and allow for the possibility that they are trying to explore their own ideas and address what they perceive as their customers' needs rather than assume they are trying to crush all similar projects in the name of corporate greed.
WhitneyLand 10y ago
You gotta remember they're just a very large corporation who doesn't care about you. It's business for them not personal. I've partnered with Amazon on development projects before and it was really great for a while and then not great at all when no longer suited their needs. It's not always fun but comes with the territory when you're a small team or company playing on the same field with giants.

by Mizza 10y ago

talawahdotnet 10y ago

I get where you are coming from, but things are often less Machiavellian than they seem, even if they feel that way. The Chalice team seems to have their own ideas about how to approach the project, some may overlap with yours and some may differ, from the conversation in the issue you mentioned (https://github.com/awslabs/chalice/issues/27 https://github.com/awslabs/chalice/issues/27) it seems like they were open to discussing ideas, but they wanted the freedom and control to experiment in their own project. As with most ideas there is room for different projects and approaches and the landscape is constantly changing so it will be hard to tell which will survive. Even API Gateway's recent addition of the proxy integration feature makes things a lot simpler and probably made some code from all these frameworks less relevant. So yes the internal AWS "team" has advantages in terms of being able to post to their blog and perhaps being privy to internal developments before you are, but that is just the way it is. Looking at GitHub the team appears to really just be one person https://github.com/awslabs/chalice/graphs/contributors https://github.com/awslabs/chalice/graphs/contributors. I just think we should have an open mind and allow for the possibility that they are trying to explore their own ideas and address what they perceive as their customers' needs rather than assume they are trying to crush all similar projects in the name of corporate greed.

WhitneyLand 10y ago

You gotta remember they're just a very large corporation who doesn't care about you. It's business for them not personal. I've partnered with Amazon on development projects before and it was really great for a while and then not great at all when no longer suited their needs. It's not always fun but comes with the territory when you're a small team or company playing on the same field with giants.