di VS json-parser-in-typescript-very-bad-idea-please-dont-use

Indeed.

The dep injection is fastapi and typer code though, and quite tied to it. So it's worth mentioning that somebody is attempting (quite successfully from the look of it) to create a generic lib of dep injection using annotation named DI, inspired by those libs: https://github.com/adriangb/di

Also, to clarify because I realized my comment above was confusing: I did not mean that 1 file == 1 function in the def a_function sense, I meant it in the "functionality" sense. So for example di/_scope_validation.py is a piece of functionality (validating scopes) and so it is in it's own file instead of being at the top of di/container.py. I guess the entire project could be a 1000 LOC container.py file, I think I would personally find that a bit hard to digest, but it's for others to read not me so...

We provide some basic benchmarks comparing to FastAPI.

[1]: https://github.com/jamiebuilds/json-parser-in-typescript-ver...

Also, shoutout to this guy who implemented a json parser in typescript types. This is what gave me the idea.

The next examples get progressively more bonkers, so I'm not going to write down all my thinking about them - you should check them out though and see if you can see how they work. The JSON parser is probably the best mix of complex and readable.