I've been using it today and honestly I'm impressed. I seem to be the exception when I say I don't care it's a vscode fork. Having access to the extension ecosystem seems like a boon to me and I could quickly get a setup to my liking to rival my current Jetbrains Claude Code setup.
It seems to streamline my existing Claude Code workflow with a much better UI. The tab complete seems the best I've experienced and the text/image selection, adding comments and iterating on a plan is genius.
Depressing to see everyone here unable to see the forest for the trees.
This is a common sentiment because so many people use ORMs, and because people are using them so often they take the upsides for granted and emphasise the negatives.
I've worked with devs who hated on ORMs for performance issues and opted for custom queries that in time became just as much a maintenance and performance burden as the ORM code they replaced. My suspicion is the issues, like with most tools, are a case of devs not taking the time to understand the limits and inner workings of what they're using.
haha, thank you for summarising my thoughts on python package management... and very few people have mentioned poetry which is what we and most teams I know use.
It's funny because OPs solution was his docker-compose-anywhere, which is exactly what, from my experience, I've seen so many start-ups running with. Sure it works while you're running an MVP but it's incredibly brittle for running something in production as soon as the application grows in complexity. IMO the primary draw of k8s isn't necessarily "infinite scalability" but its resilience.
I sometimes wonder how many of these post boil down to "I don't want to learn k8s can I just use this thing I already know?".