Earlier quoted context omitted.
What does “life size” mean here?
The same size as a live Trogdor, of course.
Of course, how silly of me!
Google Closure Library has been archived
81–89 of 89 posts
Re: Google Closure Library has been archived
#82I don't even know what this library is (quite an ungooglable name), but I don't get it. It's open source licensed. Why not just, like, not "close" it? Just keep the code and the docs up.
Which is...exactly what they did.
I don't understand how what I said can be downvoted while also people are shaming it as "another project in the Google graveyard". To me it's a matter of framing---sort of what my point is here---it was framed as a kind of death.
Re: Google Closure Library has been archived
#83It'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…
You can still use the goog.editor, even if the repo is archived, you can still fork it.
Re: Google Closure Library has been archived
#84I have very fond memories of joining Google and discovering the Closure library. It had everything and in an era before npm, JS modules, and ES6... it made writing JS feel magical. Impossibly large projects felt possible, and complex systems felt maintainable. These days it feels a bit like boost is to modern C++. A monument to amazing engineering of the past, but something to keep in the archive.
CL wasn't the only powerful library in that era - there were already: Dojo Toolkit, Ext JS, YUI, qooxdoo and jQuery.
Re: Google Closure Library has been archived
#85GCL, 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…
> GCL existed at a time when JavaScript had no notion of a module system whatsoever (not even CommonJS).
By 2007, Dojo Toolkit already had a working module system: https://web.archive.org/web/20071120165657/http://dojotoolki...
Re: Google Closure Library has been archived
#86Whats the goog.framework.of.choice these days ? For those who haven't written closure code - whats the framework of choice at google these days?
It's a merge of Wiz and Angular: https://blog.angular.dev/angular-and-wiz-are-better-together...
Re: Google Closure Library has been archived
#87Re: Google Closure Library has been archived
#88GCL, 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…
I’ve used the Google Closure Compiler for some JS13K projects, since it is so effective at producing small JavaScript code. At the time (a few years ago), there were some rough edges trying to use the Closure Compiler without the Closure Library, but they weren’t major problems—in fact, there was only one thing I added to my project as a workaround: const goog = { define(name, value) { return value; } }; That was it.…
This is more or less what I've done as well when I've used Closure Compiler for personal projects in the past... and I was one of the Closure Library maintainers! This cognitive dissonance was just one of many indicators that the library was ready to move on.
Re: Google Closure Library has been archived
#89Earlier quoted context omitted.
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
It is indeed, and the reason is because Google is switching to wasm.
Not exactly. Google is using wasm where it makes sense to do so.
Google is heavily invested in TypeScript and JavaScript. Closure Compiler is far from half dead but the need to support current language features is mitigated by translating front ends (like TypeScript).
It will support these features eventually. Public field support is mostly there, just not on by default.