no, they're (illegally) using a private intake system to bypass the courts.

And I think their argument is that the detainees (the "illegal aliens") are not US citizens (according to them), therefore US laws and courts are not applicable.

no, they're serious, but they're not sincere.

once this system is up and running, they can use it to harass and "deport" (rendition) anybody they want based on what tax-deductible contributions they've made to various non-profits.

(it's rendition because a lot of these people are being sent to countries they're not even citizens of. obviously that pertains when sending people to prisons in El Salvador and Sudan. also, when deporting immigrant parents, they've "deported" US citizens who are children or infants to the countries of their parents' citizenship.)

even a swarm of satellites has risk factors. we treat space as if it were empty (it's in the name) but there's debris left over from previous missions. this stuff orbits at a very high velocity, so if an object greater than 10cm is projected to get within a couple kilometers of the ISS, they move the ISS out of the way. they did this in April and it happens about once a year.

the more satellites you put up there, the more it happens, and the greater the risk that the immediate orbital zone around Earth devolves into an impenetrable whirlwind of space trash, aka Kessler Syndrome.

yeah, it's a good post overall, but the humblebrag factor undermines it

sorry but you’re underestimating the number of people who come here, and the range of backgrounds (and interests) they have

yeah, that’s what works for me also. LLMs are a nightmare for debugging but a breeze for this.

another good use case: have it read a ton of code and summarize it. if you’re dealing with a new (to you) area in a legacy application, and trying to fix a problem in how it interacts with a complex open-source library, have the LLM read them both and summarize how they work. (while fact-checking it along the way.)

The problem with Lisp (or at least Clojure) is that abstracting away the boilerplate requires you to correctly identify the boilerplate.

It’s nontrivial to structure your entire AST so that the parts you abstract away are the parts you’re not going to need direct access to three months later. And I never really figured out, or saw anyone else figure out, how to do that in a way which establishes a clear pattern for the rest of your team to follow.

Especially when it comes to that last part, I’ve found pragmatic OOP with functional elements, like Ruby, or task-specific FP, like Elm, to be more useful than Clojure at work or various Lisps for hobby projects. Because patterns for identifying boilerplate are built in. Personal opinion, of course.

Since I had to Google it, 3Com was the company behind Ethernet, a wired networking standard that revolutionized offices in the days before remote work. Like with GUIs, the work started at Xerox PARC.

Ethernet was developed at Xerox PARC and was inspired by ALOHAnet. Metcalfe was however a co-founder at 3Com.

Since I had to google it, Metcalfe was one of the inventors of Ethernet.

Fun fact, he predicted in 1995 that the internet would collapse entirely within the following year, and said he would eat his words if it didn't. In 1997, at a web conference, he put a printed copy of the words into a blender and drank a smoothie made with that paper.

The EPA is currently reviewing its ban on asbestos.