3 ms·

I dunno, I have active hobby projects that go weeks to months without commits. Sometimes you need to experiment with things for a while to get a feel for wheth

I dunno, I have active hobby projects that go weeks to months without commits. Sometimes you need to experiment with things for a while to get a feel for whether or not it should be committed. Sometimes you need to take a break. The bullshit amounts of churn-for-the-sake-of-it in the JavaScript ecosystem aren't normal.

apetrov 2y ago
It depends on the complexity of the project. I assumed something nontrivial, like this project. I outlined some thoughts on the effects of consistent development and what the project might become in a comment above (current state vs. becoming a go-to visualization tool in the field for years to come). Regarding the JavaScript ecosystem—I never mentioned it. Replacing one tool with another has nothing to do with the evolution of a single project.
lucb1e 2y ago
> hobby projects that go weeks to months without commits Just months? :D Last week, a hobby project took down various unrelated services on my server (like receiving email) by causing disk space to suddenly fill up. The root cause is bad handling of an expired third-party domain. I had last touched that in 2012! Or the grocery list software I use daily: its main activity period is probably 2015 through 2018, with features/bugfixes being added maybe once every 2-3 years nowadays. Back in September that I added a small feature we now use on most grocery trips, but since it gets daily use by the developer, it's not like it's unsupported One of my few projects that has regular users besides family is a ~2013 rewrite of a 2011 file uploader. Sometimes there is over a year between any change at all, but whenever someone came along with a bug report I think the fix was never more than a few days away. Come to think of it, it was just today that a friend reported being happy that I still provide it Although stalled perhaps isn't inaccurate, I would feel that it gives the wrong vibe if someone used that to described these daily-used projects where the bug reporting method pops a silent notification on my phone and I'm acting upon any. No offense to u/apetrov, I get what they meant when reading their subsequent replies elsewhere in the subthread

apetrov 2y ago

It depends on the complexity of the project. I assumed something nontrivial, like this project. I outlined some thoughts on the effects of consistent development and what the project might become in a comment above (current state vs. becoming a go-to visualization tool in the field for years to come). Regarding the JavaScript ecosystem—I never mentioned it. Replacing one tool with another has nothing to do with the evolution of a single project.

lucb1e 2y ago

> hobby projects that go weeks to months without commits Just months? :D Last week, a hobby project took down various unrelated services on my server (like receiving email) by causing disk space to suddenly fill up. The root cause is bad handling of an expired third-party domain. I had last touched that in 2012! Or the grocery list software I use daily: its main activity period is probably 2015 through 2018, with features/bugfixes being added maybe once every 2-3 years nowadays. Back in September that I added a small feature we now use on most grocery trips, but since it gets daily use by the developer, it's not like it's unsupported One of my few projects that has regular users besides family is a ~2013 rewrite of a 2011 file uploader. Sometimes there is over a year between any change at all, but whenever someone came along with a bug report I think the fix was never more than a few days away. Come to think of it, it was just today that a friend reported being happy that I still provide it Although stalled perhaps isn't inaccurate, I would feel that it gives the wrong vibe if someone used that to described these daily-used projects where the bug reporting method pops a silent notification on my phone and I'm acting upon any. No offense to u/apetrov, I get what they meant when reading their subsequent replies elsewhere in the subthread