Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub dropped Pygments

greghendershott.com

Post reply on HN
Print view View original

111–120 of 133 posts

Re: GitHub dropped Pygments

#111

Post by lbearl »

lelandbatey wrote: post #70
conradev wrote: post #57

Earlier quoted context omitted.

One other thing to note is that it's not just syntax highlighting, it's also recognizing the language a given repository is written in. Some of my repositories that use Logos[1] are now incorrectly classified as a combination of Ruby and Scala[2]. [1] http://iphonedevwiki.net/index.php/Logos [2] https://github.com/conradev/Tweaks

Yep. And now Github thinks my Makefile is JavaScript: https://github.com/lelandbatey/link_grab

It comes up as an "Executable File" for me. Guess they are making tweaks still.

Re: GitHub dropped Pygments

#112

Post by tom9729 »

JohnTHaller wrote: post #106
mcphage wrote: post #96

Earlier quoted context omitted.

I'm not sure if it's still the case, but SourceForge used to have an approval process to get a new project / repo set up, which defeats a lot of the utility of GitHub for being able to store whatever projects you want to toss up there.

I don't recall that ever being the case. And I've used SourceForge since 2005.

I remember it being the case in 2007/2008. This is the closest thing I could find to a citation. http://www.codeproject.com/Articles/4439/Getting-started-wit...

"To create a new project you simply register at SourceForge and then submit a new project request. Most projects are approved immediately, and you'll typically get an email notifying you of the approval in ~ 24 hours "

Re: GitHub dropped Pygments

#114

Post by Fuzzwah »

matthewrudy wrote: post #64
shurcooL wrote: post #47

Earlier quoted context omitted.

This planet is also a single point of failure. If a meteor strikes, all our code will be lost.

I would love to see someone offer off-planet backup facilities. Not sure who'd be recovering the data post-apocalypse, but at least it'd be there.

Always bet on Musk.

Re: GitHub dropped Pygments

#115

Post by technomancy »

petepete wrote: post #75
sytse wrote: post #55

Earlier quoted context omitted.

Thanks for mentioning GitLab, we offer unlimited private repo's and collaborators and an on-premises version too.

We've been happily using GitLab for months now, can't recommend it highly enough. If there was an open source bug tracking/ticket app that played nicely with it I'd switch all of our teams over to it sooner rather than later.

GitLab is great for lots of projects; especially internal ones. The inability to control your splash page makes it less than ideal for OSS projects trying to be welcoming to newbies though. (When you navigate to a project page, instead of displaying the readme, it just shows recent commits, etc, which is nice for people working on the project but completely irrelevant to end users.)

Re: GitHub dropped Pygments

#116

Post by alextgordon »

soegaard wrote: post #109
res0nat0r wrote: post #100

Earlier quoted context omitted.

Are the majority of languages now broken, or just a small niche subset that don't see much use vs. ruby, python, etc? If a few minor languages hardly anyone uses as compared to the whole site might need some fixing, this still seems like a win from Github's side of things since per the graph the change did in fact significantly improve render times.

Github now uses the lexer framework from TextMate and SublimeText. If your language community happens to use those editors, then you are fine. For Racket 99% uses either DrRacket or Emacs. This implies that the lexer deployed is very rudimentary. Any pointers besides the TextMate documentation for writing lexers are welcome.

Which is sad, because the TextMate lexer design is really really awful. Mostly undocumented. Lots of oniguruma-specific regexes used in the syntaxes. Inefficient beyond comprehension.

For instance, TM syntaxes can legally have recursion loops in them, which TextMate will cut so that the app doesn't spin into infinite recursion. But the precise way that it does this is a mystery.

The pygments design is better for static syntax highlighting.

Re: GitHub dropped Pygments

#117

Post by mcguire »

raverbashing wrote: post #104
shurcooL wrote: post #47

Earlier quoted context omitted.

This planet is also a single point of failure. If a meteor strikes, all our code will be lost.

At one project I worked, someone created a bug "system will stop working with the end of the world on " (yes, it was a joke) Fortunately the bug was closed.

WONTFIX?

Re: GitHub dropped Pygments

#119

Post by hobarrera »

rdtsc wrote: post #25
isomorphic wrote: post #8

This sort of thing feeds my paranoia about GitHub being a giant single point of failure in the open-source world. I know the argument: Someone, somewhere has a copy of each repo checked out, so we (the nebulous "we") could reconstruct everything from the diaspora of ".git" directories. It just bothers me to think how dependent OSS has become upon GitHub.

Good points. There is a silly joke about that even. It usually goes like -- "Gee, I wish someone would invent a decentralized version control system".

Well, if GitLab supported cross-site pull requests, we'd have just that.

Re: GitHub dropped Pygments

#120

Post by hobarrera »

isomorphic wrote: post #8

This sort of thing feeds my paranoia about GitHub being a giant single point of failure in the open-source world. I know the argument: Someone, somewhere has a copy of each repo checked out, so we (the nebulous "we") could reconstruct everything from the diaspora of ".git" directories. It just bothers me to think how dependent OSS has become upon GitHub.

Not 100% accurate. Issues and pull requests (as well as their respective comments) are not in the git repository. They're not easily cloneable either.

I'd love to see all that metadata in a separate git repo (just like wikies).

Post reply on HN