amgreg
Joined 13 years ago
Joined 13 years ago
See: https://effectivetypescript.com/2023/09/27/closure-compiler/
For the most part, I would guess people still use the Closure Compiler because of its aggressive minification or for legacy reasons. I think both are probably true for ClojureScript, as well as the fact that the Compiler is Java-based so it has a Java API that (I am guessing here) made it easier to bootstrap on top of the JVM Clojure tooling / prior art.
Shadow CLJS has made working with external libraries quite easy and IIRC it lets you set the compilation options for your libraries declaratively.
Why do you except Google and Anthropic?
I believe the misspellings in the spelling section are intentional so that the student will identify them—I am guessing that’s the point.
The statute (APA) requires courts to form an independent judgment about the gaps.
The Chevron doctrine required courts in certain cases to set this judgment aside in favor of an agency’s judgment—-basically on the basis that the agencies are closer to the problems and know better.
This setting aside may be the better outcome, however it is not explicitly specified in the statute (APA).
Ultimately, if Congress wants this to be the case, they /can/ amend the statute (APA), effectively enshrining the Chevron doctrine.
At the end of the day, the court’s decision here rests on statutory interpretation (not constitutional doctrine) so Congress could change the outcome by amending the statute (APA) to explicitly codify Chevron. This would be achieved with its ordinary legislative power (Article 1 Section 7 of the Constitution).
The court’s decision does effectively put the ball back in Congress’ court.