The more I read about these kind of article the more I am amazed that our digital future is at hand in utterly incompetent people.

This person clearly have no understanding of monadic error (AKA Maybe/option monad or slightly more advanced Either monad), which is the first monad we teach at a class targeting second year undergrad.

The performance comparison is just plain factual error. The functional error code will continue to compute n2 when computation of n1 failed; the same do not happen in the exception version. If you compare codes with completely different traces, of course they will have different performance...

A properly implemented monadic error will return as soon as compute for n1 failed, and never execute the rest of the code. This is the default and idiomatic behavior in Haskell, OCaml, F#, and rust. This performance problem doesn't even happen in LINQ-style handling like in C# and Kotlin (maybe also Typescript?).

The point of monadic error is that its control flow is local, whereas exception is non-local. Specifically, the exception can be handled and occur anywhere in the code base, with no indication on the type level. So programmers will be constantly worrying about whether the exception in a function call is properly handled.

Even worse, when you try to catch a certain error, there is always the risk to accidentally catch similar exceptions in a library call or someone else's code. Writing good code with try-catch requires a lot of principle and style guides. But unlike monads, these principle and rules cannot be enforced by the type system, adding extra burden to programmers.

In fact, we have known for a long time that non-local control flows (goto, break, contiune, exception, long jump) are the breeding ground for spaghetti code. As an evidence, many non-local control flows (goto, long jump) are baned in most languages.

That being said, there are certainly cases, with proper documentation, that exception style is easy to write and understand. But I think they are very specific scenarios, which have to be justified on a case-by-case basis.

Many people don't know usb-c cable is universal, and apple only advertises chargeing iphone with macbook and ipad charger.

I imagine most of these people use an iPhone, and they will certainly waste their money on an "Apple cable".

Plus many of these tech-illiterate people are likely on a lighting iPhone with a barrel jack Windows, they won't even know they need a new charging cable until they realize their old lighting cables don't work.

Probably runs at usb2 speed and charges at 5w.

There are support table on asahi wiki. For example, here is the support page of M2: https://github.com/AsahiLinux/docs/wiki/M2-Series-Feature-Support

It is missing thunderbolt, touch id, video decoder, video encoder, DP alt mode, pro res, PCIE etc.

The cat is playing poker with two mice in the last panel.

I cannot find anything related to "the promised 10 years of lightening". Do you min providing a source?

That didn't pass as far as I am aware.

I was talking about usb-c, and I don't care about RCS, but it is still better in everyway than SMS.

Forced by EU! Thanks again, EU.

I want to say "live to see another day", but on retrospect, that is indeed, quite boring.

Then if you care about the artists being compensated fairly, you can CD+rip; if not, streamrip/torrent will produce a lot less waste and much more convenient.

TBH most big names are millionaires anyway, I probably would care much more about my convenience than them getting paid 5 bucks for all my troubles.

If you can download music, you can either host your own using navidrome, or just use a local player like auxio.

The only downside to this approach is that the artists you like might not get compensated fairly, as most streaming service pay by stream times. This is also why I prefer buying music than streaming.