About a decade ago I heard John complaining on No Agenda about a sound card mixer problem he was having in Linux. I had the same model card so I emailed offering some debugging advice. He responded almost immediately and we went back and forth trying things. If memory serves it was a config issue with pulseaudio. It was the highlight of my week.
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.
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.
> 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.
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.
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.
HW4 is really a game changer. I was absolutely floored by HW4 FSD during a recent test drive. Tesla is accomplishing some truly groundbreaking technical achievements here. But you wouldn't know it through all the Elon Musk noise (pro and con). I'd encourage anyone to take a test drive and put FSD through its paces. I went in with a super critical mindset and walked away stunned.