pc486
Joined 7 years ago
Joined 7 years ago
Version bound checking is NP complete but becomes tractable by dropping the upper bound constraint. Russ Cox researched version selection in 2016 and described the problem in his "Version SAT" blog post (https://research.swtch.com/version-sat). This research is what informed Go's Minimal Version Selection (https://research.swtch.com/vgo-mvs) for modules.
It appears to me that uv is walking the same path. If most developers don't care about upper bounds and we can avoid expensive algorithms that may never converge, then dropping upper bound support is reasonable. And if uv becomes popular, then it'll be a sign that perhaps Python's ecosystem as a whole will drop package version upper bounds.
What you get is git-styled patch-series development. Branches on branches where each branch maintains history of the feature.
A git-spice workflow is compatible with GitHub style PRs where a PR depends depends on another PR.
Or pair git-spice with format-patch you can share with developers who prefer patch files. Or take patches from someone and import each patch as a branch, then let git-spice track the stack position.
There are black plants though! And they're studied for the same kind of questions. E.g. The Functional Significance of Black-Pigmented Leaves: Photosynthesis, Photoprotection and Productivity in Ophiopogon planiscapus ‘Nigrescens’ (https://pmc.ncbi.nlm.nih.gov/articles/PMC3691134/)
In the article there's this figure: https://www.climate.gov/media/16838
The March 13th 10hPa forecast with the wind reversal and lobe is visible on measured data: https://earth.nullschool.net/#2025/03/13/2100Z/wind/isobaric...
EIRP minimizes regulations. It's a good trade-off over operator and installation licencing.
Fear not. Code will be with us for decades to come.
Removal of morse has allowed far more people to reach more technical levels of ham radio. And, in my anedotcial experience, dropping the requirement hasn't impacted the popularity of morse code. I'd wager its more popular than ever because of how many more hams have HF access compared to limiting access to folks who learned code just to pass a test and to promptly throw away their key.
In other words, we haven't paid for that road.
The advice of "if color, start with SPI" is simple and mostly correct. Good enough for a target audience of engineers just starting with hardware.
A director asking for an exact spreadsheet to be the UI would have been par for the course, especially during the Uber China days. Heck, I personally loaded FX prices into Vertica from a spreadsheet emailed every month to the team. That process remained for more than a year as there just wasn't enough bandwidth to invert the control as automated ingestion.
Thanks for digging up these memories, @bastawhiz. I'd love to see more. :)
Also, cook books are a modern invention. You're not going to find a collection of thousand year old recipes by looking at written records.