Hacker News Reader

Comment by ducktective | Hacker News Reader

Does this deprecate my vim/gcc/gdb/make (in general "CLI driven workflow") which I have assigned so much time to, to have a nice vender/IDE-independent solution for development?

I'm curious to know the answer in an honest/practically-speaking sense not ideologically.

IMO, the downside of this container/web-app solution is the memory size that all the SDKs would need and this would add up eventually. But I'm not sure this fact alone could win any hearts over that sweet ease-of-entry-to-development.

People were nagging about latency and bloat in webapps and Electron GUIs...yet here we are...even SpaceX's console is a chromium instance.

View on HN

I don't think so. If fact you could just package your "CLI driven workflow" up into a docker image and now you can instantly move it between machines, peers, etc...

Furthermore you could version and manage the evolution/drift of your workflow as underlying components change/get updated.

Exactly: I have CI produce a Docker image from my dotfiles repo https://bergie.iki.fi/blog/docker-developer-shell/

Hey that’s cool! I do the same thing! I use the Docker image as a way to use my development environment in a pinch and additionally as verification that my giant one-click setup script works on a fresh machine.

https://github.com/jswny/dotfiles

If needed, you could probably containerize that workflow as well. Conversely, if someone shared their containerized environment with you, you don't necessarily need to use VSCode. You can still just attach to the container directly using Docker.

It actually makes your workflow more powerful as you can package it in a container and other devs can start using it in no time.

I have never managed to get a step through debugger working with Pycharm. I know it's possible, but things like this are why devs won't be able to "start using it in no time". Docker solves one set of problems and introduces others.

Yeah, unfortunately the JetBrains IDEs don't really work with this workflow yet. I'm hoping one day they will ...

I saw online tutorials showing you how to set it up and wasted a few hours not managing to make it work.

Probably not, but your vim/gcc/gdb/make flow doesn't scale to other developers. If it works for you, by all means keep using it.

you can still have a shared base Image for your teammates, then use that base image to create a new image just for your .vimrc etc.

I meant more that by modern standards, vim/gcc/gdb/make is a very labor-intensive toolchain to write applications with.

"Doesn't scale" in the sense of "other developers are pretty unwilling to learn that chain of they didn't grow up with it."

> "other developers are pretty unwilling to learn that chain of they didn't grow up with it."

Funny, I've been running into this problem while trying to switch people to docker. Maybe we're all a bit guilty of this in our own way.

Reply on news.ycombinator.com