HN user
Stinging nettle is known to have been eaten by the celts. It can be boiled or picked, which breaks down the stinging nature of the plant.
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.
> Ignoring requires-python upper bounds. When a package says it requires python<4.0, uv ignores the upper bound and only checks the lower. This reduces resolver backtracking dramatically since upper bounds are almost always wrong. Packages declare python<4.0 because they haven’t tested on Python 4, not because they’ll actually break. The constraint is defensive, not predictive > Man, it's easy to be fast when you're wrong. But of course it is fast because Rust not because it just skips the hard parts of dependency constraint solving and hopes people don't notice.
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.
stgit is similar in that it sits with git, but it's not the same workflow. git-spice has branches per feature that base on one-another. It's more git-like than quilt-like.
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.
Have you seen git-spice? It may be up your alley.
As far as I understand it, this is a still debated question. One theory is it's about evaporating water: Plausible photomolecular effect leading to water evaporation exceeding the thermal limit (https://www.pnas.org/doi/10.1073/pnas.2312751120).
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/)
I'm not an expert, but it looks like the predicted wind reversal did occur.
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...
I believe the author is saying they're willing to relicense the software for commercial integrations.
EIRP is good at reducing uintentional interference. After all, you'd probably wouldn't like me pointing a 20 element yagi antenna through your house, denying your ability to use the spectrum in a reasonable manner, just so I could do a point-to-point fixed link.
EIRP minimizes regulations. It's a good trade-off over operator and installation licencing.
Morse code is fun! It's not just an emergency mode either. Those mountain climbing SOTA hams love code because CW radios are so simple that they can cram several bands into an absolutely tiny QRP rig. Collectors practice on their 80 year old rigs. There's even a club dedicated to making contracts only with straight keys.
Fear not. Code will be with us for decades to come.
I feel the opposite. Morse code was a major barrier into HF for many different people. Folks who are musically challenged would fail to copy. People with hand disabilities faced major hurdles. Hearing disabilities made it impractical, even though there are plenty of visual-only modes (sstv, digital tty modes, etc).
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.
And I learned today that NYC has a 50%-off program for low-income transit users ("Fair Fares"). That makes taking a bus or the subway incredibly cheap.
The last federal gas tax increase was 31 years ago (1993). Most states have similarly stalled gas taxation. Both are also facing the issue of electric cars entirely dodging this tax revenue. It's such a large problem that the Highway Trust Fund is projected to bankrupt in 2028.
In other words, we haven't paid for that road.
To be fair, I believe the author is addressing a beginner audience for inexpensive displays commonly found today. These modern small displays have about 7 times more pixels than those older Nokia ones, which means the bandwidth to drive them in monochrome is the same as driving the color Nokia displays.
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.
The author holds a Finnish call sign, so it would be more appropriate the Finnish authorities (Traficom). That said, it's still a bad look on Apple's design or production engineering. I would expect a higher level of quality.
What a fantastic perspective from the former Uber BI team. I was on the Vertica team during this time period and the amount of effort was spent on incentives mind boggling. Millions a day lost on downtime, product features, or engineering bandwidth was a common theme.
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. :)
To add onto some of the great replies, one aspect of the proposal is much higher power with less harmonic attenuation. 23 db less attenuation with a 20x power increase is going to cause interference in the adjacent ham bands.
As a practical matter, interference complaints from hams are not easily or quickly resolved. Interference from power companies is difficult enough, and they want to know when their equipment is throwing sparks!
It's not like polyester resists forever either. Many outdoors folk have experienced "wet out." Resistance only goes so far and I'd rather wear wet wool than wet polyester.
Synthetics are still great though. They have many other benefits and are easy enough to avoid soaking through.