It's a bit like 2 space indention versus 4 or 8 space. I find the em-dash example pretty compelling because visually relaxes my eye more than commas do — similar to how prefer at least 4 space indention over 2.
(Unrelated: The alt-code for em-dash on Windows is Alt+0151. I just typed my first manual em-dash wow exciting.)
Something interesting is the author right away wants to isolate and reduce placebo. But surely, latency is all about "placebo" and "vibes" and "feel" is it not? The ultimate test is how it feels to use on a personal level.
Of course, where gathering this sort of data _is_ useful is diagnosing and fixing real latency so it obviously has merit. I just think it's ok to lean on taste and experience for most things UI/UX, including latency.
Another point, by couching the comparison in a less technical form (for example, rating a configuration/setup out of 5 stars or some similar approach), it protects from being "too methodological" during testing and data-gathering. One possible issue with the author's methods is if there are degenerative cases that are common in the day-to-day experience of a given configuration, they are unlikely to be present during the precise test that they have setup.
Yeeeeep. There is no moat at the moment. AI companies are trying to dig one as fast as they possibly can. Either through passing laws to prevent local inference ("It's too dangerous! We need to control it") or by creating/limiting possible integrations (locking down OS/hardware, APIs/MCPs that only work with Claude/ChatGPT, etc).
As someone who went down the keyboard only blackhole, I've rebounded all the way to mouse maximization. Mice are nice! Another tip that really helped me is embracing good mouse acceleration (i.e. not the Windows or Mac built in garbage). This tool has honestly made using a mouse at least 3x better for me: https://github.com/RawAccelOfficial/rawaccel
Frankly, this comment does little to avail the parent's point - doing this on the open road was both illegal and reckless. It reflects extremely poorly on your character and the project as a whole.
100%. MSDN is the definition of saying nothing with as many words as possible. I guess if you wanted a case for why LLMs are helpful, MSDN is a good one haha
It is important to note that this is a deal struck for just some ethnic groups of the citizenry. It does not apply fairly across the board to all people under Chinese governments' control so it's not even as good as it sounds for the average Chinese citizen.
As often the case with Dan's letters, a well balanced take on many issues. I particularly appreciated the thoughts on AI and (what I read) the undertone of infrastructure being the real differentiator between the US effort and China. We'll see how it plays out this year. "May you live in exciting times" etc.
This matches my experience. State management is the key thing - you end up needing to put way more on the backend then you'd otherwise like to. Quick example: something like a multi-step "wizard" is far more difficult to express in HTMX than with any SPA-ish pattern.
I don't want a more conversational GPT. I want the _exact_ opposite. I want a tool with the upper limit of "conversation" being something like LCARS from Star Trek. This is quite disappointing as a current ChatGPT subscriber.
There are two of us! I also espouse the virtues of TortiseGit any time I am able! I do take a bit of guff at work, but one feature of TG I've never seen equalled is how it handles what I call "drill-down git blame adventures". TG'a blame lets you easily keep going down through a files commit history in a way that is both intuitive and useful. My only issue with TG is that it is so Windows-focus and as I'm working more and more in Linux I will tragically need to leave it behind ;_;
(Unrelated: The alt-code for em-dash on Windows is Alt+0151. I just typed my first manual em-dash wow exciting.)