usagisushi

Here's a somewhat cyberpunk-ish fact I learned today: Back in '98 Taiwan, unbranded, mysterious desktop CPUs called Golden Soldier ("黄金戦士") were available in the street. It turns out they were actually modded mobile Intel CPUs installed in slockets.

https://pc.watch.impress.co.jp/docs/article/980618/parts4.ht... https://ja.wikipedia.org/wiki/%E9%BB%84%E9%87%91%E6%88%A6%E5...

BTW, speaking of repair culture, I love this idea of repurposed headless MacBooks.

https://www.notebookcheck.net/Screenless-MacBooks-masqueradi...

They are both based on WireGuard (kernel-space and user-space `wireguard-go`), so I guess there's no significant difference in performance for typical usage.

In terms of stability, Netbird has been pretty good for me. I've been using Netbird as the backhaul network for my laptop, phone and inter-site k3s cluster for several years without major issues.

One major downside of Netbird is that its Android client can be quite a battery drainer [1]. (It keeps your fingers warm during winter, though!) As for Tailscale, it offers some neat features like Funnel, which is missing in Netbird, but in my case, covered by DNS and k8s Ingress.

[1]: https://github.com/netbirdio/netbird/pull/3379

It's a mesh VPN, so peers communicate directly without additional delay.

I opted for Netbird myself because Headscale's UI felt too basic for me back then. Has that improved over the years probably?

There's a creepy Japanese urban myth about a guy who injured his knee at the beach. He developed knee pain, so he went to the doctor, and they discovered barnacles growing inside his kneecap. A goose appearance would probably make it goosebump-less.

Or, for a lazier approach:

    $ head -10000 *
    ==> package.json <==
    {
      "name": ...
      ...
    ==> tsconfig.json <==
    {
       "extends": ...
      ...

    $ head -10000 * | llm -s "generate a patch to switch this project to esm"

I came across something interesting titled "Apple iPhone was launched, presentation (2007-12-31)"[0]. It mentions Nokia N800 and implicitly implies a lineage of devices (N770 > N800 > N810 > N900 > N9). Sometimes I wonder what Nokia might have been like in a timeline without Jobs and Ballmer.

> Leverage N800 with its touch screen - it competes nearly in the same arena

[0]: https://repo.aalto.fi/uncategorized/IO_926740c7-5165-439a-a0...

Here it is https://pastebin.com/64825QxC

Great write-up! Recently, I struggled with DynamoDB and eventually opted for a library called ElectroDB, which supports a type-safe way to model entities in Single Table Design.

Noob question: For DynamoDB, I think internal partitions are automatically split based on usage. Is it still worthwhile to apply double-sharding at the application layer as well? Is cross-partition querying a key factor here?

SST (v3, ion) is awesome! Its live Lambda debugging feature totally changes the way I develop Lambda functions. It has the potential to be a cloud vendor-independent alternative to AWS Amplify Gen2.

Since SST allows you to use Pulumi code, you can code your infrastructure extensively even if some resources are not directly supported by SST itself. However, for such usage, it also has rough edges inherited from Pulumi. For instance, I encountered issues with cyclic dependencies [1] between resources and incomplete deployments. It would be great if I could run the Pulumi CLI against my SST stack.

[1]: https://github.com/pulumi/pulumi/issues/3021