Are there any settings to improve the ui? I enabled reduced motion turned but iOS 26 is still intolerable.

Huge thank you for all the amazing work the astral team is doing. uv is an absolute game changer and I can’t imagine going back to a pre-uv world.

I wonder if Esri will provide a similar MCP offering.

Awesome work. I love seeing a community project step up and make a better solution than a multi trillion dollar company.

I’d love to see a collection of every attempt to add encryption back doors to apple/iPhone products. It feels like they never stop trying.

Doing the lord's work

you care extremely deeply about politics such that they align so closely with your personal comfort that you need not have to notice it

Some people actually don't care, other than getting mildly irritated by the people who think politics is everything, and are so captured they can't imagine any other way of thinking.

I do wish various things are better of course, but the typical low and middle-brow discourse is not going to help.

Have you tried beartype? It's worked well for me and has the least overhead of any other runtime type checker.

https://github.com/beartype/beartype

I think TypeGuard (https://github.com/agronholm/typeguard) also does runtime type checking. I use beartype BTW.

pycontracts: https://github.com/AlexandruBurlacu/pycontracts

icontract: https://github.com/Parquery/icontract

The DbC Design-by-Contract patterns supported by icontract probably have code quality returns beyond saving work.

Safety critical coding guidelines specify that there must be runtime type and value checks at the top of every function.

I use TypeGuard too, but only in local dev and pytest runs. I find it really useful so I'm now intrigued to try Beartype too. I found the readme on GitHub confusing at a glance though, I need decorators to type check something?

New Zealand citizenship is looking mighty appealing these days.

how so?

I agree with you. I rarely find myself in a situation where a piece of async code forces me to refactor a synchronous code to be async.

A lot of junior devs I've worked with don't understand that putting `async` in front of a function doesn't actually make it asynchronous.

> A lot of junior devs I've worked with don't understand that putting `async` in front of a function doesn't actually make it asynchronous.

of course it does. annotating any function with async makes it implicitly return a Promise, which fundamentally changes how all callers have to use it (and their caller's callers, etc.). you can't "just" make a function async and change nothing about how it was used previously.

https://jsfiddle.net/om3tj2rd/

  async function foo() {
    return 2;
  }
  
  console.log(foo());

this

> of course it does.

i should clarify a bit, that this can still freeze your UI if foo() is expensive, since the microtask still runs on the same event loop. my point is that you cannot always throw async in front of a function and not change any other code.

I agree, optimizing for readability and maintainability is almost always the right choice.