fedora atomic desktops (silverblue, kinoite, and derivatives like bluefin etc) are really great. They are as up-to-date as fedora, with an additional layer of stability provided by its atomic and image based nature.

my money is on vi or vi derivates.

I don’t think google will allow them to move to chromium. They need gecko to avoid anti-trust law suites.

Yeah, I believe the official instance of EU and ACM are both quite small. It is a great way to verify people’s identity just from their ID.

In Maybe monadic, its monadic bind will automatically resolves any failed computation, and don’t need explicit checking.

for example, the code in Haskell looks something like the following:

fib: Int -> Int -> Maybe Int
fib depth idx =
  do
     guard (depth < 10)
     n1 <- fib (depth - 1) (idx - 1)
     n2 <- fib (depth - 1) (idx - 2)
     return (n1 + n2)

Haskell type class system automatically figures out this is a maybe monad, and check for error accordingly.

Notice, unlike the C code the author provide, this haskell code will exit immediately when n1 failed and never compute n2, similar to the behavior of the exception code. Thus I believe his point about performance is at least unjustified, if not wrong.

Another interesting fact about this code is that there is nothing that is built into the compiler/interpretor (except the do expression, which is just a minor syntactical sugar), you don’t need to design special semantics for raise and catch. Everything here, guard, return and the definition of Maybe monad (which is in charge of propagating errors) is defibed by the user using normal functions, no metaprogramming involved.

Wouldn’t effect systems still be considered exceptions, but handled differently?

Yes, unlike monad, the error is propagated by the compiler/interpretor, instead of user defined. But unlike implicit effect, explicit effect (algebraic effect, throwable, etc.) makes it clear how the code can go wrong.

Although explicit error is more clear in general, there are special cases where explicit effect is undesirable. One such example is effect pollution, where low level effect that is unlikely to cause impure behavior is necessarily propgated through the call stack. Making the code more verbose and harder to handle.

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 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 code with completely different trace, of course they will have different performance… A properly implemented monadic error will return as fast as compute for n1 failed, and never execute the rest. This is the default and idiomatic behavior for any properly implemented monad, like in haskell, ocaml, F#, and rust. This performance problem even shouldn’t happen in linq style handling like in C#, Kotlin (maybe Typescript?).

The point of monadic error is that its control flow is local, whereas exception is non-local. Unless you have clear documentation about the possible error, then the return value is deceptive. And the error can be handled anywhere in the code base. And programmer knows non-local control flow (goto, break, contiune, exception, long jump) is the breeding ground for spaghetti code, so that many non-local control (goto, long jump) is baned in most languages.

That being said, there are certainly cases, with proper documentation, the exception style is easy to write and understand. But I think they are specific scenarios that 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.

runs at usb2 speed probably.

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 have never litter trained a baby rabbit, but they generally just poop where there is hay.

Sometimes it is also helpful to pick up their droppings and put it in the litterbox, but it is largely not necessary.

They are different, the little balls are hard poop, which they will not eat. I think cencotrope are only on their butt, but I am not sure.

But they still insist that they need to consume more of it.

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.