If you're running a Saas, especially a SaaS whose market is developers, and you're NOT having an existential crisis in 2026, the only possible explanation is you're asleep or possibly already dead.

Socially:

Some people don't trust governments to handle one of the most powerful collaboration technologies ever invented (money). All financial systems before Bitcoin were government controlled. Some have behaved in a trustworthy way, many have not. And over the longer term they all tend to mess it up eventually.

So these people set out to build an alternative that they believed governments couldn't control.

Technically:

The interesting key advance that made Bitcoin interesting and successful was coming up with an algorithm that solved the problem of getting parties that don't trust each other at all, to collaborate on maintaining a global ledger to everyone's benefits, without them having to even know about each other.

This is already a feature of money (I don't need to know about you to have indirect financial ties to you) but was not true of the financial system itself until Bitcoin.

The author then appears to draw the wrong conclusion:

> What I find most interesting about the changes I’ve made to code generation in P2, is that the currently compiled code is more than twice as fast as it was when P2 first came out, which just goes to show than in fact Ruby is not slow, it is actually quite fast, you just need to know how to write fast code! (And I guess this is true for any programming language.)

I love Ruby, but it is still a slow language on most benchmarks. That's ok. For most webapps, the bottleneck is not execution-time performance, it's the speed and joy of writing the code. Functionality that never got built because it was too annoying to build is infinitely slow. But there's no point in pretending Ruby, compared to, say, Rust, isn't a slow-as-molasses execution environment. It is. It's ok. It's optimised for developer happiness, not speed.

And yes, even so, you can write slow Ruby code and fast Ruby code. Again, which one makes sense is contextual. But it doesn't make the point that "Ruby isn't slow."

Not only I'm progressively migrating from my Mac onto an Omarchy linux setup... but I've even gone and beaten my Mac into behaving more like Omarchy (with Aerospace as the tiling wm) in the meantime...

"Oh I found some niche issue that bothered me and wrote some code to fix it."

-> HN Front Page

There were some decent scifi authors at the time - not least, Ursula K LeGuin.

I'm still working with RoR.

It's still an incredibly quick, powerful, flexible, versatile framework. I'm able to build pretty large and complex apps all by myself, quite quickly, without fuss.

I'm looking forward to the deployment improvements since that was one of the shortcomings that was still around. Kamal v1 didn't really do it for me (currently using Dokku instead). Maybe Kamal 2 is it.

Perhaps... a longing? Maybe this stranger has helped you find the place where you do truly long for life.

Let the feeling be. Don't label it shame. Don't label it longing. Just let it be. Give it space. Cry if you feel like it. Laugh if you feel like it. Just feel it.

And when you're ready to speak about this with others, there will be many, many willing to be there for you. You are loved.

This way, if someone says "Oh yeah we have an auth module on this site" you don't need to immediately disambiguate the statement.

But then "auth" itself is ambiguous. So it might make sense to get rid of the lot. "Identification" is a good word for the first. Perhaps "Permissions" for the second?

That simulated reasoning is enough to annihilate any human player they're faced with.

As Dijkstra famously said, "whether Machines Can Think... is about as relevant as the question of whether Submarines Can Swim".

Submarines don't swim, cars don't walk or gallop, cameras don't paint or draw... So what?

Once AI can simulate reasoning better than we can do the genuine thing, the question really becomes utterly irrelevant to the likely outcome.

> You can only change the past. The future is unchangeable.

Which is an interesting reversal of the usual perspective, I think. You can change how you perceive the past. You can learn new things about the past. You can change your stories about it. You can even assist others in doing that.

But the future? That is always out of reach, and already encompasses all your attempts to change it.

Lack of plough animals doesn't extinguish the human creative spirit, it just slows it down a lot.

It is curious why bison were not domesticated. I did a bit of research and could not find a clear reason (some suggestions that maybe Aurochs lived in forests and smaller herds, and that may have made them easier to domesticate... but that seems weak).

I'm wondering how much is due to what I'd call the Harari perspective, in Homo Deus - that Eurasians also invented the "god-centric worldview package" that shifted the view of the world from a more animistic perspective (where all beings share the world and so treating animals in the absolutely horrific ways that domestication and agriculture requires is just unthinkable, since they are seen as other beings sharing the world with us) to the "gods and humans" perspective (where god created humanity, and then every other being is just subservient and lacks a soul and therefore can be exploited, murdered, treated like goods, etc).

Mesoamerican religions, despite all the human sacrifice, did see animals and plants as intrinsically valuable and spiritually significant. Native Americans in the North definitely did that too (and they had more exposure to bisons). That would perhaps have led them not to seek to domesticate animals.

It is curious (to me) that no culture emerged that even tried, though (that culture would likely have outcompeted everyone else).

His thesis is precisely that, so he can definitely bear it.

Ultra-summarising:

- The Americas fell behind because they eliminated large mammals before inventing domestication, and not having horses and cows is a huge setback.

- Sub-Saharan Africa fell behind because it is oriented north-south and there are a lot of different climates you have to travel through, and therefore technology exchange is harder.

- Eurasia had the east-west orientation that enabled tech exchange, so it was going to happen there.

- Of the Eurasian regions, China could have been first but being too unified meant that they were less competitive and less likely to repeat high-risk ventures until they worked. Europe was fragmented and competitive which led to faster innovation, including more focus on turning anything into a weapon (e.g. gunpowder, invented in China but turned into war devices in Europe) or a disruptor (paper & printing press).

All seems pretty logical, and does not ascribe Europe any superior moral character. It's just luck.

Unless, of course, you believe that being born in the right place at the right time is related to moral character rather than luck. But I don't think Diamond does that in his book.

Also, on the "almost conquered Europe", I always find it quite mindblowing that they almost conquered Europe - with their light reconnaissance force. The main army was waiting while the lighter 10k horse force did some recon. While doing their recon they wiped out the Georgian army which had been preparing for war for years and so was probably the best prepared army in Europe at the time. The rest of Europe was totally unprepared even for that small 10k force.

Luckily for us, soon after, Genghis Khan died and the entire army turned back. Otherwise Europe would for sure have been conquered with no challenge. Luck of the dice.