6

Hey, if your repo shows up as a popular search result, and there hasn’t been an update to it in 7 years, AND it has more than 200 open issues, AND it’s a buggy piece of shit… DELETE THAT SHIT ASSHOLE. It’s a disservice to let people use your fucking stupid abomination that was relevant years ago. Swallow your pride and remove it from the internet.

Comments
  • 2
    I tell you what happens: Some people who don’t actually like to think about the future chose whatever tech pops up first in their search result without evaluating other options. If that third party ends up being a shitfest, then other devs have to suffer with that decision.

    “wEll iF u FinD a BuG U nEEd tO CoNtRiBuTE”

    BITCH I AM NOT GOING TO CONTRIBUTE TO YOUR LEGACY DOGSHIT PIECE OF GARBAGE THAT NO ONE SHOULD USE ANYMORE. EVEN IF I DID SPEND HOURS FIXING A FEW BUGS, IT WOULD BARELY BE A DROP IN THE BUCKET OF A SEMBLANCE OF HOPE.

    IF YOU, THE CREATOR ABANDONS IT, THAT MEANS YOU DON’T BELIEVE IN IT ANYMORE. FUCK YOU AND MAKE THE REPO PRIVATE SO IT DOESN’T TAKE AWAY FROM OTHER PROJECTS THAT ARE ACTUALLY FUCKING USEFUL!
  • 4
    One of the first things I look for in a project. How long it has been that things have changed? If I don't see updates to anything in months, preferably weeks, then I move on.
  • 3
    So if you’ve got a bunch of projects still relying on it, what happens? Just leave them high and dry?
  • 1
    THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  • 0
    In other words: If I provide this for free and without guarantees, don't expect anything. You're free to do whatever with it though.

    That said, if it's really not working well and/or not actively maintained, a note in the readme would be nice.
  • 0
    @black-kite in a lot of cases, yes, leave them “high and dry”. Let me put it from the dev perspective: if a software your project relies on is filled with bugs, and your manager says “if it ain’t broke don’t fix it”, how else will you be able to argue that you should use a newer technology unless the one you are using is literally deprecated. From your argument, everyone should still support IE because a lot of dumbass companies still rely on it. In this industry, it’s either fucking update your shit or get left behind in old broken bullshit. Which side do you want to be left on?
  • 0
    @saucyatom why not just admit and announce that it’s deprecated and move on to create something better? We all need to stop living in our past. What is the reason for keeping it around? Nostalgia? Showing off as past projects to get hired? What?
Add Comment