new #blog post on #devcontainers

https://ascia.tech/blog/devcontainers/

Воспроизводимое изолированное окружение с Nix и DevContainers

Как фулстек разработчику, мне доводилось работать с проектами на совершенно разных технологиях. Как правило, нужно было поправить небольшой баг или сделать небольшую фичу. Для задач такого разряда стек технологий обычно не имеет значения: отладка примерно одинаковая что на JavaScript, что на Haskell, Go или Python. Написать немного кода мне, в общем-то, никогда не было сложно на любом языке, с которым я работал. Но вот что всегда было настоящей проблемой — это запустить и протестировать проект. На это запросто уходили дни: найти нужные версии компиляторов/интерпретаторов, дебаггера, пакетного менеджера и всякого сопутствующего тулинга. Я устал от этого, и придумал, как больше никогда в жизни не устанавливать тулинг вручную.

https://habr.com/ru/articles/1010282/

#nix #devcontainers #docker #reproducibility #nixos #nixdarwin

Unser nächster #Java Usergroup Termin steht bald an.

@sparsick erzählt uns alles über schmerzfreies Aufsetzen einer Dev Umgebung

https://events.ijug.eu/events/ccbd5f78-1e7e-4a05-977e-c6041b8bf61a

#mainz #nix #devcontainers #javascript #devshell

Am I the only one who doesn't get the hype around devcontainers?
I just don't see much of a point in running everything (including LSPs) in a Docker container vs running it locally with tools like asdf or mise.

#Docker #Devcontainers

I’m rather smitten with the *idea* of dev containers and, to a degree, the reality delivers. Reproducible environments. Familiar primitives. Editors with decent adoption offer a good experience. Most engineers understand containers well enough to tolerate the rough edges.
But I can’t shake the feeling there are better ways to reach the same goal.

The usual answer is “Nix”, and that’s probably right. Yet the rise of Dev Containers feels less like a breakthrough and more like a side-effect of the container monoculture. They work because containers are everywhere, not because they’re especially well-suited to dev environments. If there’s a real successor, it likely abstracts Nix *away*, integrates cleanly with editors, and doesn’t require heavyweight plugins or full VM-scale artefacts to edit a file.

What’s wrong with dev containers? They’re slow, expensive, and bloated relative to the problem they’re solving. I’m still invested, and I’ll keep using them. But it does feel like, as an industry, we’ve settled for the first thing that worked rather than the best thing we could build.

#DevContainers #docker #vscode #zed #vim #jetbrains #python

Playing Nicely With Git Worktrees And DevContainers https://medium.com/p/playing-nicely-with-git-worktrees-and-devcontainers-3abde3ce1e8a?source=social.tw

#git #devcontainers #vscode #docker

Does anyone know how to setup a #devcontainer for #Android development with #dotnet and #JetbrainsRider ?

I can get the container running, and build the project, but can't get the emulator to work to add a virtual device, nor make my physical phone show in the devices panel.

#askFedi #androiddev #devcontainers

Is anyone using Development Containers
(https://containers.dev/) for anything serious?

I gave it a quick spin on a fairly simple Django + PostgreSQL projects, and all I see is flaky, half-assed implementations, stuff failing with cryptic stack traces, etc.

Is it maybe because I am not using VSCode but PyCharm?

Another thing a Megacorp can't afford to do properly?

#Microsoft #DevContainers #DevelopmentContainers #SoftwareDevelopment