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.
HN user
levlaz
Solutions at Dagger.io
https://levlaz.org
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.
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.
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.
I would lump dagger in with JS (programming language, ecosystem, runtime) and MacOS (operating system) before comparing it to any single tool.
Answering "what does dagger do" can be tough, because there are very broad applications.
Its always hard to describe general purpose platforms like these. Dagger is an open platform for building composable software. It has SDKs, sandboxed execution environment, observability, and now this shell interface.
Dagger aims to be more than a build kit interface and more than just a build system. Many people have been using it outside of CI for years.
But I can appreciate your perspective. Thank you for sharing your point of view.
Why is that? It’s just an extra type that has no impact on any other types. It’s a tool in your toolbox that you can use when you need it and ignore otherwise.
It’s def closer to powershell in all the best ways IMO. But the key point is that the container thing is actually a typed object. So is every other primitive in there including once you make yourself.
You sure can :)
Dagger can read dockefiles as is, https://docs.dagger.io/cookbook#build-image-from-dockerfile
There’s a tiny but of overlap in principle, but you can use dagger shell without having to learn a new language and the interface is much simpler. Give it a try and let me know which you prefer!
Yeah for sure, this was specifically designed to solve the problems you describe!
What kind of tooling do you have in mind to replace?
Also what would you prefer to see instead of bash compatible?
This is good practical advice
Thank you for making this! I've been waiting to use it for quite some time. Really happy to take it for a spin.
I wrote some instant reaction comment when I read this earlier today but then I went back and re read the whole thing and now I think the post is one of the best blogs I’ve read this year.
This was a proper rant and I’m glad it stirred up so many great discussions. Thanks to Matt.
Thanks for the thoughtful feedback, lots to think about. I reread the whole post and feel less strongly about my previous comments. Overall the original post gives me a lot to think about and I’m grateful for that.
Apologies if I am misreading you, but the fact that you keep putting culture and EQ into quotes signals to me that you think these are not important things. If that is the case, then yes, your EQ is bad.
Yes, I agree with you. I've seen this done well and I've seen it done horribly.
Do you think its better not to do them?
manage yourself and manage your peers, but you also have an engineering manager and a project manager and the CEO is your skip-level manager and the CEO’s brother is also your skip-level manager too
This is hilarious and I’m sad I’ve seen versions of this more than once.
Overall I enjoyed most of this article but disagree about the objection to behavioral interviews. I think they’re an important part of the modern hiring process but I will agree that the approach is sometimes done wrong by companies and individual interviewers.
its a test of EQ, if a simple question about past conflicts makes you this defensive then its exactly the type of thing it was meant to screen for. I’d encourage OP to put some thought into this part for their own sake. You don’t need to make everyone feel better but if you show up with the attitude that you’re never wrong, then nobody will want to work with you. I know I don’t.
I’m very confused on how this poorly written and widely speculative article made it to the front page.
I really want this to succeed, rooting for Andreas and the team!
Yeah, that is fair, its better than nothing. But he could have also done the thing that every other good journalist does and ask both sides for comment instead of speculating for 1000 words.
Interestingly has a similar mobile experience as OP.
Its great to have an open source solution for usage based billing. Really exciting to see this team get some funding to help them continue.