skobes

But the context of this discussion is the difficulty of installing an APK from outside the Play Store.

The main difference is that signing a Windows binary doesn't require any third party review of the app content.

It is still important to declare UTF-8 either in <meta> or Content-Type header, otherwise it will usually default to Windows-1252. Yay compatibility!

Maybe I'm misunderstanding something about how all this works, but can we have any confidence that 13 million lines of AI-generated Lean code are... correct?

How have we not merely substituted one verification problem for another?

The discussion of "FLIP (First, Last, Invert, Play)" would be improved by mentioning the View Transitions API, which is basically there to automate this technique.

Original Win95 did not even install a TCP/IP stack by default. It was an optional extra on the CD-ROM.

This changed with OSR2 I believe, when they started bundling IE4.

> Look at any printed media from the last 100 years.

I have, and it contradicts your point. The single space is the nearly universal standard in modern print media.

Even the CBC thinks of London, England before London, Ontario.

We are fortunate that this individual's stylistic perspective is out there adding spice and variety to the world. I think, however, that most of us would be ill-advised to emulate it.

Orwell's maxim, "never use a long word when a short one will do", is something the best writers have always freely ignored. But it's a reliable guardrail for the writer of merely average skill, steering them toward something passable rather than vomit-inducing.

I'm confused, this tweet reads like the lead-in or movie-trailer to a story, but where is the actual story?

The map tile backend is in the middle of a multi year effort to migrate from the Flippity Service to the Floopity Service. The FlippityFlooper was believed to have finished the necessary format conversions for all map tiles in the US and Canada but 5% of the data sources were missed due to a bug that was discovered after the creator of FlippityFlooper had been promoted and changed teams, so those Floopity tiles are filled in from an older source. A junior engineer vibe-coded a stopgap fallback called FloopityFlipper that redirects to legacy Flippity Service when Floopity staleness is detected, but that redirect broke three months later due to a change in an injected dependency's experiment configuration. A bug was auto-filed and marked P2 by an overworked product manager who slightly misunderstood the scope, but the FloopityFlipper engineer will probably have a look once they are back from paternity leave.

I made all of that up but it's more plausible than conspiracy theories.

It's funny how your sentences were perfectly capitalized an hour ago, and now your Shift key has become flaky.

I think you can still go directly to /messages/ and not see the feed.

Why is the whole implementation in header files?

I mean, it's also an attentional commitment for me to remember your idiosyncratic apology-preferences. So I might continue apologizing for replying late to your email, unless you convince me that _everyone_ doesn't like this...

My main home PC is a Puget Serenity workstation from 2017. It has been rock solid and outperforms much newer laptops. And it has almost zero fan noise which is a priority for me. Unfortunately it looks like they may have discontinued the Serenity model, at least I don't see it on the website anymore.

Tomorrow: modify man pages from kernel space!

Omitting <body> can lead to weird surprises. I once had some JavaScript mysteriously breaking because document.body was null during inline execution.

Since then I always write <body> explicitly even though it is optional.

Shoutout to fava, the beancount GUI frontend:

https://beancount.github.io/fava/

I really like its big picture view of the accounts, the search / query interface, and live editing of transactions.

This illustrates the difficulty of maintaining a separation between bugs and discussions:

> To be clear, I 100% believe that there is some kind of leak affecting some specific configuration of users

In this case it seems you believe a bug exists, but it isn't sufficiently well-understood and actionable to graduate to the bug tracker.

But the threshold of well-understood and actionable is fuzzy and subjective. Most bugs, in my experience, start with some amount of investigative work, and are actionable in the sense that some concrete steps would further the investigation, but full understanding is not achieved until very late in the game, around the time I am prototyping a fix.

Similarly the line between bug and feature request is often unclear. If the product breaks in specific configuration X, is it a bug, or a request to add support for configuration X?

I find it easier to have a single place for issue discussion at all stages of understanding or actionability, so that we don't have to worry about distinctions like this that feel a bit arbitrary.

This is not a standalone article but a section from Butterick's book, "Typography for Lawyers", which is hosted in full on the website. The book is an opinionated style manual, and many alternatives are described in nearby sections.

I'm fond of STIX Two, which is very close to Times New Roman but just a little bit nicer, especially the italic.

Once I realized that some people expect and are happy for you to jump in with unprompted thoughts or stories, it became easier for me to be intentional about doing so.

I think I'm a lot better now than when I was younger at adapting to a wide range of conversational styles, mostly just from paying more attention to that dynamic.

Do you feel like your conversational toolbox has evolved over time? :)

I hate these too, but I'm worried that a ban just incentivizes being more sneaky about it.

Developers have been anthropomorphizing computers for as long as they've been around though.

"The compiler thinks my variable isn't declared" "That function wants a null-terminated string" "Teach this code to use a cache"

Even the word computer once referred to a human.

If LLMs produce fake citations, why would we trust LLMs to check them?

Wouldn't this fall under Auer deference (agency's interpretation of its own regulation)?

There is some uncertainty about whether Auer deference survives after Loper Bright.

Your link is just the abstract, I had to hunt for the full talk:

https://www.youtube.com/watch?v=U1kc7fcF5Ao

But it is quite interesting and especially learning about the security problems of the document() function (described @ 19:40-25:38) made me feel more convinced that removing XSLT is a good decision.

I tried to read this but the pronouns are so grating

The only thing I know about rock tumblers is that Steve Jobs thinks they're like teams of people building software...

Apple must have been a noisy, violent place :P