@mntruell The chat input needs some love:
1. Use monospace in code blocks
2. Auto indent in code blocks
3. Bug: Copying "\ntext" pastes as "\n\ntext"
4. More autocomplete please
@guillaume_slls@ctnicholasdev@liveblocks The code is here
https://t.co/CbVMnDlCS4
A demo app (though not using the above implementation)
https://t.co/cJtiP5SGc2
One thing I like about CRDT is that we don't need to rebase the undo stack.
On the other side, OT doesn't require a special data structure.
@ctnicholasdev@liveblocks It's very challenging to do it with CRDT.
I wrote an OT lib (though not finished yet) that supports moving nodes to different branches. Also supports custom validation, important for enforcing constraints, e.g. DAG.
If you're interested, we can talk.
@hamiltonulmer I switched @RustExplorer editor from Monaco to codemirror
It gives a lot of customization, which also means a lot more code to write.
Plus it supports mobile devices.
@taofikmuhammad Sudah dapat solusi untuk bayar Google Cloud mas?
Saya lagi mengalami kendala yg sama. Saya pakai Hetzner. Sebelum nya bayar pakai BN* debit online bisa, tapi sejak bulan lalu ditolak.
@ctnicholasdev@liveblocks Hey Chris, why the @liveblocks team decided to use CRDT over OT?
And does liveblocks mutate user's selection when the doc is mutated locally/remote?
I'm building a data tool with OT, would love to hear opinions from the CRDT side.
There's no "react" in React Server Component.
Should we call it "Not React Component" instead?
Some alternatives:
- Static Component
- Dead Component
- Non-interactive Component
Current explanation on @nextjs doc
Server Component: ... rendered on the server ... then progressively *enhanced* in the browser.
Client Component: ... prerendered on the server and *hydrated* on the client.