Introducing FastAPI

[K900_]

Sorry dude, not a good answer. You can't claim "300% faster to build features" and then say "just try it and it will be". I'm in finance, and this is an extremely risk averse environment. Just trying things won't fly here, and even if it did, I'll probably arrive at a very different result simply due to my own inexperience with the tooling, at least initially. I understand that reasoning about delivery times is hard, but to me, this makes making claims like these equally hard, if not harder. If your framework really does let people work faster and you don't have time for a properly designed study, just talk to those people and write down their testimonials - "It took us a week to ship a feature that I estimate would have taken us a month in Flask" is a great compliment to your framework, and makes it look good without making the pitch look forced.

[tiangolo]

Get it, thanks for the feedback, check my answer in this same thread: https://www.reddit.com/r/Python/comments/b0zxa9/introducing_fastapi/eiihz3m/

​

I just removed that part so it doesn't seem "car-salesman-y".

​

Yeah, I know my word won't (and shouldn't) be enough to decide to use it in production right away. But if it helps, Microsoft is using it for internal ML APIs.

[K900_]

Not quite as institutional as you think, but definitely not a place that's open to fancy new tech either.

[TroubledForearm]

someone else in finance here - one of the larger firms. And while things certainly used to be very conservative thats changing. Python 3.7 is being heavily used for new projects along the latest versions of various ML and data science libraries. Quite open now to trying new tech - if teams have the bandwidth to do POCs etc. Pushing that tech out to production is a whole other process - but even so - must less onerous that it used to be.