Yeah, but still - the elephant.

I care about my friends, and if they want to talk about it, I’m happy to listen.

Depending on what the thing is (eg, potential new person) they can be inherently interesting too.

“I love life on Earth… but I love capitalism more.”

You’ve linked into it, but I was just going to point at the Git book: https://git-scm.com/book/en/v2

It’s an afternoon’s reading; it does an excellent job of giving you the right mental model - and a crib aheet of commands to navigate it.

“Maybe our friend doesn’t like monads.”

Experience. For what it’s worth, the instinct I distrust is absolutism.

I think it’s like the distinction between art and obscenity; it’s not a nuanced distinction in the case in question. If it were, I’d largely trust UK courts to get it right (they are by-and-large capable of this, and much less politicised than their US counterparts).

I’m coming around to it.

I think unqualified freedom to say anything can lead to negative utility, pragmatically speaking. Malicious lies bring less than nothing to discourse.

I’m concerned that the libel system can be abused, of course; and I don’t approve of arresting octogenerians under the Prevention of Terrorism Act for shouting “nonsense!” at Jack Straw. But I don’t see there being a need to draw a distinction between online and in person speech, and I think that incitement to riot isn’t something I’d typically defend.

Having said that: I hope the woman in question (who has a history of being a deniable pot-stirrer) gets a trial rather than copping a plea, because the bounds of these things are worth testing.

That’s a cracking article.

My own use of jvm errors tends to follow the same kinds of patterns: I think the major fault with that model is having RuntimeException as a subclass of Exception, because it’s really intended for abandonment-style errors. (The problem is that lots of people use it instead as an exception system in order to cut down on boilerplate.)

I find it eye-opening that the author prefers callsite annotation with try (although I’m not going to argue with their experience at the time). I can see this being either “no big deal” or even “a good thing” to Rust users in particular - mutability and borrowing annotations at both callsite and definition aren’t required to make the language work afaict (your ide will instantly carp if you miss 'em out) but the increased programmer visibility is typically seen as a good thing. (Perhaps this is down to people largely reviewing PRs in a browser, I dunno.) Certainly there’s tons of good food for thought there.

In which case, perhaps unqualified “freedom of speech” isn’t all it’s cracked up to be.

(I appreciate that Chomsky’s opinion resonates more with 1968 than now.)

Have you seen pictures of the sub? What makes you think the wiring was all hidden?

You joke, but watch this:

https://archive.org/details/take-me-to-titanic

from 29 minutes in. A last-minute adjustment before launch plugged in a thruster backwards; no protocol to check the behaviour prelaunch. They doscovered it when they got to the bottom.

I’m not sure why it’s “obviously” good to move from one mechanism to two: as a user I now have to categorise every path to work out which is appropriate.

What I said was less about adding to a function signature than it was about adding to a facade - that is, a system boundary, although the implementation may be the same depending on language. People typically use exceptions pretty badly - a function signature with a baggage-train of internal exceptions that might be thrown by implementation guts is another antipattern that gives the approach a bad rep. Errors have types too (or they should have), and the typical exception constructor has a wrapper capability for good reason.

That’s fine, and for that there are sum types. My own opinion differs - it’s a question of taste. Being able to bundle the handling of exceptional situations aside from the straight-line logic (or use RAIi-style cleanup) is notationally convenient.

Yes, you can do the same with monads; use the tools available to you.

Checked exceptions are powerful but misunderstood. Exception types are a useful part of the facade to a module - they express to a caller how it can go wrong even if used correctly.

Runtime exceptions are typically there to express contract-breaking by callers; although as an alternative return mechanism I’ve seen them used to simplify the inner workings of some frameworks.

I think they get a bad rep because there aren’t a ton of good examples of how to use them - even the java classpath had some egregious misuse initially that helped turn people off the key ideas.

Figure eight on a bight.

That depends entirely on the ability to execute change. CTO is the role that should be driving this.

Developers aren’t the ones at fault here.

Possibly the thing that was intended to be deployed was. What got pushed out was 40kB of all zeroes. Could’ve been corrupted some way down the CI chain.