Re:Chrome Is The New C Runtime
by nilsbunger on Friday January 17, 2014 @08:12PM
(#7079577)
You build the libraries and link them into your libraries. If you maintain a cadence of updating your Chrome checkout every month, you will mostly be OK (though this can vary, of course).
So every month if I update I will be required to fix my application to work with the new versions of the library. Perhaps say 25% of my time will be _only_ on maintenance? And from what I recall things are not deprecated for a while, but very rapidly changed with little to no warning. This was a major headache.
Re:Chrome Is The New C Runtime
by bd_at_rivenhill on Friday January 17, 2014 @11:50PM
(#7080120)
Why not just stick with a stable version for a while? Updating every month sounds like a huge headache.
Re:Chrome Is The New C Runtime
by erichocean on Saturday January 18, 2014 @12:09PM
(#7081417)
Because the Chrome team makes huge, breaking changes to their code APIs with breathtaking rapidity. If you don't update that often, it'll just get harder and harder and harder to do.
Google can do this (in general) because they have a single source tree (although IIRC Chromium isn't actually part of that). Point is: when you only care about your own code, as the Chrome devs do, third parties are in a really bad place to try and stay current.
Edit: to be clear after you get your app up and running with the current version how much time has to be spent on ongoing maintenance down the road?