laughinghan
Joined 16 years ago
Joined 16 years ago
And the LLM makes subtle mistakes perceiving what you were trying to say, and I make subtle mistakes perceiving what the LLM generated.
It's interesting that you seem to think an LLM would be better than you at understanding what someone was trying to say. I have complete, 100% certainty that if a personal friend of mine was having trouble expressing themselves and was concerned about being misunderstood, I would understand what they were trying to say better than any existing LLM. (I suppose the exception would be if the friend was referencing some factual matter I'm unaware of but that the LLM has memorized, like a pop culture reference I didn't get or something.) Do you find that ChatGPT has more emotional intelligence than you?
Given that, do you really think goal #1 non-Web APIs really added much additional delay on top of the delay necessitated by goal #2 anyway?
This paragraph has both:
> The symptom is familiar: a stream that occasionally "locks up" briefly before catching up, jitter in audio or video, or a latency spike that appears to come from nowhere, a "hang" in the application when it gets blocked waiting for a packet. It comes from a single packet forcing the entire pipeline to pause. The underlying network recovered quickly; TCP's ordering guarantee is what made it visible.
So does this!
> WireGuard's protocol is a fundamentally different design point. It's stateless — there's no connection to establish upfront, no session to track, and no certificate authority in the picture. Two keys, a compact handshake, and you're encrypting. And unlike TLS, WireGuard's cryptographic choices are fixed: Noise_IKpsk2 for key exchange, ChaCha20-Poly1305 for authenticated encryption. There's nothing to misconfigure.
I think it’s specifically the resemblance to the clickbaity writing style that Twitter threads and LinkedIn and Facebook influencer posts are written in, presumably optimized for engagement/social media virality. I’m not totally sure what I want instead, I’m pretty sure I’ve seen the same tactics used in writing I admired, but probably much more sparingly?
What is it that makes tptacek’s writing or Cloudflare’s blog etc so much more readable by comparison? Is it just variety? Maybe these tactics should be reserved for intro paragraphs (of the article but also of individual sections/chapters might be fine too) to motivate you to read on, whereas the meat of the article (or section) should have more substance and less clickbaiting hooks?
This thread also has a lot of anecdotal examples of failure modes of 'diverse slate' rules, though, such as people who have already decided who to hire still interviewing women candidates just to appease the rule, thus wasting everyone's time.
It has had the connotation of "mainline", a synonym for "trunk", in version control since before Git existed: https://en.wikipedia.org/wiki/Branching_(version_control)
Presumably this was originally due to the connotation of the railroad mainline: https://en.wikipedia.org/wiki/Main_line_(railway)
Which is exactly the point—the UI is written in HTML/CSS, not the native platform language, and the high-performance modules are written in C++ and Rust, also not the native platform language.
This just isn't true. Look into how Dan Harmon gave a genuine apology and accounting for his wrongdoing and was forgiven. Can you point to Sabatini doing anything that even arguably rises to that level of contrition?
http://github.com/laughinghan