Honestly so glad to see the reversal.

Whatever problem we might have with them, they explicitly say that they do not do this in the launch post.

https://github.com/tekacs/zeroserve/commit/b33f261615d20d55b...

It does leave me wondering about other runtimes that could be used as the go-between though, because at the point of compiling Rust, an approach like Cloudflare's Pingora (https://github.com/cloudflare/pingora) which I've tried using before... in _theory_ should be a 'nicer' solution - just historically awkward when I've tried using it the way that I'd have liked. Wish it were more library-shaped!

On top of that, small VTOL craft that can hover and would be at lower speeds closer in (esp. autonomously flown) would just need less mutual clearance compared to jets, which also have an altitude band they have to stay in, as well as no ability to slow to a crawl and coordinate finely.

'The labs are underwater on inference' is an absurd thing to say whilst not separating the cost of _compute_ out into training and inference.

Certainly there'd be density _at_ take-off and landing, but even that's manageable by having e.g. arrival/departure locations at multiple heights.

It also seems vanishingly unlikely (at this point) that we'd have EVTOL that's not fully autonomous, further reducing the odds of this - ~perfect and coordinated driving, as well as foreknowledge of what's happening between you and the arrival location drastically reduces traffic.

In any reasonable setup, hovering would be a rare, rare operation (like 30-60 seconds during takeoff and landing), with most of the time spent in wing-borne forward flight – which'd be _wildly_ lower power usage, more like 200-250kW tops. About ~par with staying in continuous acceleration in an EV. More for sure, but not nearly as insane as what you're pointing to.

... and this is exactly where better batteries would help – being able to hold that power level for longer so you could actually go places in earnest without untenable mass.

https://www.kickstarter.com/projects/getpebble/pebble-2-time...

This reminds me of that in a good way – a small Linux device that doesn't have to maintain a screen all the time (power) or focus on real-time but has physical buttons, connectivity, a microphone and a sealed case so it can be thrown in your pocket would be... an absolute dream.

Counter to some others here, I would buy this at whatever cost if it lived up to that intent!

It's... suboptimal, but hopefully that's a reason to hope... if Google get themselves together for 3.5 Pro / the next Flash.

Even if they weren’t individually worried about their proprietary data being shared with Chinese domestic competitors or with government… their audit / security programs likely wouldn’t allow it for a _huge_ range of types of data.

Totally understand why it may not be reasonable or in their best interest (and that the US is _absolutely_ not doing the same reflexively). But it would be lovely to be able to try these out on production workloads in earnest.

People talk a lot about how MacOS has gone downhill but I feel like it would have been a good start if developers could continue to patch over Apple's shortcomings like they used to be able to.

I imagine that we would be a few years into a spectrum of tools like this if they didn't lock it down like they do.

Totally aware that plenty of HN commenters are very glad that Apple keeps this locked down. I'm just the other opinion, that's all.