Long time without writing on my blog, let's talk about Dev Containers this time.

DevContainers: Migrating my entire Rust setup - https://www.edu4rdshl.dev/posts/devcontainers-migrating-my-entire-rust-setup/

I've been struggling with getting a larger .NET Project to open in a DevContainer. Specifically, the language server kept dying and I was always too busy to figure out why.

It was running out of memory!

Docker on my dev machine had a max memory allocation of 8GB and limited swap. Cranking that up and everything is lovely!

Why didn't I catch this earlier?!

Just past month I consulted a company, and I said they shouldn't renew #JetBrains, and fully transition to #VSCode and Coder.

Past week they did. They took three days to replicate their development environment, and a week to move from their muscular memory.

Nothing against JetBrains, but their products feel like 2005 crap on 2015 interfaces and 2025 promises.

My beef with #PHPStorm is not unfounded.

I still believe it wasn't made with Containers in mind and the codebase is "patched" to work with containers.

I've seen two workplaces pivoting to containers and VSCode. Their developers just abandoned #JetBrains for this same reason. Container workflows suck and it's full of inconveniences.

Damn, #Fleet doesn't support remote #PHP interpreter.

Guess I'll have to juggle around #PHPStorm while they get their shit together around DevContainers.

Meanwhile, I'm hoping #Zed catches up. As soon it brings the important bits from PHPStorm, I'm moving on.

Not renewing my #PHPStorm subscription. I'll do once #DevContainer support is as good as #VSCode.

"Hey, try DevPod instead, I've never had a problem using it with PHPStorm"

It did fucking work. How the hell.

Is this a fucking joke, #JetBrains?

That's it, moving on from #PHPStorm and their half-ass implementation of #DevContainer, it's fucking shit. JAVA was a mistake.

Let's test Zed. Worst case scenario, VSCode.

Am I using #Github #Codespaces wrong?

I thought the point of creating a devcontainer.json file to specify extra bits have built when you set up a machine, and they were honoured on the creation of codespaces.

Given that #Gitpod seems to be adopting #devcontainer now, I figured I'd try Codespaces. A basic thing seems to be harder than I thought.

If you have direct experience building Codespaces, would you share a pointer on how to fix this seemingly basic thing?

https://gist.github.com/mrchrisadams/9ee981ffdcc1cef38431f51a76886098

I stumbled upon #Coder, which is a #DevContainer platform you can use in your own computer (much like #DevPod).

I'm going to give it a spin to see if I can connect remotely to a DevContainer on another computer. It "should" work, since it's made for this type of scenarios, unlike DevPod which focuses on local.

https://coder.com/