syklemil

I'm not entirely sure here, but you are aware you're in a humour community, yeah?

It's a joke because it includes useless letters nobody needs, like that weird o with the leg, and a rich set of field and record separating characters that are almost completely forgotten, etc, but not normal letters used in everyday language >:(

With ASCII æs the åriginal sin. Can't even spell my name with that joke of an encoding >:(

There's some interest in attracting non-awful people from the US. Get a bit of a brain drain going from there:)

What, like an anglophone who can't tell the difference between the i and y sounds?

(Or do the anglos actually pronounce it "tajpst"?)

Isn't that sort of just the cost of doing business in C? It's a sparse language, so it falls to the programmer to cobble together more.

I do also think the concrete example of emails should be taken as a stand-in. Errors like swapping a parameter for an email application is likely not very harmful and detected early given the volume of email that exists. But in other, less fault-tolerant applications it becomes a lot more valuable.

It is pretty funny that C's type system can be described pretty differently based on the speaker's experience. The parable of the Blub language comes to mind.

Parsing is a way of "validating early". You either get a successful parse and the program continues working on known-good data with that knowledge encoded in the type system, or you handle incorrect data as soon as it's encountered.

it really does sound more and more like people think it's Stormblood 2

I feel I gotta point out it's a pretty funny example—email comes up so frequently as a thing that you're recommended to neither parse nor validate, just try to send an email to the address and see if it works. If you need to know that it was received successfully, a link to click is the general method.

But "parse, don't validate" is still a generally good idea, no matter the example used. :)

DAP stands for Debugger Adapter Protocol or something close to that. My impression is it's pretty much the debugger variant of the Language Server Protocol (LSP).

Been looking forward to try the new LSP configuration method!