eventualcomp

Legal culpability is one of the few motives for working appropriately on misalignment. If I/my startup can self-absolve from an infinite paperclip machine problem while getting rich off of it, why should I not?

I would like to define my own thresholds for exploration/exploitation so that I can shape the person I want to be, thanks.

> created in under 15 minutes

This is an artificial constraint that does not serve the reader. Where did the 15 minute constraint come from?

That is an orthogonal matter and maybe my imagination is limited. But when I think of realistic new flags I do not think of a union jack missing its right diagonal in the corner (e.g. if we decide to decompose the UJ primitive).

We could also complain that the crescent is a complex primitive. Why not define it with three parameters: two circle radii with a center offset?

Choosing the primitives is hard and requires domain knowledge/taste, and finding a simple enough implementation solving for key usecases (e.g. decent coverage of maps, meaningful bit encoding) and descoping (e.g. deciding on no emblems) is also hard.

But I am personally impressed with the primitives the author created and the scope simplifications done to achieve it.

Maybe there's an allegory to the sciences. But I rather a model be suboptimal in encoding that can be used to generate hypothetical reasonable flags in its unpopulated states, than having an optimal encoding which doesn't answer questions or reveal possibilities in its unpopulated states. Like what does flag #0xFE look like in an 8-bit encoding? I really like the idea of driving compressed trees in reverse with random data to generate new fascinating (valid) sequences.

Also, for compressing into 8 bits - is this not like saying "I can compress all of Shakespeare's plays in 6 bits" because there are ~39 plays, but then the size of the "shakespearezip" is just the sum of the works?

I think if nuclear weapons were unregulated then we would probably have blown up by now.

I feel like there would either be too many locks or too much contention on something like /var/log or /tmp if that API was ever exposed to userspace.

Waiter, waiter! More optimization articles without benchmarks, please!

Thanks for commenting and acknowledging that it's challenging. My mates and myself have definitely fallen into this. Reminds me of that hackernews post about how doomerism is a siren's song for genZ, forget where it is.

Almost 6 years old. (2020).

Devs gotta eat. Yeah the code is out there but the code is a result of a lot of thinking, prioritization, research into what is needed from the actual product. So now AWS owns that mindshare and talent and will (probably heavily) influence its decisions. I just hope DuckDB doesn't stray from its goal of being the SQLite (e.g. embedded) OLAP.

> I declined to take that offer. I had missed several business meetings that cost me actual money. I couldn't donate blood for years because I had been to the Amazon and was tagged a malaria risk.

RTFP?

Checked the contributor list, please disclose that you're a primary contributor.

No such thing as a too-low risk to reward ratio. That's basically free rewards.