alt Hacker NewsSprites are a beautiful place to make an abstraction.
But I have never used a buggier infrastructure product in 30 years of development than when I tried sprites. Data loss left and right, sprites going into unconnectable zombie mode. Couldn't use even load snapshots because half the system seemed to think the sprite was fine, and half seemed to think it was dead. I gave up after two weeks of losing stuff over lunch or overnight or in the middle of working. I vividly remember scrolling through my terminal history, copy/pasting out work I could find to save from a dead sprite. I would guess that half or more of the sprites I launched had some kind of problem.
Hope they get things stable. The concept is great.
Replies
Can second this. I had an enterprise client that was interested in using these for fast development etc. Wasn’t my project or the reason I was there but I was curious so I kept up with it.
Eventually they abandoned the company but stuck with the concept by going with another company. Complaints were the same, extremely buggy interface, dataloss, but also terrible support. That may have been there fault though for not using their actual domain for the test period (and not mentioning that they were an F200 or something).
I operate an app that orchestrates code running on a bunch of Sprites. A few months ago it was an exceptionally buggy service, frequently just fully broken or losing data (had to get support involved to recover one that got into a fully broken state), but from what I've seen at least they've become much more reliable in the past two months or so.
I evaluated Fly.io itself several years ago and found it unacceptably buggy as well for any real use case at the time, but I kept an eye on it and today I operate a few production workloads on it that are very stable and reliable—I figured the same would be true for Sprites and it seems to be taking shape that way.