Wazako

Alternatively, a much simpler CRDT solution is to flatten our tree and build a LWW underneath it. This makes it easy to debug, save, and delete the history. { “id:1”: { “parent_id”: “root”, “type”: “p” }, “id:2”: { “parent_id”: “id:1”, “type”: “text”, “content”: “text”, "position": 1 } }

Or internally: [ [HLC, “id:2”, ‘parent_id’, “id:1”], [HLC, “id:2”, ‘type’, “text”], ... ]

Merging is easy, and allows for atomic modifications without rebuilding the entire tree, as well as easy conflict resolution. We add the HLC (clock, peer id). If the time difference between the two clocks is significant, we create a new field [HLC, id, “conflict:” + key, old_value]

What is absurd is finding yourself paying 30% on every digital item purchased on a smartphone app. It would never even occur to us that Microsoft takes a 30% margin on Steam, yet that is what happens on webtoon apps.

Slow llm generation. A progressive display of a progressive json is mandatory.

Yet deepseek has shown that more dialogue increases quality. Increasing speed is therefore important if you need thinking models.

It was designed by cloduflare for serverless use. There's no dependency on node, as cloudflare is based on web standards, so it was designed around warper for browser-native js modules (Request, crypto, ... hence the low dependency), which is why it integrates well with bun and deno.

It's different with solid-js, which is more of a library than a real framework.

The solid-js surface is relatively small, the jsx / css is identical to the native, the Hook simply builds the DOM once. solid-js therefore brings above all a createSignal that adds an observer where it is called in the DOM to directly update the DOM accordingly.

You might think of solid-js more as a signal primitive than a real framework.

This reminds me of crunchyroll, the anime website, which uses local utc us with fixed times for episode releases. This creates confusion in the rest of the world, because for 2 weeks, there's a time difference until daylight saving time changes in the US.

What's wrong with making Promise.all ?

try {

  const [user, session] = await Promise.all([
    getUser(userId),
    getSession(sessionId)
  ])

} catch (err) { … }

But when you look at the disaster that was c++ for cloudflare, and the switch to rust.

This is precisely the argument given against rust for video games: too much typing induced by memory safe, which is too restrictive.

Is there any use if your c code works, the advantage of rust over wasm is the easy-to-use packages (which is a pain in c++), and the ease with which you can make a wasm project with wasm-pack that generates the wasm, js and ts interface.

There really are a lot of libraries that support wasm, it's even a problematic point raised in the article on bevy, with wasm support (so webgl) limiting the api.

Use Rust if crashes or memory bugs are not an option. For everything wasm, Rust is much more pleasant with good libraries than the competition.

meta has the Quest. It's not so bad that they're looking to create an LPU for their headset to offer local play.

It's one thing to be able to track a transaction, but it's a real problem that a name exchange is mandatory for micropayments.

I don't know if I'm the only one, but I can't see myself giving my identity for 10c to buy blog articles.

Especially since first and last names are a powerful tracking tool that's not as easy to change as your IP address.

How do you centralize without having a government requiring KYC?

By this I mean that Microsoft had the positioning of an iPhone in a not-so-great version. Where as Android relied on the "Open source" and free side for manufacturers to adapt to their phones, even if Google's services remained proprietary.

Can we really talk about timing, when it's above all a problem of a product that didn't fit the market?

It's not a question of timing, but of Microsoft's brand image (Internet Explorer) and the fact that Android was already open source.