Let's Make GitHub Better, Together
shurcool.github.io
shurcool.github.io
http://letsmake.github.io/bettertogether/
This original repo[2] was made by someone who appears to now work at GitHub.[3]
[1] https://github.com/shurcool/bettertogether
- Syntax highlight when diffing: https://github.com/danielribeiro/github-diff-highlight
- Better personalized search: https://github.com/danielribeiro/Octogrep
A few Hubbers did see the site, but that is, of course, half the story, and I can honestly say that that wasn't the reason I got hired. I did also send in a resume weeks earlier, which did also get seen. It was the right place, the right time, and the right skills.
I would suspect--and this is just my opinion--that anyone attempting to create a site to highlight suggestions won't impress anyone. It worked once, and you'll need your own way to stand out. Uniqueness is what's valued here, not number of HN points or comments.
I'm going to mark my repo as Private to discourage copycats. I apologize for that.
https://github.com/skratchdot/github-editor-theme.user.js
I have a few other user scripts that I like to use as well when browsing Github:
https://github.com/skratchdot/github-repo-filter-info.user.j...
https://github.com/skratchdot/github-repo-counts.user.js/
https://github.com/skratchdot/github-code-search.user.js/
https://github.com/skratchdot/github-get-missing-description...
But why is this the #1 story on the hn frontpage?
I love github and use it quite a bit, but why nitpick over every tiny github issue/feature on the hn frontpage?
There's too much venting on the front page. We're not all whiners that keep on ranting about how this and that is crap (hyperbole, but there's truth in that).
We're supposed to be the builders of the future, so instead of grinding axes, let's go and chop some wood.
And let's talk about trains that arrive on time for once.
Instead of just stating the problems and some possible solutions, it wraps it up with faux sentiment about "loving" GitHub, and making it sound like GitHub is a poor soul suffering from some medical condition.
GitHub is merely a tool, hopefully just one among many in any given developer's toolbox. It seems kind of weird to me to think of it as anything but a tool, and especially weird to tread so lightly or carefully when discussing its flaws.
if you look at what happens with gitlab, just imagine how much it would advance github itself it they would have a repo for which people could open PRs
Chromium + Debian
Wow. Looking at my sibling comments, this is some full spectrum incompatibility. Abandon ship on these videos!
Granted, needing additional plugins is kind of bad. But I don't know an easy way to embed very short videos so it's as good a solution as any.
- Using a browser that supports the QuickTime container format (i.e., has the QuickTime or compatible plugin installed)
- Using a browser that supports the <video> element with the h.264 codec (not Firefox).
- Using a device that can decode 3Mbps h.264 video (not iOS devices).
This is more for the sibling comments, but on Hacker News, I'd expect people to take a minute to check why something is or isn't working for them on a page instead of just commenting what browser/OS combo they're using.
As for your points:
- installing QuickTime is not an option (in my opinion it's a piece of bloatware crap that should be retired)
- why should I not use Firefox? just because it chose to support only open video formats
- last time I checked iOS devices sold way more than Macs and I bet a lot of people check out HN using them
Problem: the page is more or less only addressed to people using MacBooks and Windows/Chrome !?! (maybe should include that in the HN link to the article)
Solution: it only takes 10-15 minutes to convert the videos to ogv or webm and add new source tags to the code for fallback thus making the page accessible to the rest of the world
P.S. I did not mean for my first comment to sound like a snarky remark (the blood rush to the brain took over for a moment). I should have included more details about the nature of the problem. Cheers.
To that point, the list of conditions I presented weren't normative, they were descriptive. The videos won't work in Firefox because Firefox doesn't support h.264. Likewise, they won't work on iOS devices because even the latest generation only decodes 2.5Mbps h.264 video. So 10 comments listing all the browser combinations people tried is pure noise: taking a minute to look at the video would've been enough to know which browser/OS combinations were going to work.
They have always been really fast and responsive in my experience.
The reasoning? If you star a project, you're usually interested in the project's announcements, but not always. In particular, some projects might have high-volume announcements. That's perfectly okay, if the particular project culture wants them; but users who view high-volume announcements as annoyances or even borderline spam can still turn that particular project's announcements off, and still be able to have it starred.
If not, maybe he should be using some open source Git GUI if he wants to work together. Although I don't know of one offhand. I just use the command line myself.