Hacker Newsnew | past | comments | ask | show | jobs | submit | levlaz's commentslogin

So if tropes.md works it doesn’t actually solve the problem. You’ll be reading stuff that you think an LLM didn’t write.

This person is so addicted to ai that they even had an LLM write this post.

I think this is a good reminder about the importance of offline backups. It’s silly how railway treats volumes but it’s the customers fault for not using that information to come up with a better disaster recovery plan.


Em is dead, AI ruined it for everyone. Sorry.


Hello, Dagger employee here.

Thanks so much for taking a look and sharing your feedback! We've heard this feedback in the past and are working on a big docs change that should make this whole experience a lot better for folks that are new to dagger.

https://devel.docs.dagger.io/getting-started/concepts

This should land in the coming weeks.


Ocaml


Most wholesome HN post this year


It’s similar to a builder pattern but not just a builder pattern because depending on the type you can indefinitely pipe context independent types.

So it’s a bit of a hybrid between bash and powershell.


Yeah this is method chaining, and method chaining is not the same as piping.


If you’re working on your own you may not need dagger.

If you’re working on a team often your shell scripts, python programs, and makes files are not always portable between local and CI, but even worse between your local machine and your colleagues local machine. This is where dagger shines because it lets you do all that stuff in a fully portable way.


I need an example to illustrate that, because I had to read this thread to even understand what I was reading/looking at.


Maybe the docs will help? https://docs.dagger.io


A lot of projects and teams have been successfully using all tools mentioned in both CI and local dev envs. Portability and reusability of this “glue” stuff is a nice indicator of engineering maturity and culture within those projects and teams.

Low pro teams and individuals will happily abuse any new tool.

Mature teams stick to local-first CI - i.e. be able to run pipeline locally - and then translate to whatever is being used in their build and test infrastructure.


Thanks for sharing your experience, I'd love to hear more details.

Feel free to send me an email if you'd like lev@dagger.io, it would be great to learn from your experience so we can continue to improve the platform for everyone.


Its the same idea. You are taking the instructions in with-exec and pushing it to the previous type.

In this case, `from alpine` is a function attached to the container type that has many additional functions. You chain them together to do stuff. You can do it through code as if it was any other object, but this shell allows you to do things without code as well.

Perhaps the example is too simple to feel useful, but being able to pipe primitives like files, directories, containers, secrets, and even any custom object makes it possible to rapidly experiment with and compose pipelines.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: