mpercival531

FTSE Russell is proposing changes similar to Nasdaq, with the consultation ending 18 March.

> Is App Engine still preferable purely for cost predictability?

How is Cloud Run cost not predictable?

It is fairly simple arithmetic in a spreadsheet to estimate the upper bound with # of max instance times the unit prices times the per-instance resources. Exactly the same as you do with App Engine standard & flexible environment.

> budget caps

Doesn’t exist in GCP and most cloud providers. You can fix the usage or hard cap the usage autoscaling, but not the spend incurred by the usage.

> What guardrails work that don’t depend on constant manual billing checks?

Start conservatively with max instances and instance resource, and iterate based on the actual performance and needs. Say, you know, put the number 1 in everything.

Do your capacity planning and cost estimation and understand them. “Solo dev” or not, you need these things to run the business. The root cause was that you outsourced your business and budgeting decision to LLM without verifying it and understanding it.

How iOS Mail gets push inbox updates working with third-party IMAP servers is in the public since 2015/2016 if you look hard enough. That has nothing to do with JMAP the protocol inherently.

It is “notify to pull”.

IMAP servers through APNS ping the iOS Mail about updates in certain pre-registered inboxes. Then iOS Mail re-fetches those inboxes.

The change signal is pushed; the data (inboxes/emails) aren’t.

iOS Mail app does not support IMAP IDLE like any ordinary email clients.

It only supports a proprietary IMAP extension that uses Apple Push Notification Services (APNS) as a sideband channel for IMAP servers to signal the iOS Mail app.

Last I researched this (like… years ago), most IMAP-based email providers that are listed by the iOS Settings have implemented the extension, except for Gmail and Exchange. Fastmail then got on the train since 2015.

Not sure what is with the tweet targeting Fastmail specifically though.

They are. Strix Halo is going after that same space of Apple M4 Pro/Max where it is currently unchallenged. Pairing it with two 64GB LPCAMM2 modules will get you there.

Edit: The problem with AMD is less the hardware offerings, but more that their compute software stack historically tends to handwave or be very slow with consumer GPU support — even more so with their APUs. Maybe the advent of MI300A will change the equation, maybe not.

LINE did.

Listener callout does not have to be part of the synchronous writes. Say if you keep a changelog, listeners can be asynchronously notified. These checks can be batched and throttled as well to minimize call-outs.

I would suspect this is what Google does with Cloud Firestore.

They have abandoned it at their lowest to focus on Zen. Now they seem to start picking up the slack. Upcoming Instinct MI300 APU brings HBM as unified system memory, together with hardware cache coherency between CPU cores and GPUs within and across NUMA nodes.

Each process has its own GCD queue hierarchy that are executed by an in-process thread pool. Though it has some bits coupled with the kernel for stuff like Queue/Task QoS class -> Darwin thread QoS class and relatedly priority inversion.