High level summary article

More detailed article

In June, the Python steering council announced that it was pausing work on the JIT in CPython's main branch until there was an accepted Python Enhancement Proposal (PEP) that addressed concerns about maintenance, compatibility, and set clear success metrics as well as a timeline for completion. [....] After months of discussion, the JIT maintainers have withdrawn the PEP. For now, it appears that development on the once-promising project has come to an end

Hey r/programming,

Weekend-project-turned-obsession here. I wanted to see how far you

could push "serverless" – so I made a cryptocurrency where the entire

network is just open browser tabs.

Stack:

- WebRTC data channels for peer mesh (with deterministic mutual-dial

resolution so two nodes never keep duplicate connections)

- MQTT-over-WebSocket as a zero-config gossip fallback (every node

subscribes to the same public broker topics)

- IndexedDB for chain storage, snapshots every 1,000 blocks

- A Web Worker miner hard-capped at 70k H/s regardless of hardware

- secp256k1 signatures, v2 scheme binds chain-id to prevent replay

across networks

The interesting problem was sybil resistance without a central

authority. Solution: a ~65k-hash PoW challenge after every handshake.

Flooding the network with fake peers costs real CPU per connection.

Another fun constraint: one miner per browser (Web Locks API) and a

consensus-enforced cooldown so the same address can't mine two

consecutive blocks.

It's an experiment, MIT-licensed, no token sale, no investors. I'd

love to hear how you'd break it or what architectural choices you'd

question.

Repo: [link]

README has the full threat model if you want to dig in.

I have followed Scott for some time because of his contributions to the fsharp learning community. He's website fsharpforfunandprofit.com is one of the best programming article websites. This talk especially is very good. I think Scott is very good at breaking down complex topics to make them seem approachable.

There's been a big resurgence lately in automating and interacting with sites programmatically. I've been arguing for a few years that every front-end should be embeddable as a component and have its own client side interface/api. This article is designed to show one way to do that!

I host a podcast for senior engineers and recently had Carson Gross, creator of HTMX, on as a guest. We covered how REST was originally defined, how the industry ended up calling JSON over HTTP "REST", and why he thinks returning HTML from the server is closer to the original idea.

We also got into HTMX 4, when you actually do need a SPA, and how AI changes the tradeoff between simple and clever code.

Full episode: https://youtu.be/9xs0oZN2rs4

4' video on the history of REST: https://www.youtube.com/watch?v=DbNvpiJ9gTs

The “Bug Hunt” blog post pattern is the programming world’s equivalent of a detective story. It has a theme, a main plot, side plots, a protagonist (you), an antagonist (usually also you, having introduced the bug two weeks ago in the first place). It’s captivating, keeps readers in suspense, and ends with a satisfying plot twist, or a tactical cliffhanger. And the best part is…it’s even more fun to write than to read!