just because there's nothing particularly wrong with only getting the usb in on the 3rd try doesn't mean it's not a minor inconvenience worth resolving.

but if you want a more dramatic example, it's right there in the text: Moylan got soaked because of this inconvenience. if he'd gotten a pneumonia as a result of this and died, then that is suddenly much more than a minor inconvenience.

There's a trick to USB, the block part (in the wire) is nearer the ground. ( motherboard-side for vertical desktops )

Since learning that, I have the confidence to stick it in first time rather than 3rd or 4th.

That's not to say that USB-C isn't a huge improvement that has thankfully resolved having to know that.

I like that usbc is double sided but I find them prone to pop out a lot easier than standard usb. It's a weird ask but wish they were bigger

yes I thought this was going to be about jshell too.

jshell is amazing, I don't think enough people know about it!

isn't this exactly what modules and jlink do?

still sucks though

imagine removing the original lionking for the same reason

what is the game?

It's a musical puzzle game called Resynth: https://polyphoniclp.itch.io/resynth It's like a cross between sokoban and a step sequencer!

he (she?) didn't mention anything about offense, he mentioned the possibility of bumping across preconceptions which accidentally harm your ability to communicate an argument.

nor does he say you should patronise; he says understand the problem well yourself so that you can descrive it well and use it to frame the problem, rather than rely on potentially loaded terms. if anything this is respectful rather than patronising

Friends and people you know are fine.

People you don't know but who take the time to leave a considerate message explaining why they would like to connect, is also probably fine.

But some "Jeffrey Epstein" rando wanting to connect without even explaining why should be an instant ignore. You are the company you keep, so might as well know who your company are.

using an instance of a sealed class in a switch expression also has the nice property that the compiler will produce an error if the cases are incomplete (and as such there's also no need for a default case). So a good case for the "make invalid states unrepresentable" argument.

There's nothing stopping you from writing code that is completely functional and devoid of nulls these days. It's just that java obviously still allows nulls if someone needs to use them (partly for interoperability with legacy code)

But if you're going to argue about the mere presence of null being problematic, you might as well complain about the ability to use "unsafe" code in Rust too.

it's even worse than this.

your paid email address would now always end up in people's spam folder by default, because the big 2 don't trust any email not originating from the big 2