The "Developing Leadership" podcast [1] by Jason Werner (ex Github CTO) and Eiso Kant (founder Athenian) just did a three-part podcast series where this was also discussed. Can recommend.
Except when your app is meant to be used by them for work and their IT has them stuck on an old version of IE.
I know that customer requirements are pretty much unheard of in startup land but other companies have to obey this kind of limitation in order to make any money (which again is an alien concept in startup land -- not every business model survives on growth alone).
For a lot of business owners using an old version of IE, the browser is something to facilitate their bespoke ActiveX application. They probably don't care if their employees can browse less sites.
And on the flip side, a lot of those employees are a sizeable chunk of business for other businesses when they browse on their lunch breaks or whatever. So, large sites aren't going to fully drop support for any browser until after the market share has dried up.
That's their problem. They'll install Chrome. Quit making excuses. I've heard it all a thousand times. Stop supporting old browsers today and business will adapt.
I think you're assuming that the employees in question are permitted to install software freely on their work computers, and/or that the company decision-makers are aware of new sites/services they're denying themselves by their policy.
Firstly, the policy is there for a reason -- often something like "we paid a lot in 2003 for this custom software, and if we upgrade browsers we'll have to pay X to have it rewritten/replaced".
X may be a rather large sum of money -- easily enough to overwhelm whatever benefits they might get by becoming paying customers of whoever's new venture.
There's also a potential for a sort of catch-22; new sites/services may pop up that could even replace their old custom-built software... but if they can't even try it out and the site looks awful on their browsers, a) it's less likely they'll make the jump and b) it gives the impression of being a new-fangled flash-in-the-pan sort of thing. After all, the serious companies online put the effort into supporting older browsers.
1) Install latest version of Rust found here: http://www.rust-lang.org
2) git clone --recursive git@github.com:rust-lang/cargo.git
3) make
4) make install (could be that sudo is needed for you)
Hmm, well, rust's brew seems a little outdated (0.10), so if you are intent on using Cargo soon, I would recommend on building rust yourself or grabbing a new binary from their website.
Stuff being either in Cask or Homebrew is just terrible. Homebrew also has a versions tap. Those two projects should combine efforts and remove ambiguity.
I 100% agree with you. It took me like an hour to figure out where I thought it made sense to put rust-nightly, and I'm still not really sure I did it right. But it works and is way better than the morning compilation cronjob I used to use.
I agree, it works, but we need to keep pressing those guys... or contribute. Cask still doesn't have reinstall/upgrade. As far as I know, Homebrew can't upgrade packages with head versions, and, worst pain of all - Homebrew doesn't support Yosemite or any unreleased OS X version. Being a tool for developers primarily, all the above are must-haves!
[1] https://github.com/carp-lang/Carp