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

61–70 of 133 posts

Re: GitHub dropped Pygments

#61

Post by hansjorg »

isomorphic wrote: post #43
Demiurge wrote: post #15

Earlier quoted context omitted.

I don't think it's paranoia. I think it factually is a single point of failure, which is a bad thing(tm). And GMail is a single point of failure for my (and my companies) e-mail, and that bothers me too, despite the fact that I'm not doing anything about it :)

Google is a giant single point of failure. Others would rush to fill the vacuum, but it'd be a brutal few months (years) while we all relied upon Bing. Is there any GitHub-esque outfit waiting in the wings that provides free OSS hosting?

There's also Gitorious:

https://gitorious.org/

Used by projects like Qt, GnuTLS, Haiku and CMake.

Re: GitHub dropped Pygments

#63

Post by frabcus »

isomorphic wrote: post #59
agumonkey wrote: post #56

Earlier quoted context omitted.

Should there be a limit on the size of any organ, to avoid this bit bus factor ? Like hierarchies starting to be needed after a group reaches 150 people.

Well, the current Internet pendulum has swung to nearly the polar opposite of federated services, much to the dismay of my inner software-libre graybeard. Even a duopoly (!) would be preferable to a single vendor.

Bitbucket is extremely good these days!

Re: GitHub dropped Pygments

#64

Post by matthewrudy »

shurcooL wrote: post #47
Demiurge wrote: post #15

Earlier quoted context omitted.

I don't think it's paranoia. I think it factually is a single point of failure, which is a bad thing(tm). And GMail is a single point of failure for my (and my companies) e-mail, and that bothers me too, despite the fact that I'm not doing anything about it :)

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.

Re: GitHub dropped Pygments

#65

Post by colechristensen »

Twirrim wrote: post #52
isomorphic wrote: post #43

Earlier quoted context omitted.

Google is a giant single point of failure. Others would rush to fill the vacuum, but it'd be a brutal few months (years) while we all relied upon Bing. Is there any GitHub-esque outfit waiting in the wings that provides free OSS hosting?

https://bitbucket.org/ https://www.codebasehq.com/ https://www.fogcreek.com/kiln/ https://about.gitlab.com/gitlab-com/ I must admit, I rather like bitbucket, you can get free private repositories with them too.

I've tried a few and as far as I can tell they're all pretty good but not quite there.

Re: GitHub dropped Pygments

#66

Post by luch »

shurcooL wrote: post #48
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.

> GitHub being a giant single point of failure What is our definition of a "point"? If you have an external hard-drive backup of your laptop, that's 2 points of failure, right? If someone else has 10 external hard-drives that they keep in different places, that's 10 points, yes? But what stops you from calling all those hard-drives "a giant single point of failure"? If all of them are destroyed, the data is lost. I j…

You're right about the 10 hard drives : if you've bought them identically at the same time, it's likely they all gonna fail in a short time span. I've recently heard about the "3,2,1" rule concerning backup :

  - 3 images of your data (1 original + 2 copies).
  - 2 types of media (e.g. extHD and DVD)
  - 1 offshore location (e.g. bank vault, your parents' house,etc.)
Of course it's not a golden rule, but it can prevent catastrophic failures.

Re: GitHub dropped Pygments

#67

Post by pjc50 »

volent wrote: post #60
isomorphic wrote: post #43

Earlier quoted context omitted.

Google is a giant single point of failure. Others would rush to fill the vacuum, but it'd be a brutal few months (years) while we all relied upon Bing. Is there any GitHub-esque outfit waiting in the wings that provides free OSS hosting?

If Google goes down, go with duckduckgo instead of bing please :)

They're an anonymising frontend to bing with a number of extra search utilities.

Re: GitHub dropped Pygments

#68

Post by pjc50 »

cespare wrote: post #4

I assume the new syntax highlighter is way, way faster than pygments. It's written in C++ rather than Python. (Atom uses the same grammar format, but a Node implementation.)

Given the discussion going on at https://news.ycombinator.com/item?id=8650952 , this sounds like it might also increase the risk of exploit.

Re: GitHub dropped Pygments

#69

Post by agumonkey »

isomorphic wrote: post #59
agumonkey wrote: post #56

Earlier quoted context omitted.

Should there be a limit on the size of any organ, to avoid this bit bus factor ? Like hierarchies starting to be needed after a group reaches 150 people.

Well, the current Internet pendulum has swung to nearly the polar opposite of federated services, much to the dismay of my inner software-libre graybeard. Even a duopoly (!) would be preferable to a single vendor.

True, I was asking this in a topic about systemd vs set of old protocols. It seems that where the universe is headed right now.

Re: GitHub dropped Pygments

#70

Post by lelandbatey »

conradev wrote: post #57
abhinavg wrote: post #11

I honestly don't see a problem here. They decided to change a backend library for a non-essential system in their product. Most services don't ask for permission or make announcements when they make changes like this. The approach seemed to be, if things break, people will report it and we’ll fix it. While this may not be the best approach, the number of languages supported is too high for a person to check each one…

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
Post reply on HN