Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Giving users the choice of "slow" in a webapp means that both hardware and software deployment/management/purchasing is greatly complicated.


"Web 2.0: don't like it? Tough shit."

That's the nice thing about actual software with actual versions that you actually install: it doesn't change out from under you at someone else's whim. No sane person would use a "Cloud" C compiler. Of course, GitHub is just a mashup of online backup and Facebook, so it doesn't matter if it breaks.


Existing users are being served by existing hardware and software. It wasn't "slow" for them before.

Many companies provide existing users with advance notice of technology migration, so they can plan and adapt.

Why is advance customer notice incompatible with Github ops planning?


It's not like they broke git, or some actual important interface. They stopped syntax highlighting on non mainstream languages until new lexers can be written. What on earth would you as a customer have done if they had said, "syntax highlighting in the browser for <your-favorite-language> is going to go away in a week"? Are you going to migrate away from github? Or shrug and say, "bummer"?

Github did the most efficient thing: break it and let the people who actually care fix it.


> It's not like they broke git, or some actual important interface

Does the vendor or the customer decide what's important to the customer?


GitHub is free, the repo owners are not the customer.


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 :-)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: