Earlier quoted context omitted.
Many of us are paying GitHub for private repos.
Seems unlikely that this is true for the affected languages like Racket though.
I for one am a paying customer :-)
GitHub dropped Pygments
131–133 of 133 posts
Re: GitHub dropped Pygments
#132Earlier quoted context omitted.
Why is Atom more strategically important to Github than existing developers? Is there an economic belief that Atom will reach some larger base of untapped developers who don't know how to use other editors? If a vendor cannot be trusted to host your content without regression, why would you trust that vendor to supply your mission-critical editor?
No, but the article highlights that maybe they are using Github's traction to get a better syntax highlighter for Atom. As in, instead of waiting for a large community of Atom users contribute Atom syntax highlighting, they simply push the same engine onto Github and let that community take care of the syntax highlighting they actually care bout. If this were the case, it would be slightly evil, but very clever busin…
If the strategy is that obvious, how would it still be clever? Rather than simply brazen, that is.
Re: GitHub dropped Pygments
#133Earlier quoted context omitted.
The promise any service makes. To solve my problems and to work _as a service_ for me.
That's neither how promises nor the laws around them work. GitHub owes you nothing except what was explicitly spelled out when you signed up. Half the difficulty of running a business comes from customers with a sense of entitlement not understanding this.
I was thinking the same, in terms of business relations thinking of anyone doing you a favor comes from the wrong perspective. But the promise to be reasonable is imperative and doesn't have to be spelled out. Of course that counts for both sides, though and the code viewer is hardly the core service. A fact made pretty clear when source views aren't enhanced with links to function definition etc, which, with this announcement, I lost the last hope for.