I thoroughly enjoy uv, having used poetry and requirements.txt prior, but it does come with its faults in a large codebase. Admittedly, I don’t know whether they re due to uv’s infancy, or PEP restrictions.
For example:
1. uv sync should update by default (like poetry)
2. uv lock revision and dependency resolver keep changing and it makes it hard to figure out if changes to our uv.lock are real or due to separate versions of uv among developers
3. uv pre-release dependency rules should be able to be disabled with either a sys_marker or specific case like pinning a version
Some other pain points but I can’t remember them all at the top of my head..
I agree with you until you bring foodbabe into this. She’s notorious for hand-picking things that meet the MAHA agenda. For example, the oats argument, yes there is a ton of crap in the ultra processed Quaker oats, but that’s an old recipe. Here’s what they sell at target:
There’s not always a one-to-one comparison, and I agree shady companies in the US have free rein over what crap they add to our foods, but this has already been debunked.
They changed the recipe after it received significant attention. Before then the company was happy to use food coloring on Apples to pretend it had strawberries while actually providing strawberries in another country.
The thing is you can’t bring attention to every single product, which is the point of regulations around deceptive packaging.
I don’t know for sure but it looks like in the image the oh so simple is a different product line. Seemingly similar to all of Lays chips which come in normal and the healthier line.
2025 Ioniq 5s have the NACS port (only in NA markets, obviously). I don't think the 2025 Ioniq 6s do, though they probably will for the next model year. Like you said, CCS-equipped cars can use the Tesla network with a NACS-to-CCS adapter.
