29 ms·

It's probably been stated a million times before but it's hard to remember what coding was like before github. CVS and subversion - what's that? Github is so pe

It's probably been stated a million times before but it's hard to remember what coding was like before github. CVS and subversion - what's that? Github is so pervasive that when a project uses another git code sharing site you just get annoyed. Github Issues may suck, but it's so darn convenient and so well integrated. It's far worse when a project uses another ticket tracking system and just uses github for pull requests. Just give in to our new code overlords and go with the flow.

peatfreak 10y ago
> Just give in to our new code overlords and go with the flow. No. They are turning coding into a monopolistic monoculture. Not everybody loves pull request-based workflows, you know.
- yepperino 10y ago
  You're right. I'm going to go back to uuencoding my tar files and posting them on usenet.
  - mwfunk 10y ago
    You clearly are far too young to have ever done this. :)
  - drauh 10y ago
    You need to split them, first. ;)
kevin_thibedeau 10y ago
I always cringe when I find a useful tool still clinging to Sourceforge and it's abomination of a web site.
bdcravens 10y ago
> Github is so pervasive that when a project uses another git code sharing site you just get annoyed Bitbucket's ability to lock down branches is pretty nice. > Github Issues may suck, but it's so darn convenient and so well integrated. It's far worse when a project uses another ticket tracking system I don't feel this is true, having worked on projects that used Jira, Unfuddle, Pivotal Tracker, Assembla, Trello, etc. Of course, none of those systems have the killer feature of turning a ticket into a giant scrollfest of "+1", emojis, and animated gifs.