https://futureofcoding.org/ logo
Join SlackCommunities
Powered by
top context: <https://twitter.com/garybernhardt/st...
# thinking-together
c
r
I'd love to hear from other people who work with this stack if they share this experience. So is the typical Node workflow to edit a file, then kill your server, then restart your server, then refresh your browser, each time you make a change to test it?
Just to elaborate, I had thought the restarting the server start had already been solved by things like https://github.com/remy/nodemon What am I missing here?
f
Gary is saying there's a variety of tools trying to address this and all of them are "flaky"(leave processes running, fail to pick up changes, etc)
r
I guess I'm wondering what the specifics are, e.g., which part leaks processes, and which tools fail to pick up file system changes. And if other people here have the same experience as Gary or not?
m
I write a lot of js and I've developed a minimal environment myself, I tried to start with the usual boilerplates, scaffolds or *-cli tools, they all break after you change a single thing
my dev environment doesn't have anything running while I develop
i
I only do (JS/CLJS/etc) dev with some sort of watcher running, picking up on changes and refreshing (or hot patching) as needed. It's definitely flaky, and I'm sure it leaks processes (though I don't notice because.. honestly..)
I've used some watchers that die whenever files are created/moved/deleted. I've used some watchers that die when there's a stiff breeze outside. My current watcher works well enough that I'm happy to overlook the quirks. Also, your music skips. Constantly. Gary is right about that too. If you don't hear it, you're not listening very closely.
Oh, and you should listen to Hella. Gary is also right about that. And everyone needs to put more effort into the quality of their audio recordings. He's right about a lot of things.
🤘 1
2 Views
Open in Slack
PreviousNext
Powered by