All jokes aside, this is a very serious question when it comes to Google products [1]. Imagine having spent 5K on a Jamboard... [1] https://killedbygoogle.com/. - Source: Hacker News / 10 days ago

Https://killedbygoogle.com (and https://gcemetery.co ) the list is endless. - Source: Hacker News / 11 days ago

Alright, let's kick another party off: https://killedbygoogle.com/. - Source: Hacker News / 11 days ago

Someday Google could very likely terminate gmail accounts that block youtube ads Then there is this which just scrolls on and on forever https://killedbygoogle.com (or https://gcemetery.co ). - Source: Hacker News / 12 days ago

With Google’s graveyard[1] growing so fast, I’m careful with new Google announcements. An API like this sounds particularly problematic to replace sometime in future. [1]: https://killedbygoogle.com/. - Source: Hacker News / 17 days ago

I’m not exactly sure what you are trying to do but JavaScript Source Maps basically do this same thing with browsers and they use https://developers.google.com/closure/compiler/. Source: over 1 year ago

I'm using the Google Closure Compiler. I believe it has similar capabilities. Source: over 1 year ago

In a real world scenario you'd probably run the resulting JS through Closure Compiler. It would be nice to see how that affects both code size and performance. Source: over 1 year ago

Kind of funny that Google actually does have a product called the "Google Closure compiler". It creates different kinds of compilations though. https://developers.google.com/closure/compiler. - Source: Hacker News / over 1 year ago

Partially, depending on what's used it also optimizes the javascript code. See Google's closure compiler for more info. Source: about 2 years ago