Earlier quoted context omitted.
Dagger is already a popular dependency injection framework, so why choose a name that will be confusing to people who will likely use both of these frameworks in their projects?
These comments are extremely uninteresting. If you care so much, please just create an issue on their bugtracker or something.
Dagger: a new way to build CI/CD pipelines
231–240 of 267 posts
Re: Dagger: a new way to build CI/CD pipelines
#232One of the big benefits of using a cloud build server like CircleCI is that it allows me to parallelize tasks. For example: - Build code and lint code at the same time - Run slow end-to-end tests in parallel Is parallelization possible with Dagger, even in principle?
I think this comment from the OP answers your Q ? :) https://news.ycombinator.com/item?id=30859125
I guess my question is how this integration works in practice and what kind of complexity it generates.
Re: Dagger: a new way to build CI/CD pipelines
#233Earlier quoted context omitted.
> What can your team do to reverse this tragedy of the commons? It's tragedies all the way down :-) Making a successful tool in a competitive space is hard enough. Asking a creator to somehow factor in environmental impact isn't going to work. A creator that places additional constraints on themselves will more likely lose out to a competitor that doesn't. This is the kind of thing a carbon tax is perfect for. Cost o…
> Asking a creator to somehow factor in environmental impact isn't going to work. That attitude doesn't leave a great impression for me. I take your points about how difficult it is, but I think we can all do better than throw our hands up in the air. For instance, you could talk about how easy containerization of CI/CD makes it easier to move your pipeline where impact is lowest. Or that you can control your own imp…
I think the ideal way is to let a startup thrive any way possible and when they're not trying to not starve anymore, begin environmental changes.
Re: Dagger: a new way to build CI/CD pipelines
#234Re: Dagger: a new way to build CI/CD pipelines
#235https://github.com/JuliaParallel/Dagger.jl
Re: Dagger: a new way to build CI/CD pipelines
#236Earlier quoted context omitted.
Usually it helps by adopting Windows development practices instead of trying to cram UNIX workflows into it. Who on their right mind uses ssh/scp on Windows development other than connecting to UNIX boxes?
I use gitlab for ci/cd, a gitlab-runner runs on a windows based system (legacy aka not .net core so can only build with msbuild.exe). Now I have to copy this release to another windows based system. Are you calling me stupid for using scp via openssh? Would like to hear an alternative? Took me like 5 minutes to set openssh up.
Re: Dagger: a new way to build CI/CD pipelines
#237Earlier quoted context omitted.
In my personal experience, Windows development is absolutely awful. Nothing about it is ergonomic, and the management of the development environment is just painful. Obviously you don't always have a choice, but creating a nice development experience is clearly not a priority for Microsoft. One really basic example: I was deploying files to a Windows Server box using scp, but my internet connection died midway throug…
> But you can't easily interact with files on the system outside of Linux subsystem, which made it more or less useless for my purposes. It’s possible in file explorer via \\wsl$, but that is not always supported by applications so it’s not 100%.
Oh, hey, there's the C drive in WSL! ;)
ln -s /mnt/c/Users/Somejerk/Documents ~/documents
Oh, man, a shared documents folder!
Granted, access to those files is slow as dirt because of the Plan9 filesystem, and there are some weird bugs where a process sometimes loses access to $cwd if it's not a native wsl filesystem (also a Plan9 bug reported to MS over a year ago). But it's tolerable when interoperability is necessary.
It also facilitates using the same filesystem under multiple WSL instances.
Re: Dagger: a new way to build CI/CD pipelines
#238Earlier quoted context omitted.
How is possible to restrict someone from making a factual statement like X is compatible with Y?
If Y is a trademarked term, you are free to not allow statements about your brand.
https://www.gfrlaw.com/what-we-do/insights/beyond-brand-x-us...
So as long as they don't imply endorsement, "I'm compatible with X seems fine".
Re: Dagger: a new way to build CI/CD pipelines
#239Worst company name I've experienced in years. Absolute embarassment. How do I introduce an app named "Dagger" into my stack without sounding caustic or ignorant to my staff? How do you make a service called this without feeling caustic or ignorant. And you have investors? Are you serious? Did you think Mailgun was a good name? edit: Figures Paul Graham is pimping this trash. Good work Sykes, you found a way to float…
Re: Dagger: a new way to build CI/CD pipelines
#240There's so much more to CI/CD than the build definitions (e.g. dashboarding, log viewing/retention, access control, manual interventions, secret management, test reporting, etc.) and while some of your points resonate very strongly with me (e.g. local builds), I can't help but wonder what the endgame is here? You've raised $27m to what? Give away a free tool for engineers to define their builds in? While they continu…
IMO the best open source infra lock-in strategy is kube took a while for E/AKS to catch up with G, things like ingress still vary in DX across clouds 'the same everywhere but it only works here' (no comment on morality of this, quality of kube generally, or whether this team will do the same. docker IMO missed the chance to be a cloud host or a standard interface)
That was also the initial goals of k8s - make it universal so it's adopted as a standard by everyone else to make yourself competitive against the AWS juggernaut. And it worked.