Does someone know how cross-border payments work, and why it would be complicated for countries to link up their sovereign systems? The article gives the example of Brazil and India, suggests there might be a “liquidity” bottleneck, but omits the details.
The author makes no effort to explain why AI :isn’t: a commodity as Apple and Amazon says. I was looking forward to that. I think the article is weak for not defending its premise. Everything else is fluff.
Yeah nowadays I think non-ClojureScript people use it mostly for legacy reasons or the aggressive minification. Back in the day, aside from the pre-ES5 conveniences I mentioned surrounding inheritance and module bundling, it was also a way for developers to do some basic type enforcement (via JSDoc annotations that the Compiler would check). TypeScript essentially rendered that obsolete.
Yes and yes; in the past, prior to ECMAScript providing first-class inheritance, module ex/imports etc, the Library supplied methods to achieve these in development, and the Compiler would identify these cases and perform the appropriate prototype chaining, bundling, etc. See, eg, goog.provide
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.
I think you are conflating the Closure Library with the Closure Compiler. They are related but not identical. The Compiler, I think, is what makes it difficult to use externs; its “advanced optimizations” can and often does break libraries that weren’t written with the Compiler’s quirks in mind. But advanced optimizations is an option; if you don’t need aggressive minification, function body inlining, etc. you can opt out.
Shadow CLJS has made working with external libraries quite easy and IIRC it lets you set the compilation options for your libraries declaratively.
If you’re on a Mac or iOS you could try creating a Shortcut where you input Markdown, convert to rich text, then output as a PDF. I use Shortcuts regularly. It’s pretty easy to set up. I haven’t tried it on something as larger as 500 pages, though. YMMV
“Decline I” is an instruction for the student to provide the first person pronoun in all cases: I (nominative), me (accusative/dative/ablative), my (genitive), mine (genitive substantive). (I have borrowed the case names from Latin, with which I am more familiar. I think the English cases are nominative, objective, possessive.)
I believe the misspellings in the spelling section are intentional so that the student will identify them—I am guessing that’s the point.
This case is about whose interpretation gets to fill in the gaps.
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.
It struck me that Jepsen has identified clear situations leading to invariant violations but Datomic’s approach seems to have been purely to clarify their documentation. Does this essentially mean the Datomic team accepts that the violations will happen, but don’t care?
From the article:
> From Datomic’s point of view, the grant workload’s invariant violation is a matter of user error. Transaction functions do not execute atomically in sequence. Checking that a precondition holds in a transaction function is unsafe when some other operation in the transaction could invalidate that precondition!
> things get complicated with virtual threads, they shouldn't be pooled, as they aren't a scarce resource
Why not pool virtual threads, though? I get that they’re not scarce, but if you’re looking to limit throughput anyway wouldn’t that be easier to achieve using a thread pool than semaphores?
Spoiler alert. In /The Three-Body Problem/, by Cixin Liu, a planet in the Alpha Centauri system is inhabited by an advanced alien civilization that evolved to survive the hardships related to the unpredictable effects of the three stars on the planet. Though able to survive, it comes at a great cost to their civilization (requiring them to “dehydrate” and hibernate for, sometimes, hundreds if not thousands of years) and eventually they hatch a plan to move to another habitable planet. Fortuitously they receive a message from Earth, from an astrophysicist who detests humanity and invites aliens to invade.
I found the rest of the book (and the two volumes that follow it in the series) to be very entertaining!
A good way to de-risk yourself, so I’d probably take it. But in a private tender offer like this (as opposed to an IPO) the employees will likely pay ordinary income tax, regardless of how long they’ve held the shares, as it is difficult to argue the transaction is not compensatory.
This is true. I think college towns are a boon, too, for remote workers who are looking for a lower cost of living than in large urban centers, without detriment to some of the nice amenities of city life.
Personally I love college towns and wish there were an effort for them to continue to thrive despite the (probable?) demise of small colleges.