5 ms·

So it’s a google branded yaml? Let’s raise a glass to our blue eyed comrades who’ll adopt this fully, only for google to decide in 2-3 years to completely and

by nabdab 7y ago

So it’s a google branded yaml? Let’s raise a glass to our blue eyed comrades who’ll adopt this fully, only for google to decide in 2-3 years to completely and aggressively kill it again for no apparent reason.

dvtrn 7y ago
Pardon for slamming my ignorance down on the table here: I know Google has a tendency of killing products but I’m not familiar with many of their engineering tooling being similarly sunset with comparable frequency. Any named examples? I’m sure there are-and likely they just elude me at present, maybe seeing their names will jog the memory probably?
- mirekrusin 7y ago
  jsonnet? :)
  - zellyn 7y ago
    The jsonnet mailing list still has activity. Is the project dead?
- TheDong 7y ago
  You don't hear as much about developer tools being sunset because they rarely impact as many people and that makes less interesting news. Examples include: AngularJS (replaced by a rewrite of angular effectively), GWT (donated as 'open source' with minimal continued google involvement), basically 90% of all 20% projects by googlers that weren't official google stuff (too many examples to name, practically all of them), the xmpp api for google talk (and all associated library code, including some open source xmpp extensions, libjingle), tons of chrome and android libraries that were killed/deprecated as part of new versions not using them, ARC (https://en.wikipedia.org/wiki/Google_App_Runtime_for_Chrome https://en.wikipedia.org/wiki/Google_App_Runtime_for_Chrome), the caldav API for google calendar and any associated libraries... I could go on, but the majority of the relevant examples are the 20% projects that never made it, and I'd rather not list any of those since they're largely single-person projects and it's kinda personal to comment on any of em.
ben_jones 7y ago
Worst case scenario it has a short life and is forgotten for a better OSS alternative but remains the default for several Google projects and a number of developers are forced to learn and maintain it as it becomes brittle with age. With that as the worst case scenario, it's more than worth the try.
DEADBEEFC0FFEE 7y ago
It's on GitHub, if you fork it, they can't kill it. If you use it, contribute to it.
michaelmrose 7y ago
How much support does the configuration language that basically converts to json need? If your <insert language> here supports json then the support required is a library to convert cue -> json or at worst if nobody cares about the format anymore a program that converts one time from cue -> <insert new format here>.
lonelappde 7y ago
It's not Google branded and who has blue eyes?

by nabdab 7y ago

dvtrn 7y ago

Pardon for slamming my ignorance down on the table here: I know Google has a tendency of killing products but I’m not familiar with many of their engineering tooling being similarly sunset with comparable frequency. Any named examples? I’m sure there are-and likely they just elude me at present, maybe seeing their names will jog the memory probably?

mirekrusin 7y ago
jsonnet? :)
- zellyn 7y ago
  The jsonnet mailing list still has activity. Is the project dead?
TheDong 7y ago
You don't hear as much about developer tools being sunset because they rarely impact as many people and that makes less interesting news. Examples include: AngularJS (replaced by a rewrite of angular effectively), GWT (donated as 'open source' with minimal continued google involvement), basically 90% of all 20% projects by googlers that weren't official google stuff (too many examples to name, practically all of them), the xmpp api for google talk (and all associated library code, including some open source xmpp extensions, libjingle), tons of chrome and android libraries that were killed/deprecated as part of new versions not using them, ARC (https://en.wikipedia.org/wiki/Google_App_Runtime_for_Chrome https://en.wikipedia.org/wiki/Google_App_Runtime_for_Chrome), the caldav API for google calendar and any associated libraries... I could go on, but the majority of the relevant examples are the 20% projects that never made it, and I'd rather not list any of those since they're largely single-person projects and it's kinda personal to comment on any of em.

ben_jones 7y ago

Worst case scenario it has a short life and is forgotten for a better OSS alternative but remains the default for several Google projects and a number of developers are forced to learn and maintain it as it becomes brittle with age. With that as the worst case scenario, it's more than worth the try.

DEADBEEFC0FFEE 7y ago

It's on GitHub, if you fork it, they can't kill it. If you use it, contribute to it.

michaelmrose 7y ago

How much support does the configuration language that basically converts to json need? If your <insert language> here supports json then the support required is a library to convert cue -> json or at worst if nobody cares about the format anymore a program that converts one time from cue -> <insert new format here>.

lonelappde 7y ago

It's not Google branded and who has blue eyes?