This really sucks. I not only like fly a lot, I have two production apps; thousands in annual creds up for renewal soon; and some mildly embarrassing discussions about migrations to have.
sucks: fly backburnering the app platform to build sprites.
> [...] Sprites, and focusing the company on [Sprites] and the problem they solve.
Then later
> first path [the thing I like/advocate/use] and [Sprites] ... We do one thing or the other. We don’t limp in on both. And if we fail, we fail with our full asses.
Hard to interpret that as anything but the thing I like being backburnered. Which is how it goes, but sucks.
Ah, that's fair! I just got the impression that other people on this thread were axiomatically deriving that we were killing Machines, rather than just shifting the roadmap towards Sprites.
Well, I do interpret this is step one towards a forthcoming post titled "Our Incredible Journey [with Fly Machines]"...
Whether that comes to pass depends on sprite uptake and so forth, but I believe it to be a lot more likely than I did a month ago. So, like I said, bummed, because fly is genuinely nice and I dislike using aws.
That's nice of you to say, and I appreciate it. I'd be sad in the event you're describing too! I spent a lot of time on Fly Machines (not nearly as much as JP and Peter, though).
Yeah that seems like a weird way to end an article that includes this paragraph:
> Fly Machines and our Platform As A Service features aren’t going anywhere. But Sprites was the product of a tiny skeleton crew inside of Fly.io[†], and now it isn’t.
Well, there's doing both in terms of focus and effort, basically treating them as peer products. And then there is doing both in terms of "keeping the lights on for one, and focusing on the other".
Without any special insight into fly.io, I'd bet the situation is the latter. You keep the lights and fix security issues for the existing infra (which incidentally gives you money out of cashflow to invest in new efforts).