Live data from Hacker News

AWS Chalice

github.com

21–30 of 37 posts

Re: AWS Chalice

#21

Anyone here actually developing Python apps on AWS Lambda? If so do you use Serverless Framework or something else? I am part of a research project that is developing techniques for identifying security vulnerabilities in serverless apps so would be interested to understand what people are actually using for deployment and why.

If you try to use serverless (the framework) for Python, you very quickly learn that its support is a second-class citizen vs building in TS/JS.

Adjacent concern but: It also makes for unholy large Docker images to combine an entire JS toolchain with an entire Python toolchain.

Zappa is a better (more native) choice.

Terraform modules provide a decent Python Lambda experience.

AWS also has multiple semi-overlapping projects in the space. Chalice, SAM, and Powertools specifically to name a few. CDK more generally as well.

Re: AWS Chalice

#22

Hilariously, "chalice" is a strong swear word in Quebec French, so there the name of this product is roughly equivalent to "AWS Fuck". https://en.wikipedia.org/wiki/Quebec_French_profanity

If I'm reading right, you also giggle and roll your eyes whenever you're asked to connect to a host.

I was told by a Canadian anglophone that the French Catholic tradition was strict about cursing, so what happened over generations was that actual Church words turned into the cussing words.. the example given was the French word of "Tabernacle" if you say it with loud outrage by itself, it is definitely cussing..

Re: AWS Chalice

#23
post #9

Hilariously, "chalice" is a strong swear word in Quebec French, so there the name of this product is roughly equivalent to "AWS Fuck". https://en.wikipedia.org/wiki/Quebec_French_profanity

What a bizarre phenomenon. Per that article, the word chalice does mean chalice, but is treated as a swear word precisely because it doesn’t have any profane association and has sacred overtones? How then would one discuss these topics at all? Is this an attempt to wipe out all the words entirely?

In Quebec French, the general motif for swear words is to use church related terms [0].

Common examples:

* câlice [kɑːlɪs] (calice): "chalice"

* ostie [ɔs.t͡si] (hostie): "host" - as in sacramental bread

* tabarnak [ta.baʁ.nak] (tabernacle): "tabernacle"

[0]. https://en.wikipedia.org/wiki/Quebec_French_profanity?wprov=...

Re: AWS Chalice

#24
as a previous contributor and user, I would not recommend.

as a project in the GitHub aws organization, it can not accept non amazon external maintainers.

as a project, it has a single maintainer, doing on average, an hr every few months.

as a result of both of those , its not able to keep up, or reach critical mass on community.

it has fallen fairly far behind current lambda feature set. for a simple throw away, its okay, but if you want to grow something or take advantage of new features in the underlying service capabilities or integrations, this is a dead end.

I filed this ticket a few years ago https://github.com/aws/chalice/issues/2067

Re: AWS Chalice

#25
post #9

Hilariously, "chalice" is a strong swear word in Quebec French, so there the name of this product is roughly equivalent to "AWS Fuck". https://en.wikipedia.org/wiki/Quebec_French_profanity

What a bizarre phenomenon. Per that article, the word chalice does mean chalice, but is treated as a swear word precisely because it doesn’t have any profane association and has sacred overtones? How then would one discuss these topics at all? Is this an attempt to wipe out all the words entirely?

The swear words in Quebec originate from old religious principles, yes. You can differentiate between "good" and "bad" (swear) use of it purely from written context or verbal cues. The verbal cues are a lot easier to pick up on. Sarcasm, angry face, crass conversation amongst friends, etc.

Re: AWS Chalice

#26

Spin something up in an hour; spend a week fixing it when the magic inevitably breaks. Maybe I am just incredibly jaded but I can't stand all these shortcut frameworks. It just ends up locking you into an ecosystem, especially AWS, and decouples you from building technical understanding of the system where if you go down the path long enough, you have no abort button besides an entire re-build because your code is en…

[deleted]

Re: AWS Chalice

#27

Spin something up in an hour; spend a week fixing it when the magic inevitably breaks. Maybe I am just incredibly jaded but I can't stand all these shortcut frameworks. It just ends up locking you into an ecosystem, especially AWS, and decouples you from building technical understanding of the system where if you go down the path long enough, you have no abort button besides an entire re-build because your code is en…

Every framework have worked on for the last 12 years has bugs, breaks in certain situations. Every system in fact, i have worked on in 12 years has bugs and breaks. That is just the nature of software development.

You should be using frameworks instead of trying to reinvent things. It takes away decision fatigue and makes it easier for most teams to follow conventions that are already established.

Re: AWS Chalice

#28
post #24

as a previous contributor and user, I would not recommend. as a project in the GitHub aws organization, it can not accept non amazon external maintainers. as a project, it has a single maintainer, doing on average, an hr every few months. as a result of both of those , its not able to keep up, or reach critical mass on community. it has fallen fairly far behind current lambda feature set. for a simple throw away, its…

[deleted]

Re: AWS Chalice

#29

Hilariously, "chalice" is a strong swear word in Quebec French, so there the name of this product is roughly equivalent to "AWS Fuck". https://en.wikipedia.org/wiki/Quebec_French_profanity

[deleted]

Re: AWS Chalice

#30
post #4
post #2

It seems dead? https://github.com/aws/chalice/issues/2067

> It seems aws focus is now at https://github.com/aws-powertools/powertools-lambda-python

its not quite the same, roughly 60-70% of chalice code by volume is actually helping auto provision. power tools is about 70-80% code by volume is integration with other services/capabilities in aws (tracing, logging, metrics, etc). the overlap is the event routing shims/decorators.
Post reply on HN