mrkurt

32 ms·

211.
by mrkurt 4y ago
You should definitely use a managed Postgres. So should many of the people in our forum. This is part of why we wrote this! That said, the vast majority of PG users on Fly have no issues. Most issues are the result of people trying to spend
212.
by mrkurt 4y ago
Our pricing is a rorschach test. If you come from Heroku, we seem too cheap: https://community.fly.io/t/comparison-of-prices-to-heroku/89... If you are most familiar with AWS, we seem pretty close to what you&#x27
213.
by mrkurt 4y ago
A "training program" starts with good onboarding. It might even start during the hiring process. A company with 10 devs can be training less experienced folks.
214.
by mrkurt 4y ago
I don't want to belabor this because we need to do a much better job making it obvious: but single node, development postgres databases are going to have downtime in our infrastructure. We'll get that host back for you, but you sh
215.
by mrkurt 4y ago
The status page is the communication mechanism we use for incidents. Definitely subscribe to that!
216.
by mrkurt 4y ago
This didn't actually kill VMs, but it _did_ prevent them from being rescheduled for upwards of an hour. The vast majority of apps running on the platform had 100% uptime throughout the incident. The ones that didn't rely on our re
217.
by mrkurt 4y ago
We've had an issue with our Consul/Nomad since last night. This was preventing new deploys, and also preventing rescheduling peoples' VMs when they crashed. Not good! This did not affect running apps (unless they crashed and
218.
by mrkurt 4y ago
I hope their pitch is "rewrite your app in JavaScript, even if it's already JavaScript". :D
219.
by mrkurt 4y ago
I won't tell you you need Fly.io. I am offended you'd put us in the same bucket as kubernetes though, rude.
220.
by mrkurt 4y ago
People use the infotainment in cars almost as much as the actual driving interface. It's not all that weird!
221.
by mrkurt 4y ago
This is all true. But my goal is to make the portfolio succeed.
222.
by mrkurt 4y ago
Yep! If all goes well, we'll have people working on Rust "last mile" UX sometime in 2023. We all use Rust, we just so happen to write Dockerfiles when we do.
223.
by mrkurt 4y ago
Oh when I say "the right thing", it includes actually making money. We're not just building a dev focused cloud because it's fun (it is fun!). We think it's a good business with a very large market. An IPO would be
224.
by mrkurt 4y ago
That's a pretty big market. Heroku got to ~$500mm of revenue while they funneled their most valuable customers to AWS. Keeping those customers around (by, say, giving them lower level primitives) would have 10x'ed that, I bet.
225.
by mrkurt 4y ago
Render is very good. People seem to prefer us (Fly) if they like using a CLI, and they prefer render if they'd rather have a full in browser experience. If you're trying all the things, https://railway.app/ is als
226.
by mrkurt 4y ago
So far, people seem to get the most out of the `performance.timing` API and a metrics package. There are very expensive real user monitoring tools to do some of this, but that browser API makes it really easy to just wire up an app and coll
227.
by mrkurt 4y ago
That's interesting. I don't think we've run across that before, definitely send us more info!
228.
by mrkurt 4y ago
Hey! I love this feature. What don't you like?
229.
by mrkurt 4y ago
I also agree about the importance of fully managed databases! We shipped "automated" Postgres because we couldn't get any fully managed DB providers to pay attention to us when we were small. I expect we'll have an optio
230.
by mrkurt 4y ago
I think if you look at the companies you like, you'll notice that it's not the investors who call the shots. There are a handful of very large, very profitable, developer focused companies that investors love because they remain d
231.
by mrkurt 4y ago
I'm going to make a point here that might be contentious: you are asking for Heroku. Heroku is going away because it no longer works as a business. We are not Heroku. It is ok for you to not like what we're doing. We're build
232.
by mrkurt 4y ago
You definitely can't make complex things simple just by removing features. What we did, instead, was built low level primitives, then built opinionated PaaS-like magic on top of those. If you're running a Phoenix app, `fly launch`
233.
by mrkurt 4y ago
You can route arbitrary TCP or UDP services through our load balancing layer just fine. I'm not sure what SIP actually needs, but it might work. We don't currently have a way to route TCP connections directly to individual VMs, so
234.
by mrkurt 4y ago
We aren't going to support Heroku buildpacks. We are working to make more frameworks easy to launch with minimal configurations. Which means – hiring people to work specifically on those frameworks + docs + builds. We did bake nixpacks
235.
by mrkurt 4y ago
This is a 10-50 year company. You're not wrong, though, we are either building something big or we're building something that will fail. Our bet is that a developer first public cloud is important and needs to exist. Which means,
236.
Figmex: Making Figma with Elixir(nathanwillson.com)
10 points by mrkurt 4y ago|0 comments
237.
by mrkurt 4y ago
They might, but that's the wrong way to think about security. It is true that people can be tricked into bypassing any security layer. It is also true that strong security boundaries are useful tools.
238.
by mrkurt 4y ago
https://news.ycombinator.com/item?id=32251586 This is answered in the forums, too: https://community.fly.io/t/new-feature-every-public-port-now...
239.
We clone a running VM in 2 seconds(codesandbox.io)
414 points by mrkurt 4y ago|109 comments
240.
by mrkurt 4y ago
You can really only swap drugs for guns if gun related imprisonment is high. Are there are lot of people in prison for illegal gun possession / dealing?

More ›