←back to thread

528 points sealeck | 2 comments | | HN request time: 0.473s | source
1. sergiotapia ◴[] No.31391116[source]
My experience with Fly.io has not been a good one.

If I could sum it up, it would be that the dev ux needs a lot of work, and it seems like they are mostly focused on the fundamentals of the platform first.

Following their guide you get postgres not spinning up and linking to your app correctly and you have to nuke your entire app.

The billing UI is weird and feels cobbled together.

I don't feel secure using Fly right now. But again, they are doing cutting edge shit and are probably focused on the underlying bedrock of the platform. They can always circle back to polish the dev ux.

Right now we're on Render.com and it does absolutely everything we want with wonderful dev ux.

In my mind it's a race: can fly catch up to render's UX before render can catch up to flys global mesh load balancing? We'll see who wins.

replies(1): >>31391490 #
2. mrkurt ◴[] No.31391490[source]
It's very generous of you to assume we're focusing on underlying platform. It's true! But it's a difficult thing to notice when our service gave you papercuts.

We've just now grown large enough to have people focus full time on the in browser UX. If you feel like fiddling around again in a few months, let me know and I can hook you up with some credits. :)

The billing UI is definitely cobbled together. This is because I built it over a weekend and it's marginally better than "no billing UI". I have learned that if I'm building features, they probably aren't gonna be very good.