suhlig

Thank you very much for your stewardship over the years. And kudos for not just letting it rot, but communicating clearly, and closing it down responsibly.

Maybe because yours is listed as having its latest release five years ago, and the one it builds upon only two months ago? Not saying this is the only metric that counts, bit it is easy to check when comparing.

Thank you for mentioning the effect by name. I read first about it 20 years ago, memorized it under a totally different name, and was never able to find it again.

I like Zed too, but never understood why people think that a shared editor is enough for a pairing session. In my experience, I need to look at the same web pages, SSH sessions, calculator, VPN client, and so many other desktop tools as my pairing partner. I would feel seriously disconnected if all we had was a shared editor session.

> Every time someone reinvents the wheel, it becomes a little rounder.

Not sure if this particular library is an improvement, but even if it serves nothing but the author’s enjoyment, or education, it’s a win.

Being involved with software professionally and woodworking as a hobby, I can recommend that talk. The parallels he draws are so good that I was almost angry with myself for not seeing them before watching that talk.

Concourse has it right: You can ssh into a failed container, and debug in the exact environment where the failure occurred.

I don’t understand why people settle for less.

> Next to every incubator was […] a product that I had written a lot of software for.

That must feel like ultimate satisfaction - software that is making the world a better place. Congratulations!

That part where you have to make a commit in order to attempt to fix a CI problem was driving me nuts. It‘s the same with Travis.

Concourse gets this right - you can run a pipeline task as a one-off from your workstation until it’s done, and only then check it in. And even ssh into the build container in order to debug build failures.

I leave the handling of those situations to Lastpass. My wife and kids may request access to my password locker, and if I don't reject within 30 days the locker is opened to them.

> run commands on the worker host directly

I‘d think that Concourse is not the best fit for this requirement.

Not sure how your current builds look like, but I tend not having to deal with containers per se. All they force you to do is be explicit about the build‘s dependencies, which I think is a useful thing.

My approach for migrating existing builds to Concourse is to start with a stock image (alpine or ubuntu), and gradually add things that are missing (`fly execute` is a big help for that).

Once I have a successful build, I extract the prerequisites into a task image (but that really is an optimization).