Earlier quoted context omitted.
You could also say that everyone moving to GitHub is leading to a dangerous centralized monoculture that evaluates software quality based on how well it fits GitHub's conventions.
git is still git - people don't even need a github account to have full functionality.
Go is moving to GitHub
41–50 of 244 posts
Re: Go is moving to GitHub
#42Earlier quoted context omitted.
Why does hacker news not have a reddit style 'below threshold' to display none subthreads? :/
I feel your pain. This is coming. In the meantime, we've detached this subthread from its parent so we can mark it off-topic. All: predictable flamewars add no new information, therefore have a signal/noise ratio of zero, and therefore are off topic for Hacker News.
Re: Go is moving to GitHub
#43Earlier quoted context omitted.
I feel your pain. This is coming. In the meantime, we've detached this subthread from its parent so we can mark it off-topic. All: predictable flamewars add no new information, therefore have a signal/noise ratio of zero, and therefore are off topic for Hacker News.
If this area is going to be marked off, then I would appreciate my mod points being restored as well. If you look at my original response, it was pointing out the fallacy in a very particular claim (and nothing resembling a 'flame war').
Re: Go is moving to GitHub
#44Earlier quoted context omitted.
git is still git - people don't even need a github account to have full functionality.
How many Github projects accept git format-patch submissions? There's functionality beyond the basic DVCS commands.
Re: Go is moving to GitHub
#45Considering open source's history, you'd think its primary management tool would be open source as well. I guess it's GitHub's combination of accessible design + performant version control + lack of ads + reliability that made it the premium source for anything open source.
I'm impressed.
Re: Go is moving to GitHub
#46The writing's on the wall for Google Code. I don't think I've seen a new feature in several years.
Re: Go is moving to GitHub
#47Earlier quoted context omitted.
There are a lot of things lacking about GitHub's code review process (pull requests). Off the top of my head: - Merging a pull request (almost) always creates a merge commit, polluting the change history. Gerrit will automatically rebase the changes atop the master branch head, leaving a nice linear history. - Pull requests require the contributor to create a public fork of the repository they're committing to. I can…
> Pull requests require the contributor to create a public fork of the repository they're committing to. You can create Pull Requests within a repository. You don't need to fork the repository if you have push access.
Re: Go is moving to GitHub
#48Earlier quoted context omitted.
To the siblings to this post: it seems rather unlikely as the research is being generated at a rate that far exceeds any one person's ability to read it (especially when they are already busy marrying C and CSP [which is easy to build as a library or add-on to any other existing language] & type theory isn't their specialty).
So, you're criticising someone for not doing something that's impossible? Just stop.
Also, if you take a look at the thread I posted, his attitude and approach re: map, filter & reduce doesn't come across as the most academic or well thought out.
Re: Go is moving to GitHub
#49Google hosting Go on GitHub. Microsoft hosting .NET on GitHub. It must feel like an accomplishment to be implicitly endorsed by these companies. Considering open source's history, you'd think its primary management tool would be open source as well. I guess it's GitHub's combination of accessible design + performant version control + lack of ads + reliability that made it the premium source for anything open source.…
Their website design is beautiful, consistent, making it delightful to use everyday. They fix issues quickly, are reliable, and have top notch customer support. They try to be at the top of their game and offer features to make our work easier (while maintaining simplicity, similar to Go). You can edit posts to fix typos, and GitHub Flavored Markdown is efficient to write. They have the best API and docs I've come across.
It helps that once you're familiar with the workflow, if another project you want to make a contribution to on GitHub, it's super convenient (unlike in the past, think SourceForge and others). Even if you're not, the web flow makes it easy to press edit and go from there.
Re: Go is moving to GitHub
#50Earlier quoted context omitted.
Totally serious. And, it's not just the lack of generics-- that's just the tip of the iceberg.
What problems have the lack of generics caused you in development?