It's not so funny anymore.
15,621 karma · joined September 20, 2011
It's not so funny anymore.
Back then, I believe, Stross had already conceptualized "corporations as slow AI", (which is a separate concept from above).
[1] which you can read for free online https://www.antipope.org/charlie/blog-static/fiction/acceler...
First, thank you for taking the feedback :)
To be clear, I'm focusing on the first thing you should be telling users. It seems that, as a CLI program, the target audience of this tool is fairly technical users who are likely already familiar with SSH, rsync, and everything. As demonstrated in this thread, your first communication task is to convince them why it's worth their time to use your tool, considering they're probably satisfied with the pre-existing ones (or a replacement would already exist!).
My point is, explaining why it's better/faster than rsync shouldn't be buried in the docs. It should be a paragraph on the front page.
Hope this helps, and keep it up. HN is a rough audience to go public on ^^;
As an aside, It's perhaps an indictment of our networking landscape that multiple parallel connections between 2 specific machines would accelerate a transfer. I would've expected a single TCP connection to be able to saturate a line. Or perhaps the parallel connections seeks to amortize the per-file setup overhead?
Into the Spider-Verse, for breaking away from the 3D animation movie style
[1] https://www.reddit.com/r/movies/comments/1w58qjb/hi_reddit_i...
My favourite is his answer to being compared to an actual coyote catching an actual road-runner: https://www.reddit.com/r/movies/comments/1w58qjb/comment/p7d...
But a few hours into the tutorial, at a point of yet another "go gather 20 wolf Pel^H^H Ores from that other planet and bring it back", and I lost interest.
The inner gameplay loop didn't work for me, and I need that hook.
Have there since been improvements to that inner loop?
In contrast, Destiny 2 keeps hooking me back in because its inner loop, the gunplay and abilities, and variety of builds, really works for me.
Apple produces a "small" phone (S or Mini series) only every few years because that's enough to saturate that market.
https://www.nytimes.com/2026/02/16/movies/muppet-treasure-is...
> Curry emphatically denied that interpretation. “I saw the Muppets as actors with distinct personalities,” he said. “It’s astonishing how quickly you see them as people.”
There has been a ton of work to improve throughput, but that's often come at the cost of latency, because a great technique to improve throughput is batching, to avoid the per-task overhead cost.
We've also added many layers of abstraction.
A seminal example is Dan Luu's "computer latency" table (2017) https://danluu.com/input-lag/, which measures the time between a keypress and visible changes on the screen, and wherein an Apple IIe has latency 5x lower than a Lenovo X1 Carbon on Windows.
From some perspective, you could say that the Lenovo on Windows example is an impressive feat of engineering, considering all the subsystems involved (USB, interrupt dispatcher, input layer, windowing system, double-buffering...)
This throughput-over-latency tradeoff can be seen across the entire computer landscape design.
[1] also known for open-sourcing ProtoBufs v2, creating CapnProto and Sandstorm, and commenting on the recent Cloudflare OS post https://news.ycombinator.com/item?id=49182996
But they're also quite explicit and repeat the directive (including during the exit interview) about removing Apple files from your account when you leave, and logging out of iCloud from the Apple devices you leave behind.
Also:
> At some point, LE asks MA to sign out off LE's iMessage account
You can sign out remotely, so this would've been stupid of everyone involved.
Then again, this whole situation demonstrates a level of stupidity from supposedly competent people that I wish I could say was unbelievable. Add "Making a public post about a topic under litigation" under that category too.
... said every spammer.
I'm sorry for your pain, and I'm in the same boat.
But it's important to understand that any sufficiently large, distributed-agent system (like federated email), will see the rise of parasites that will pump resources and diminish the value of the system.
What we're seeing here is an "immune" response to those parasites. We all pay for it.
I think this is an important lesson for anyone designing a distributed-agent system [1]. How do you design it so as to keep the bad actors out, or at least so their impact is negligeable?
[1] imma make my own email system! With blackjack, and hookers! oh wait...
> I am creating a RAIDZ1 (RAID 5) zpool. That means 1 drive redundancy in-case of failure
A friend once told me that RAID5 has a high latency cost, because every Write requires a Read to update the stripes across all drives, and while this made sense when drives were expensive, nowadays you might as well do a RAID10 instead, and trade space for latency.
Is this still true with ZFS RAIDZ1?