kloop

I eventually opted to desugaring the scala completely, but we were already on the way out of scala by that point

This was scala 2, so implicit resolution lookup was a big chunk of the problem. There's nothing at the call site that tells you what is happening. But even when it wasn't hidden in a companion object somewhere, it was still difficult because every import change had to be scrutinized as it could cause large changes in behavior (this caused a non-zero number of production issues).

They work well for anything you would use environment variables for, but a chunk of the ecosystem likes to use them for handlers (the signature being a Functor generally), which was painful

That's fair, but what we call a monstrosity by modern standards is much simpler than porting the assembly

There were cross plaform languages before C, but they never really took off for system development the wat C did (OSs, for example were commonly written in pure assembly)

That the community is going to be significantly more dramatic than average

This can only be done with a sentiment that was, at least partially, already there. And may very well happen naturally eventually

It breaks the model of c mapping to the hardware.

Functions in C are just labels you jump to. Assuming you want to capture values from the environment you're defining the function in, you have to implement some sort of function struct that is callable, and it probably won't work with any shared libraries on your system. Also it would be slightly slower, and C programmers tend to not be willing to make that tradeoff

It's from about halfway through the process you describe. If you don't have time to read the whole thing, look for the section on "milking the plant"

You can learn the first one by rote memorization. But to continue down that path requires remembering the product of all language features x syntaxes.

Of course there are. Black markets pop up everywhere to route around government intervention

As a hypothetical, let's say you believe from prior experience that being mugged has a very high probability. Let's say 50% because it's easier.

Let's also say your friend points out that you've left your home hundreds of times this year and haven't been mugged. 50% seems like a ridiculous overestimate.

Reexamining your priors would involve not only changing your mind about the chance of being mugged, but changing downstream beliefs that might be influenced by that belief (such as what public policies you support).

It's a common phrase in the ratsphere (and its descendants).

Changing your mind is one outcome, but the implication is that it requires a complete reexamining of your worldview, as changing the internalized probabilities can have many effects on perceived likely outcomes.

Cable was never regulated like that. The medium actually mattered in this case

As a platform, they can probably get around counterfeit items being listed/sold, but sending one from a different seller seems it might open them up to legal risk if Amazon knows there's counterfeits floating around.

I'm sure we all accept the risk in the fine print somewhere, but that only matters until it makes the news and a politician thinks they can get reelected by going after them

That's why the c_str method exists, so you can get a pointer to a null terminated character array

It's generally only recording private conversations that's illegal.

It feels like you didn't think about the differences between the two situations at all

Agreed on all further ones, however

You just can't put people on the vessel while you're doing that part

Trying it isn't exactly locking you into anything

If you get a key wrong it throws (panics in go)

    var res map[string]any
    err := json.Unmarshal(&res)

Don't get me wrong, the project is absolutely insane. There's an api with a gpu layer for raster transformation.

But the build process is still:

    go build [-tag {project name}] .

A little chewy, but you get used to it. And you definitely aren't short of fiber if you also have a salad that day

Any time you don't know how to do something, google it (or chat gpt mostly works these days).

Yes, you can throw the nodes on an array in the heap to allow tail recursion, but at that point you're going to be losing to a map with all but the biggest datasets, and even then the copies really aren't desirable

They abused a similar one in the US constitution (the commerce clause) to rule that growing wheat on your own land for personal consumption counted as "interstate commerce" (Wickard v Filburn) and backdoored into the federal government controling basically everything physical.