4 ms·

I also found the community active and welcoming. I also got a t-shirt. All of my issues were tagged. Unfortunately they weren't fixed, and the stale bot kept ma

I also found the community active and welcoming. I also got a t-shirt. All of my issues were tagged. Unfortunately they weren't fixed, and the stale bot kept marking them as stale. It seemed to me like Gatsby developers were focusing the majority of their time on writing "fun" new features rather than fixing all the sharp edges and broken pipes of the complicated pile of old features.

wpietri 6y ago
That fits if we think about it in POSIWID terms: https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_what_it_does https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha... If the true goal of the devs is to do the fun first 25% of the work, then the signs that a particular job hasn't been finished are unwelcome. A stale-bot sweeps most problems under the rug and, as we see in the discussion here, discourages reporting in the first place. The numbers look better, the devs get to feel like things are under control, and they get to rush on to the next shiny thing. And perhaps it works one layer deeper, too. Their website's all about "fast, fast, fast"! They advertise the ability to "create a complete website in the time it usually takes to build a prototype". I would read a claim like that suspiciously: when I build prototypes, I leave out things that are important for sustainability. But the things I think are "finishing the job right" seem to others as tedious and uninteresting things to be skipped if possible. So perhaps the devs have found themselves an audience like themselves that are fine with a high level of brokenness as long as they get the feeling of moving forward quickly?