This was made dramatically obvious in Christchurch, New Zealand, after the 2011 earthquake.

Land that previously housed people or businesses in the central city became unsealed carparks run by an overseas company that dominates parking businesses here, for years, and many still are, 15 years on.

Likewise, the owners of buildings rendered unusable by earthquake damage had no compelling reason to demolish and rebuild, as their local taxes dropped significantly, as they're based on land value and improvement (i.e., building) value, and the building was now worth nothing.

So long as the increase in the value of the land outweighed the now minimal local taxes they paid, they'd still come out ahead when they finally sold.

Hence the local government resorted to naming and shaming the so-called "Dirty Thirty", because they had no other levers to pull.

https://ccc.govt.nz/the-council/future-projects/barrier-site...

But this still doesn't address the previously utilized land that is now just a muddy carpark operating for the benefit of a company in Singapore - they have no economic incentive to invest in a parking building when they can just run their business on several hectares of unsealed and frequently muddy and pot-holed sections in the central city while paying minimal local tax.

And in and around Auckland, New Zealand's most populous city and the most expensive to buy or rent a home in, they struggle with the land bankers, and ghost houses - properties owned solely for (largely untaxed) capital gains.

And then we struggle with a housing crisis.

Like the whole Huggingface thing, OpenAI employees initiated the test, deliberately removed safeguards, failed to properly lock down the environment, and responded incredibly poorly to evidence that things were going awry.

The individual employees bear responsibility, but the people running OpenAI are ultimately responsible for the processes and culture where that can happen.

And then people writing blogposts about "3 civilizations of agents" and "altruistic suicide" by algorithms perfectly muddy the waters and obscure the very obvious responsibility that lies with humans and corporations, which I suspect suits the pre-IPO corporations very well.

I honestly don't.

Māori distinguished water _quality_ without reference to whether or not it was a lake or sea or river.

Wai tai: Salt water

Wai māori: Fresh water, water for regular daily usage

Waiora: Pure water that restored/healed a person

Waikino: Dangerous / polluted water

Waitapu: Sacred water

Which makes sense right? You can have a river that is significantly salty and hence unpotable some distance from the sea, depending on the strength of the tides - likewise you can have a lake near the sea that intermingles with seawater to the extent that it's brackish.

So Māori naming was more based on utility than the geographical distinctions than we're used to in the Eurocentric worldview.

And this also extended to their view on land ownership, which caused so many issues when Europeans turned up and wanted to "buy" "land" from the local iwi/tribes - a chief would grant a European the exclusive rights to grazing in an area, and the European would interpret it as exclusive ownership, and then get angry when the Māori would continue harvesting tuna/eels or birds on "their" land that they'd "purchased".

The Hawaiians distinguished between coastal waters and open waters because in their archipelago of far smaller and more numerous islands, the distinction between the two was important. Think currents, waves, depth.

And I guess I failed to adequately make my point, but I'll try again - when the Polynesians who would become the Māori reached New Zealand, the far larger islands they now inhabited lead them to focus far less on oceanic travel as they pivoted to a focus on the land and rivers they now inhabited.

So a big lake was effectively the same as the ocean for them - a big body of water.

What's really interesting is that in Hawaiian, a close relative with some sound shifts (k/t, l/r, n/ng, so taboo is kapu in Hawaiian, in Māori, tapu, path is ala / ara, the God of the sea is Kanaloa/Tangaroa) they have more than one word for ocean, kai is coastal waters, moana is the deep ocean.

But it makes sense in the geographical context of both societies and how they evolved to their environment, the Hawaiian archipelago is made up of multiple smaller islands separated by waters exposed to the full force of the Pacific, while the archipelago of New Zealand is dominated by two large landmasses separated by a narrow strait that together are about the same area as Germany.

So the Hawaiians remained more tightly wedded to the sea to build their archipelagan societies than the Māori did.

In fact, the Māori lost the knowledge to build ocean-going vessels like the ones that had carried them to New Zealand within a few hundred years because there was no need for it. And their language lost the distinction between "coastal waters" and "ocean" while Hawaiian retained them.

While we have evidence of Māori traveling to Raoul in the Kermadecs early on, as classical Māori culture evolved on much much larger islands, their technology focus on boats switched from ocean going vessels to coastal travel and river travel.

In fact, while "Wai", water, is often considered the Māori word for "river", there's another word that also means river in Māori:

"Ara" - path.

(Of course, it still means a regular path)

I'm most familiar with Python where you get tarred up source distributions that then execute setup.py, but more commonly, wheels, pre-built binaries which don't execute code upon install - and in my company, I've been able to advocate for the work needed to upgrade to a newer Python because available wheels don't support Ye Olde version of Python because a) sdists are a security risk and b) if you're trying to install a package that wants to compile C or Rust, suddenly you get to do the fun "install the the particular version of clang this thing needs, the Python header files, and then set the env vars for the compiler and linkers" dance that slows developers right down.

But then there's the JVM world, where JARs don't execute arbitrary code upon installation - and it's rather uncommon to have packages that call out to a C lib for performance, but you'll get some that wrap existing libraries for functionality like RocksDB.

That's not what happened, go read about it harder, please.

Wait, you're serious?

Limitation of the data set I guess.

Seriously, it does, but I'm very much sarcastic when I say "don't worry".

But if she doesn't (e.g., she wasn't working enough regular hours over six months in the last 12 months, so for example, a stay at home parent) then the father doesn't qualify at all - because why would you need to stay home and support your partner and bond with your newborn child? Pfft.

Both parents have the same responsibility to their kids, to do the absolute best for them, and we should fight back against outdated cultural norms that assume that mothers are the default parent, and that fathers "babysit" their own children.

And got excited that you were open sourcing a chip.

Going to need more sources than an out of context series of lines from an Economist graph.