No, it operates on fixed size blocks over the destination file. However, by using a rolling hash, it can detect those blocks at any offset within the source file to avoid re-transferring them.
2,149 karma · joined November 5, 2010
No, it operates on fixed size blocks over the destination file. However, by using a rolling hash, it can detect those blocks at any offset within the source file to avoid re-transferring them.
I agree with you on this point.
> a datetime
AFAICT, natural sort shouldn't ever make datetimes harder to find, unless they are formatted inconsistently, as in the author's case. Suppose one camera wrote dates as 20250928 and another as 2025-09-28. ASCIIbetical sort would do nothing to help here.
Natural sort can even improve things over ASCII sort, for instance if someone is stuck with a format like "28/9/2025" or "September 2 2025"
> Jonathan Clements founded HumbleDollar at year-end 2016. Earlier in his career, he spent almost 20 years at The Wall Street Journal, where he was the newspaper's personal finance columnist, and six years at Citigroup, where he was director of financial education for the bank's U.S. wealth management arm. He was also the author of a fistful of personal finance books, including My Money Journey and How to Think About Money.
* https://humbledollar.com/about/jonathan-clements/
* A Money Guru Bet Big on a Very Long Life. Then He Got Cancer. https://www.nytimes.com/2024/07/13/your-money/jonathan-cleme...
* https://www.reddit.com/r/financialindependence/comments/1npe...
* Tributes to Jonathan Clements https://humbledollar.com/2025/09/tributes-to-jonathan-clemen...
* Best of Jonathan’s HumbleDollar Posts https://humbledollar.com/2025/09/best-of-jonathans-humbledol...
* Choosing Happiness https://news.ycombinator.com/item?id=32804468 (3 years ago, 101 comments)
(Good) "natural sort" implementations generally have ways of handling ties like this. It's similar to the problem of case-insensitive sort over case sensitive sets.
It'll be interesting to see what the second non-browser-based WASM runtime to fully support 3.0 will be (I'm guessing wasmtime will be first; I'm not counting Deno since it builds on v8). Garbage collection seems like a pretty tricky feature in particular.
Does anyone know how this 3.0 release fits into the previously announced "evergreen" release model?[2]
> With the advent of 2.0, the Working Group is switching to a so-called “evergreen” model for future releases. That means that the Candidate Recommendation will be updated in place when we create new versions of the language, without ever technically moving it to the final Recommendation state. For all intents and purposes, the latest Candidate Recommendation Draft[3] is considered to be the current standard, representing the consensus of the Community Group and Working Group.
[1] https://webassembly.org/features/
Ultimately "all day"/"36 hours" are marketing labels that are at best rough approximations of reality. Your original argument sounds like "if Apple says that the iPhone Air's 3,149 mAh lasts all day, then a 4,500 mAh battery is useless", but as any heavy phone user can attest, with high usage even a new iPhone battery will need to be charged midday, regardless of what Apple says, and an extra 50% battery capacity can be the difference between regularly needing to charge midday and not.
(TSV FTW)
The battery time estimates are based on certain usage patterns, not 100% utilization of power-hungry apps. A battery that can last "36 hours" can offer more real-world usage per day than one that only lasts for 24.
Edit: Looks like the only estimates Apple provides any more are video playback hours, which is much more power-efficient than general app usage and internet browsing.
Jell-O -> Brand -> Business -> Trade -> Goods and services -> Tangibility -> Perception -> Sense -> Biological system -> Biological network inference -> Inference -> Logical reasoning -> Mind -> Thought -> Cognition -> Mental state -> Mind (Loop!)
What the parent commenter is referring to is actually called a Navbox (https://en.wikipedia.org/wiki/Wikipedia:Navigation_template). Like @chatmasta, I think it would be interesting to label those types of links distinctly and allow excluding them.
Or perhaps alternatively, exclude the contents of those navigation templates, but allow using them as an additional node: David_Bowie -> Template:Grammy_Lifetime_Achievement_Award -> Enrico_Caruso. (In this case, that is redundant with the main non-template Grammy_Lifetime_Achievement_Award page.)
It looks like Deadbolt also hit QNAP and Terramaster.
> Probably another environment variable
Having any of the existing XDG_* environment variables set is an incredibly-clear indication that the user wants the XDG spec followed.
> Put app-created support files in the Library/Application support/ directory. In general, this directory includes files that the app uses to run but that should remain hidden from the user. [emphasis added]
> 2315 was the original number of Wordle secret words. After the New York Times acquired Wordle, it was revised down to only 2309 secret words.
The NYT puzzle is no longer beholden to any specific list for solutions. There's now a larger list (of 3200 words) that Wordlebot thinks are now likely to be solutions based on NYT word frequency data, but some recent solutions (like KEFIR and LORIS) have come from outside even this set. (The NYT did however add those words into the Wordlebot dictionary just before those puzzles went live.)
> 12972 possible 5-letter words
Likewise, the number of legally guessable words has been increased to 14855.
> If the standard is continuously updated and they feel they can just make arbitrary changes to how grapheme clusters work at any time, how is any software that's not "evergreen" (I.e. forces users onto the latest version and pretends older versions don't exist) supposed to deal with that?
Why would software need to have a permanent, durable mapping between a string and the number of grapheme clusters that it contains?
They made the horizontal cuts evenly spaced between the cutting surface and the top of the onion, which is nonsensical to me. I believe that a single horizontal cut at around 15-20% height would be better for uniformity than a horizontal cut at 50% height.
I feel like you haven't used most date libraries.
https://docs.oracle.com/javase/8/docs/api/java/time/YearMont... / https://docs.python.org/3/library/datetime.html#date-objects / https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
I'd also love to be able to filter out a style, to drill down to the examples that aren't just the multi-tier ("free/basic/pro/enterprise") vertical cards (which doesn't seem to have a dedicated style tag—maybe "Stacked Cards"? but there's a lot that look like that that don't have that tag).
This doesn't seem like an accurate description, since it's designed to trigger the same dopamine release as shopping, just without the real-world consequences.
I'm confused by the NoBucks Rewards ("Need $xx.xx more NoBucks; Complete anti-consumption tasks to earn more"; <https://justbuynothing.com/rewards>). Obviously no real products are getting shipped. I'm not going to make an account on this site but can NoBucks actually be earned? What happens when you've earned enough to actually "checkout"?