Using stimulants prescribed for ADHD to have extra pep in your step is drug abuse - just sayin. You see this a lot with adults taking stimulants for ADHD.
One suggestion to the authors - every serious codebase I've ever worked on had their own set of linters and plugins for whatever linter they were using.
How do I extend Ruff? Can I extend Ruff? How do I write plugins and linters? It's Rust in Python and I am generally leery of such things. The fact that it's one tool to do all these things makes believe it's because the tool is inflexible so it must be able to do all these things.
simply rendering tables - most of the (python) pdf generation libraries I evaluated a few years ago all had the same limitations (reflow is hard) around laying out large multipage tables. We went with a headless chrome service to print to pdf which did not have the limitation.
How well does this handle large tables that span pages? That seems to be a key differentiator for most PDF libs I sampled. I'd assume this works well if it's coming from Chromium
you can pick a alternate browser on IOS and as I said - it was multiple instances
Go in your google/android settings and make sure location tracking is off - come back and tell me with a straight face that the UX of the feature is not a dark pattern.
Why would some be branded damaged because they have knowledge of a tool? That's ludicrous.
I've used many databases including mongo. They are all tools like any other with pros and cons and having experience with multiple across domains is a boon.
Another commenter illustrated some of the issues you will run into with this pattern at scale.
It would probably help to benchmark some complex queries on a sizable data set. And compare against mongo, postgres jsonb, vanilla eav, clickhouse, etc. Without much information to go on, it's hard to know what this is.
Are you unrolling the nested JSON data structures and storing as traditional K/Vs in an EAV pattern? Possibly using one table for each datatype or using a sparse table?
I'd be curious how this performs for complex queries - does this rely heavily on index intersection?