A function executes, and some error happens:

- Return error value: try to handle the error ASAP. The closer to the error the more detailed the information. Higher probability of recovery. Explicit error code handling throughout the code. Example: maybe you try again in one millisecond because the error is a very low probability but possible event.

- Exception: managing errors requires a high-level overview of the program state. Example: no space left on device, inform the user. You gather the detailed information where the error happened. The information is passed as-is or augmented with more information as it bubbles up the stack until someone decides to take action. Pros: separate error handling and happy path code, cleaner code. Cons: separate error handling and happy path code, unhandled errors.

Worst case scenario: you program in C. You don't have exceptions. You are forbidden to use setjmp because rules. A lot of errors are exposed directly to the programmer because this is a low-level language. You return error codes. Rules force you to handle every possible return code. Your code gets incorporated as an appendix to the Necronomicon.

And now my personal opinion: If we are going the static typing way I would prefer simply to use Scala or similar instead of Python with types. Unfortunately in the same way that high performance languages like C attracts premature optimizers static types attract premature "abstracters" (C++ both). I also think that dynamic languages have the largest libraries for technical merit reasons. Being more "fluid" make them easier to mix. In the long term the ecosystem converges organically on certain interfaces between libraries.

And so here we are with the half baked approach of gradual typing and #type: ignore everywhere.

"There is no legal responsibility for a landlord to enforce the payment of taxes by their tenants, nor any suggestion that Aziz should be paying the bill."

This usually makes some sense. But in this case it is obviously being abused. I guess that a police investigation would need to track the flow of money back to the landlord. Or put in place better legislation. Banks for example cannot claim ignorance about their clients and are required to deny access to their services if something does not look good.

https://github.com/akermu/emacs-libvterm

and

https://github.com/suonlight/multi-vterm

Reasons: - I can compose queries, which in turn makes them easier to decompose - It's easier to spot errors - I avoid parsing SQL strings - It's easier to interact with the rest of the code, both functions and objects

If I need to make just a query I gladly write SQL

The earth moment of inertia is about I=8e37 kg m2 [2]

The energy extracted by a slowdown of angular speed from wa to wb would be 1/2 I(wa2-wb2).

Approx wa=2pi/86400 and wb=2pi/86401. Energy extracted: 4.9e24J=4.9e12TJ.

We would have energy for about 12 billion years.

If I double check with Kagi's assistant with Claude 3.7 (I'm in my phone and I could easily have made an error) it starts with my exact reasoning and figures but messes up final numbers (so close!!!) to give a total of 40 billion years, which nevertheless is the correct order of magnitude.

[1] https://en.m.wikipedia.org/wiki/World_energy_supply_and_cons...

[2] https://scienceworld.wolfram.com/physics/MomentofInertiaEart...

While the focus has been on olives, the bacterium’s ability to infect such a broad spectrum of plants makes it an agricultural nightmare, particularly in regions where multiple crops are grown in close proximity.