Opinions about what?

I guess if you don't understand what I'm asking, you don't have (strong) opinions about any of this 🙂

No, I'm unclear about what the question is. Two possible interpretations: 1. "Is anyone else worried about Google Closure being deprecated?" 2. "Are other people using Squint (or Cherry) for frontend work, and if so what work?"

Yes, all of the above.

https://github.com/google/closure-library is going into maintenance mode, it’s different from the closure compiler.

Right, and I just said "Google Closure"... but both the library and the compiler are dependencies of ClojureScript and that's always felt a bit precarious to me (and I get the impression that getting away from the library impacts ClojureScript directly since it emits goog.* references -- whereas you can avoid the compiler by not using the optimization modes?).

@U04V70XH6 You might be interested in the discussion happening in #C07UQ678E.

I looked at the discussion in #C07UQ678E and it seemed to be very much "oh we don't need to do anything" (despite several people raising concerns)... which doesn't exactly inspire me with confidence...

But there has been low-level continual pushback against the dependencies on Google Closure for years (both the compiler and the library) and the core team just kind of dismissed it all along so... 🤷:skin-tone-2:

At work we tried ClojureScript about a decade ago and built proof of concept apps with Om and then Reagent and decided it wasn't ready for primetime back then (partly the language differences back then, partly the tooling/ecosystem) and so we adopted a sort of waiting game... and meanwhile built all our frontend stuff with JS which seemed a lot more mature, even if the tooling has a stupid level of churn... but I've always kind of hoped we might get to use ClojureScript at some point and the easier interop with Squint (since we have an established JS codebase now) is appealing... ...but I was curious if other folks are a) concerned about the whole Closure thing (apparently not?) and/or b) see Squint/Cherry as a viable (and exciting?) option for doing serious frontend work instead of the traditional cljs tooling?

For me it's all of the above. I am concerned about it being deprecated. I also know the people working on cljs core (and indeed shadow-cljs) are super smart and I trust they are balancing the different tradeoffs in a sensible way and will replace goog. if/when it becomes necessary. As far as I can tell it's not something that has to happen very fast. One thing I like about the Clojure ecosystem in general is low churn and a great deal of care taken when making potentially breaking changes. I'm also super bullish on borkdude.cljs. and excited at the prospect of having squint in particular in my toolbelt. I've used it in a couple of niche cljs->js situations and look forward to using it in more where the tradeoffs and requirements make sense. At the moment for my day to day projects shadow-cljs and cljs have a lot of DX affordances which I don't want to give up just yet, but I can definitely see squint coming into my codebases in addition to these tools to accomplish different goals, just like nbb has previously.