/new convention: think of it as “dotfiles” but “for computers”
ghuntley.com
ghuntley.com
I guess what he means is not so much the dotfiles themselves, but the customization and sharing of them, and not for computers, but for containers, and not dotfiles, but Docker configuration. But other than that I'm sure it's basically the same thing.
The two feel complementary; you'd likely still want your dotfiles included in the images you're spinning up.
The idea here is to have, rather than a set of configurations you can deploy wherever you go, a factory that produces ready to go computers on demand.
This post makes a lot of sense to me, & is a good exploration of what our environments are, & how they might be expanded & better able to serve, especially as we get better containerized systems. This approach is web based, and with nice integration work like Toolbx[1] I expect this sort of primed, ready-to-go, containerized development strategy being more popular. Having everything ready, but having it all still be "cattle" not "pets" allows for a lot more unchecked & wild experimentation during development.
Services like GitPod are about serving a development environment remotely.
The blogposts discusses dotfiles as a social thing. e.g. you should be able to fork someone's dotfiles repository as a good starting point for your dotfiles.
The idea in the blogpost is a suggestion which combines this idea of sharing dotfiles, with the idea of being able to quickly spin up a developer environment.
Project-specific configuration is just that, project-specific configuration, and you would not call it dotfiles anymore.
Also by defining dev environments in code that can be deployed on-the-fly (aka infrastructure-as-code), that allows you to do things like share the code with others, who can "fork" your dev environment with their own customizations. This seems to be what OP's article is about.
Bingo!
> Why is the first sentence, just the title repeated?
An artefact of using Ghost defaults; I've moved the excerpt from the main article into the social media cards section to improve readability.
> other articles mixed in with the content
By referencing the other articles which are relevant to points made within the post becomes shorter.
> The article is not that long
The post is meant to be short because it's about a simple convention that I've adopted that has helped me. Maybe others will find value in the idea as well.
There are already links in the paragraph text, and those links are highlighted a different color. I can click on them to see the other article if I’m interested.
I don't believe these are ads, but just previews of the linked content.
/new is a route on his webserver, which when clicked sends them to a web-based IDE, primed and ready to go with their set of dotfiles & configuration, namely, https://github.com/ghuntley/new
Also are you adding in tailscale so that you can then reach the container from your iPad as well?
Stop developing on broken by design platforms?