DAlperin

Moving this out of a subthread, but I can't find any sources corroborating the the phenomenon described in this article. In fact a lot of the literature from NASA seems to explicitly contradict the claims in the article[0][1]. Obviously not dispositive, but this article reads to me at least partially like AI confabulation. Perhaps my Google-fu is lacking here but I had Claude do a search as well for good measure and couldn't find any supporting evidence that way either. Without the author offering more primary sources I would advise against placing too much if any stock in this piece.

[0] https://humanresearchroadmap.nasa.gov/Evidence/reports/BMed.... [1] https://link.springer.com/chapter/10.1007/978-3-642-30583-2_...

I can't either. In fact a lot of the literature from NASA seems to explicitly contradict the claims in the article[0][1]. Obviously not dispositive, but this article reads to me at least partially like AI confabulation. Perhaps my Google-fu is lacking here but I had Claude do a search as well for good measure and couldn't find any supporting evidence that way either.

[0] https://humanresearchroadmap.nasa.gov/Evidence/reports/BMed.... [1] https://link.springer.com/chapter/10.1007/978-3-642-30583-2_...

One of the cofounders it seems https://atomicsemi.com/about/

I think the next sentence clarifies pretty well.

> In this case, what’s dropped is &mut future1. But future1 is not dropped, so the actual future is not cancelled.

(I used to work at Fly, specifically on the proxy so my info may be slightly out of date, but I've spent a lot of time thinking about this stuff.)

> why can't every proxy probe every [worker, not application]?

There are several divergent issues with this approach (though it can have it's place). First, you still need _some_ service discovery to tell you where the nodes are, though it's easy to assume this can be solved via some consul-esque system. Secondly, there is a lot more data than you might be thinking at play here. A single proxy/host might have many thousands of VMs under its purview. That works out to a lot of data. As you point out there are ways to solve this:

> One could reduce _average_ bandwidth a lot by having the proxies mostly send some kind of "send changes since <...>" or "send all data unless its hash is <...>" query.

This is definitely an improvement. But we have a new issue. Lets say I have proxies A, B, and C. A and C lose connectivity. Optimally (and in fact fly has several mechanisms for this) A could send it's traffic to C via B. But in this case it might not even know that there is a VM candidate on C at all! It wasn't able to sync data for a while.

There are ways to solve this! We could make it possible for proxies to relay each others state. To recap: - We have workers that poll each other - They exchange diffs rather than the full state - The state diffs can be relayed by other proxies

We have in practice invented something quite close to a gossip protocol! If we continued drawing the rest of the owl you might end up with something like SWIM.

As far as your second question I think you kinda got it exactly. A crash of a single corrosion does not generally affect anything else. But if something bad is replicated, or there is a gossip storm, isolating that failure is important.

(I used to work at fly on networking)

Fly has a lot of interesting networking issues but I don't know that like, the actual routing of packets is the big one? And even in the places where there is bottlenecks in the overlay mesh I'm not sure that custom FPGAs are going to be the solution for now.

But also this blog post isn't about routing packets, it's about state tracking so we know _where_ to even send our packets in the first place.

That’s the name in the Arabic text hallucinated by the model :)

The story here isn't that they've invented a new format for user defined indexes (the one proposed here is sort of contrived and I probably wouldn't recommend in production) but rather demonstrating how the user defined metadata space of the parquet format can be used for application specific purposes.

I work on a database engine that uses parquet as our on-storage file format and we make liberal use of the custom metadata area for things specific to our product that any other parquet readers would just ignore.

For what it’s worth I don’t think we entirely disagree: it has at times felt absurd that it didn’t make as much money as it maybe otherwise could. We made a bet that the type of cloud platform we wanted to build could be well served by GPUs. It wasn’t as good a bet as we thought. There is probably a different type of cloud product we could build that would be better set up to sell gpus but we are still committed to the primitives our machine product has to offer.

Super neat! Does the v2 branding mean that the more "fully featured" observability product is going away? Or is it all going to be rebuilt on top of clickhouse?

We have to invest in fighting fraud and abuse anyway, such is the public cloud business. We don't intend to diminish user experience in service of fighting it.

> we can steer them to an area that's easy for us to drive out and pick them up.

What does this look like in practice? As you mentioned I know you don't really have any lateral control, but I imagine you can wait for it to overfly somewhere convenient to descend?

Fwiw Teenage Engineering is a design firm who was originally contracted by Rabbit to design the physical device. I don't think they had anything to do with the functionality.

Also to add, we already have lots of customers who use this model.

This is super cool! Do you have any plans to support on-demand image building like the now defunct https://ctr.run? It seems like with your speed it's kind of a perfect match.

Hah I've got my own backlog of side projects, don't tempt me I'm like a year behind on it :). If you ever get around to building it or something like it I'd love to hear about it. You should check out tools like https://github.com/nocodb/nocodb which expose a spreadsheet like interface on top of a database.

The problem appears less when creating new tables, creating tables is relatively safe. But let's say in your one table per db you keep track of a few things (columns). For example you have a column for the name of the sheet and another column for the time it was created and some other miscellaneous columns. Later on once you have a hundred users or so you get a persistent feature request: keep track of the time it was last updated. You write up a simple migration, it looks something like

  ALTER TABLE your_table ADD updated_at TEXT;

This is also relatively harmless, but now you have to figure out how to run this migration across your 100 databases, and deal with the case where maybe some fail, what do you do then? Rollback everywhere? But what if some users have already have rows that use the new column? Do you delete their data? Etc. Now consider a more complicated migration, maybe it renames a column, drops a column, adds a default value, drops an index, etc. You can see where problems might come from.

That said I do really like your idea, I've gotten into sqlite a lot lately (I work on the database team at Fly.io), I'm just responding to you questions specifically about migrations.

As fly apps v2 becomes more stable the docs will continue to improve. Watch this space :). As for the graphql, it's a bit of a thorny situation. The graphql exists primarily to service our needs internally and as such has no guaranteed contract. Unfortunately, however, for some things that's the only API that exists. The autogenerated docs in the playground are pretty good actually though. That said, we are working on improving our rest api so more things will be available there.

Yeah. api.machines.dev is a public endpoint for our machines api.

EDIT: See this comment for an example on how to make the provider use the public endpoint https://github.com/fly-apps/terraform-provider-fly/issues/42...

EDIT EDIT: I pasted the wrong link, sorry about that.

We allow this now: https://community.fly.io/t/new-proxy-handler-pg-tls-postgres... :)

I do machines Devrel at Fly.io and I've got a whole lot of demos coming soon, so stay tuned :)

A lot of this is a Google search away. Here's an article from vox that is well researched: https://www.vox.com/22841191/gifted-and-talented-education-p...

I would argue the point that Stuyvesant is the "best" but I don't disagree with your point. The problem is that a lot of the money ends up in the schools with the rich kids and for a lot a lot of students and schools they never see anywhere near that type of money.