Note that this doesn't include the Closure Compiler[0], and doesn't affect Clojurescript[1], which has traditionally used the compiler and related bits of the Google Closure library. [0] https://github.com/google/closure-library/issues/1214 [1] https://clojurescript.org/news/2024-01-24-release
Google Closure Library has been archived
71–80 of 89 posts
Re: Google Closure Library has been archived
#72It's a shame this is being abandoned, because if you want a rich text editor that truly is Gmail's compose editor as it has existed for the past decade - that emits the same structures that Gmail would, handles copy-pasted rich text the same way Gmail does, has the same behavior in typing inside links etc... which is especially useful if you're building an email client that Gmail users need to feel familiar on every…
Fun fact: the code name for the editor was TrogEdit, with Trogdor the Burninator as their mascot. I believe they even had a life size cardboard Trogdor by their desks. It's one of the oldest, most stable, and never rewritten parts of the Gmail codebase.
Re: Google Closure Library has been archived
#73Closure library and the advanced closure compiler to the rescue
Re: Google Closure Library has been archived
#74It's a shame this is being abandoned, because if you want a rich text editor that truly is Gmail's compose editor as it has existed for the past decade - that emits the same structures that Gmail would, handles copy-pasted rich text the same way Gmail does, has the same behavior in typing inside links etc... which is especially useful if you're building an email client that Gmail users need to feel familiar on every…
Fun fact: the code name for the editor was TrogEdit, with Trogdor the Burninator as their mascot. I believe they even had a life size cardboard Trogdor by their desks. It's one of the oldest, most stable, and never rewritten parts of the Gmail codebase.
--
Re: Google Closure Library has been archived
#75Note that this doesn't include the Closure Compiler[0], and doesn't affect Clojurescript[1], which has traditionally used the compiler and related bits of the Google Closure library. [0] https://github.com/google/closure-library/issues/1214 [1] https://clojurescript.org/news/2024-01-24-release
Closure Compiler is half dead anyway, doesn't even support public/private class fields etc from ES2022. I wouldn't be surprised if its gets abandoned within 1-2 years
Re: Google Closure Library has been archived
#76Earlier quoted context omitted.
Are you sure about that? The clojurescript implementation is built on top of the google closure library. Here's an example: https://github.com/clojure/clojurescript/blob/master/src/mai...
The implementation really is not built on top of GCL, the bulk of the standard library is persistent datastructure implementation and functional apis. The few cases here and there like `goog.string` can be removed over time. But really what's the rush? Large portions of GCL have worked unchanged for nearly two decades. Does Google archiving GCL make perfectly good code stop working? When we eventually remove the dire…
Re: Google Closure Library has been archived
#77It's a shame this is being abandoned, because if you want a rich text editor that truly is Gmail's compose editor as it has existed for the past decade - that emits the same structures that Gmail would, handles copy-pasted rich text the same way Gmail does, has the same behavior in typing inside links etc... which is especially useful if you're building an email client that Gmail users need to feel familiar on every…
Fun fact: the code name for the editor was TrogEdit, with Trogdor the Burninator as their mascot. I believe they even had a life size cardboard Trogdor by their desks. It's one of the oldest, most stable, and never rewritten parts of the Gmail codebase.
https://www.youtube.com/watch?v=90X5NJleYJQ (Strong Bad Email #58)
Re: Google Closure Library has been archived
#78Re: Google Closure Library has been archived
#79Has anyone outside of Google had any luck using the closure compiler with a modern-ish stack with the advanced optimizations? Tsickle and the like seem to be archived as well, so it's unclear to me. Google must internally have some tooling to go from ts to closureJS?
Yes, I've used Closure Compiler with advanced optimizations for the Soundslice JS codebase, for around 10 years. It is so, so good! You have to take care to write code in a certain way, but once you understand the constrants it's not a big deal. The advanced optimizations are better than anything else I've seen in the JS world, and it's not even close. It's just insanely good.
What an amazing project, well done!
Re: Google Closure Library has been archived
#80Earlier quoted context omitted.
Fun fact: the code name for the editor was TrogEdit, with Trogdor the Burninator as their mascot. I believe they even had a life size cardboard Trogdor by their desks. It's one of the oldest, most stable, and never rewritten parts of the Gmail codebase.
What does “life size” mean here?