Wow, crazy this still existed. Hasn't been modern for a LONG time.
Google Closure Library has been archived
31–40 of 89 posts
Re: Google Closure Library has been archived
#32Closure. What a fitting name.
I remember disliking google’s project names of that era. Too generic and borrow-y. Closure was a concept in JavaScript. Chrome is what Firefox was calling the parts around the rendered page (UI buttons, etc)
Re: Google Closure Library has been archived
#33Closure Library was originally designed based on the lessons learned from building Gmail in 2004/2005-ish. When it was archived, one of its founders wrote a great thread about how much the JavaScript ecosystem has changed in the last 20 years. It's been a wild ride!
https://www.threads.net/@dpup/post/C2QsW5QsSPW/?xmt=AQGzV4jb...
Re: Google Closure Library has been archived
#34[flagged]
It's a 15-year-old project. Try harder.
Re: Google Closure Library has been archived
#35Has 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?
Re: Google Closure Library has been archived
#36It'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 keystroke... then following https://github.com/google/closure-library/blob/master/closur... line-for-line is still the gold standard, because it grew from the same codebase as Gmail.
I've had great success at a previous startup referencing a prebuilt Closure Library from a modern ES6+ codebase and creating a React-friendly wrapper around the editor component, and using this to power an email templating experience. Ironically, I'm within weeks of needing to do it again, thanks to Zawinski's Law https://en.wikipedia.org/wiki/Jamie_Zawinski#Zawinski's_Law - "Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can." I'll give you one guess what I'll be reaching for, archived or not.
Others have more context on the history and have written more detailed obituaries - but it's a true testament to the engineers that worked on it, that a library can be so ahead of its time that it's still an industry-leading experience 14 years after its initial release.
Re: Google Closure Library has been archived
#37GCL, the Google Closure Library was sunset and this was announced almost a year ago on the mailing lists. The archiving was scheduled for 2024-08-01. GCC, the Google Closure Compiler , is still used by Google internally and they are shifting towards supporting the compiler for tools that emit "ClosureJS" (remember goog.define and goog.provide?). ClojureScript is one of several tools that target "ClosureJS" and there…
Oh, GCL and GCC, not the other GCL and GCC
Re: Google Closure Library has been archived
#38It'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
#39Has 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?
They archived the open source parts , but it's the same stack internally.
Re: Google Closure Library has been archived
#40GCL, the Google Closure Library was sunset and this was announced almost a year ago on the mailing lists. The archiving was scheduled for 2024-08-01. GCC, the Google Closure Compiler , is still used by Google internally and they are shifting towards supporting the compiler for tools that emit "ClosureJS" (remember goog.define and goog.provide?). ClojureScript is one of several tools that target "ClosureJS" and there…
Oh, GCL and GCC, not the other GCL and GCC
Even more confusing: inside Google they call the compiler JSC, unrelated to the JS engine in WebKit.