←back to thread

Tilt: dev environment as code

(github.com)
136 points saikatsg | 4 comments | 26 Apr 25 19:14 UTC | HN request time: 0.294s | source
Show context
hamandcheese ◴[27 Apr 25 01:24 UTC] No.43808716[source]▶
I still think "dev environments" really ought to be running tests directly with your languages native tool. e.g. `cargo test`, `bundle exec rspec`, etc. If you make me run a VM that runs Kubernetes that runs a docker container that runs the tests, I will be very, very upset. Doing this properly and reliably can still be a lot of work, possibly more work if not relying on Docker is a design goal (which must be if you want to run natively on macOS).

There seem to be a lot of tools in this space. I wish they wouldn't call themselves tools for "dev environments" when they are really more like tools for "deploying an app to your local machine", which is rather different.

replies(3): >>43809231 #>>43810096 #>>43812090 #
1. OptionOfT ◴[27 Apr 25 03:28 UTC] No.43809231[source]▶
Not to mention the developer experience is usually sub-par.

I firmly believe that the primary way of interacting with my tests should be the ability to run them one by one from the IDE, and running the code should be run / attach with breakpoints.

replies(2): >>43809384 #>>43811606 #
2. michaelmior ◴[27 Apr 25 04:15 UTC] No.43809384[source]▶
It takes some work, but it's entirely possible to both use Docker and run individual tests with breakpoints (in a Docker container) in your IDE. For example, you can attach VS Code to a running container.
replies(1): >>43810428 #
3. elktown ◴[27 Apr 25 08:44 UTC] No.43810428[source]▶
Yes, but it creates a restrictive and fragile happy-path when the aim imo should be closer to a lab/woodshop where you can take it apart however you like and need for the moment.
4. jbverschoor ◴[27 Apr 25 12:59 UTC] No.43811606[source]▶
Shell containers under code are unbearably laggy and crappy.

I simple have a container for each project using my own container-shell

I run my bundles / whatever. Have all the tooling and can use VSCode to attach via ssh (I use orbstack, so I get project hostnames for free)

It’s the best workflow for me. I really wanted to like containers but again, it’s too heavy, buggy, bulky.

http://github.com/jrz/container-shell