4 ms·
they need to be able to dial support. FTFY. Vendor apps and commercialized software aren't purchased (to my knowledge) with the intent of being able to point t
by prawks 14y ago
they need to be able to dial support.
FTFY. Vendor apps and commercialized software aren't purchased (to my knowledge) with the intent of being able to point the finger with the buyer's lawyer. The reason large enterprises prefer Perforce/TFS/etc. is (along with their proven capability to scale) that if something goes wrong they can call the vendor for help.
While you might be able to post on a usergroup and hope for a response, you can't call Linus directly. That's a big difference for the people making the decisions from a financial, architectural, and tools-planning level.
- phaemon 14y agoYou can buy Git support from several different vendors. Were you honestly not aware of this? Try googling for "Git support".
- elemeno 14y agoWhich isn't quite the same as being able to get support from the company which built the software and who can push out a new release to fix the bug that you've just run into.
- phaemon 14y ago(is there a better way to do quotes on HN?) > Which isn't quite the same as being able to get support from the company which built the software I'm sure they'll build Git for you if you ask :) Do you think the original authors of Perforce etc. are still with the company? Are you under the impression that their current development team understand the Perforce source code far better than people providing professional Git support understand Git's? > and who can push out a new release to fix the bug that you've just run into. That's exactly what Git support can do. Why not? [edit: to clarify who "they" are]
- hanksf 14y agoChristopher Seiwald is still at Perforce. I would have to say: Yes, the current Perforce development team understands the Perforce source code intimately at least as well as the core developers of Git know Git, if not better. Disclaimer: I work for Perforce