top | item 10989703

Improved commenting with Markdown

65 points| Amorymeltzer | 10 years ago |github.com | reply

30 comments

order
[+] manachar|10 years ago|reply
Seems that Github is recognizing that more and more non-dev types are interacting with Github in various ways and are providing tools to help them out.

I suppose it's fine, and certainly easier than teaching newbies Github-flavored markdown.

One complaint: Using the aA icon to hide the different headers menu. Headers are not just "bigger text" as the icon indicates. They should use a different icon that indicates its for headers and has nothing directly to do with font-size.

[+] browseatwork|10 years ago|reply
Is this why GitHub unicorned for a bit yesterday? I'm looking forward to the engineering blog post talking about what went wrong and how they fixed it.
[+] rmchugh|10 years ago|reply
Disappointed that Github still haven't responded to the issues raised in the open letter a few weeks ago.
[+] nikolay|10 years ago|reply
Yeah, that's pure arrogance! Time to reconsider GitLab or Bitbucket!
[+] mofle|10 years ago|reply
Power users can remove it by putting this in their user style:

    .toolbar-commenting{display:none !important;}
Use with e.g. https://chrome.google.com/webstore/detail/stylish/fjnbnpbmke...
[+] rasz_pl|10 years ago|reply
Power users? how is disabling few icons empowering anyone? The space is still there, blank and wasted. Do you scratch all the button/knob markings off in your car because you are a power driver?
[+] prezjordan|10 years ago|reply
Or by adding `github.com##.toolbar-commenting` to your favorite adblocker's custom lists :)
[+] cthulhujr|10 years ago|reply
>Have feedback on this post? Let @github know on Twitter.

This probably isn't new, but I just noticed it. For shame.

[+] kingosticks|10 years ago|reply
Using github regularly was what got me to learn markdown and I'm very grateful as I've found it useful in lots of different places. I'm not convinced this change was really worth doing, especially if it was at the expense of features people have been asking for.
[+] nilliams|10 years ago|reply
I don't think that the belief that feature X was created at the expense of feature Y is a reasonable assumption. Who knows how this feature came about? It could have been a Githubber's 20% project, or weekend hack project, or largely down to a 3rd party library.
[+] gravypod|10 years ago|reply
This seems much harder to implement than a comment rating system so we don't see +1 spam.
[+] venning|10 years ago|reply
I doubt that. This update is entirely client-side, while a rating system requires data management server-side in addition to the user interface elements.

That doesn't mean ratings are difficult, just more difficult than this.

Besides, the developers in place to build this update may not overlap at all with the developers in place to implement new rating functionality.

[+] detaro|10 years ago|reply
Does anyone know a similar component/library to do something like this on your own website. Most I've seen try to build a full Word-like editor, without the markdown aspect?
[+] WorldMaker|10 years ago|reply
I've not used it myself (yet), but Prose Mirror (http://prosemirror.net/) is the one I have bookmarked and has been featured here on HN in the past and seems to be very full featured and from the demos it seems flexible everything from the full WYSIWYG-style editor that some users may want to this sort of simple toolbar over a Markdown field.
[+] nikolay|10 years ago|reply
Fugly and distracting!
[+] nikolay|10 years ago|reply
Why the downvotes?! Okay, I use some strong language, because while Bitbucket is introducing Projects [0], GitHub is working on bells and whistles! In the time of Medium.com, we know there are better ways to allow formatting controls!

I understand GitHub is in desperation to go beyond programmers, but this is a ridiculous expansion goal!

[0]: https://news.ycombinator.com/item?id=10950730