This is the first Mac I’ve personally owned. I had a lot of criticisms in the pre-M chip era, it just felt to me like you paid twice as much for branding and kind of weak hardware. But it’s hard to deny how much of a jump the M chips are now, and competitor prices have crept up.

Local LLMs, a zillion concurrent processes with elixir, doesn’t seem to matter what it is. It’s just cool as a cucumber at all times. Coming from non M chip hardware, that’s absolutely nuts to me. My old rig would literally be on fire if I did half of this.

Razing awareness is the new zeitgeist

I think part of the reason why is:
If no one’s name is on it, then no one is responsible and so how could any failure be anyone’s fault?

Tempting for corps, infuriating for customers. Leads to employees systemically not caring as much about quality or customer experience and general disconnection.

You can fit so many spinners in this bad boy 🚗

Bold of you to assume I have anything to do on any night

Thanks, and exactly!

A nice side effect is that it tends to result in features that people are more likely to intuitively understand. And in the code base, something other developers can understand more easily.

That's a good question! I just assumed they are because that would make the most sense, but I haven't actually used this method to grab events themselves before so I'm not sure.

For your use case where you want the events themselves, I'd call the events API and grab those instead, triggered by receiving a webhook.

A frustrating but (I've found) more reliable option is to trigger an API call to get the latest data when webhooks come in. Depending on frequency and the situation you can debounce/deduplicate so you're not slamming API calls more than some rate, too.

That's probably true, but no, I think I don't think I'd feel right doing that. At the end of the day it's a US corp, with all of the unfortunate things that entails, and I wouldn't want to mislead people about that even by accident.

Being Canadian while having a US corporation has been a uniquely tense experience lately, I'll say that.

This is in addition to the inbound load balancing we already have, which balances based on region, connection count, etc.

That inbound handles which part of your Approximated cluster a request should go through, and the upstream load balancing decides which upstream to send it to.

This is extra handy if you want to have your app running on multiple hosting/infra providers and load balance between them for redundancy, costs, etc.

Or if you just don't want to manage a global load balancer on your own infrastructure (or your provider makes it hard to do).

Also, is there anything with liveview that could work similarly? Wondering about ways to have frontend stuff coexist with liveview easier. Maybe the same thing but for event handlers?