Hacker Newsnew | past | comments | ask | show | jobs | submit | kolanos's commentslogin

For a little context. Salesforce changed their enterprise structure, effectively doubling their prices and my guess is many of their larger customers fled the platform. The enterprise pricing organized dynos into blocks and without notice they doubled the minimum block unit you could have. As a result, you ended up paying for dynos you weren't even using because they were now rounding up, sometimes by thousands of dollars worth of dyno blocks. So if you thought Heroku was expensive before, now it just didn't make any financial sense at all. For the other PaaS out there: don't do this.


RISC is good.


Does this mean Keynote and Pages are now paid products? Aren't they included with Mac OS?


From the subheading: “plus new AI features and premium content in Keynote, Pages, and Numbers”


996 is a work schedule that derives its name from its requirement that workers clock in from 9:00 am to 9:00 pm, 6 days per week, resulting in employees working 12 hours per day and 72 hours per week.


> (Benchmarks run on PyPy 3.11, Intel i5-8365U, 8 Cores, 100 connections)

Why not benchmark Flask/FastAPI with 8 workers instead of 4 for a more apples-to-apples comparison?


all framework except Catzilla run with 8 workers for benchmark

you should run yourself for testing.


China currently only holds about 2% of U.S. debt. What is the risk exactly?


Found this in their roadmap [0]:

> Managed ECS-EC2 clusters in preview

> AWS has a long standing issue with the ECS agent randomly disconnecting, resulting in orphaned EC2 instances which can cause traffic or deployment degradation.

> We have attempted to solve this a few ways in the past, but there were still critical edge cases falling through.

> So we bit the bullet, and developed a robust, full featured ECS cluster management solution to solve this problem once and for all.

> It's currently in private preview. To get early access before we roll it out to everyone, contact support.

I found elsewhere in the Flight control docs where they recommend ECs+EC2. While I'm not surprised to hear about issues with ECS+EC2, given the reported issues above I don't know if I'd recommend it in my docs. Fargate is a far better option for most use cases, at least in my experience. Unless you need specialized instance types, like GPU workloads.

[0]: https://roadmap.flightcontrol.dev/changelog


Just reading over the docs, you'll need a lot more GCP services than Cloud Run to encompass what Flightcontrol is managing for you. The Cloud Run analog is Fargate. Which is only the container orchestration piece.


Please provide links for the docs to this, as this was a misconception I had about Dooku as well.


Looks like you can use your own Dockerfile or a container registry. Suspect nixpacks are just a recommended starting point for people looking to get up and running quickly.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: