Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Automerge: a new foundation for collaboration software [video]

youtube.com

Post reply on HN
Print view View original

21–30 of 33 posts

Re: Automerge: a new foundation for collaboration software [video]

#21

Post by samwillis »

melony wrote: post #20
hanspagel wrote: post #10

Earlier quoted context omitted.

I’m a bit biased, but I think 2022 will be the year of Y.js. What we’ve done or set up for the next year: * The Y-Collective to fund more and more related projects, like slate-yjs: https://opencollective.com/y-collective * The Hocuspocus backend you've discovered, which will become public in April or so * A cloud offering we’re bootstrapping to hopefully get even more money into the ecosystem * Y.js core support for…

How do the performance and features of Yjs compare to Automerge?

https://github.com/dmonad/crdt-benchmarks

Not completely up to date I believe but it shows that Yjs significantly outperforms automerge.

Re: Automerge: a new foundation for collaboration software [video]

#22

Post by samwillis »

hanspagel wrote: post #10
adeptima wrote: post #8

Main takeaways from toying with both Yjs and Automerge: 1. Extremely difficult to build backend in other programming languages than Nodejs Rust implementations https://github.com/automerge/automerge-rs https://github.com/yjs/y-crdt You will cry looking at source code https://github.com/yjs/y-crdt/blob/main/yffi/src/lib.rs C-binding, FFI, etc 2. Both communities are great. Before committing recommend to go through iss…

I’m a bit biased, but I think 2022 will be the year of Y.js. What we’ve done or set up for the next year: * The Y-Collective to fund more and more related projects, like slate-yjs: https://opencollective.com/y-collective * The Hocuspocus backend you've discovered, which will become public in April or so * A cloud offering we’re bootstrapping to hopefully get even more money into the ecosystem * Y.js core support for…

I agree with Hans, we are going to see an explosion of collaborative tools next year. And Yjs is best placed to enable them.

The ecosystem around Yjs with the Y-collective is so impressive.

Re: Automerge: a new foundation for collaboration software [video]

#24

Post by outside1234 »

mlajtos wrote: post #7
yuchi wrote: post #3

I really love Automerge, had some fun in the last months with building some small experiment. Some major problem I see currently is the lacking ecosystem. I had to roll my own persistence implementation on top of IndexedDB and I still haven’t touched the backend synchronization part. I would love to see Y.js or Automerge more throughly supported by a wider ecosystem of elements that make building a production app eas…

Y.js has pretty good integrations with editors. What would you wanted to see in particular? BTW Rust port of Y.js might be start of something rather wild. :)

Are you looking for https://github.com/rust-crdt/rust-crdt and https://github.com/libp2p/rust-libp2p?

Re: Automerge: a new foundation for collaboration software [video]

#25

Post by outside1234 »

adeptima wrote: post #8

Main takeaways from toying with both Yjs and Automerge: 1. Extremely difficult to build backend in other programming languages than Nodejs Rust implementations https://github.com/automerge/automerge-rs https://github.com/yjs/y-crdt You will cry looking at source code https://github.com/yjs/y-crdt/blob/main/yffi/src/lib.rs C-binding, FFI, etc 2. Both communities are great. Before committing recommend to go through iss…

Wow - you weren't kidding - the rust port is total trash. What is even going on there?

Re: Automerge: a new foundation for collaboration software [video]

#26

Post by Horusiath »

outside1234 wrote: post #25
adeptima wrote: post #8

Main takeaways from toying with both Yjs and Automerge: 1. Extremely difficult to build backend in other programming languages than Nodejs Rust implementations https://github.com/automerge/automerge-rs https://github.com/yjs/y-crdt You will cry looking at source code https://github.com/yjs/y-crdt/blob/main/yffi/src/lib.rs C-binding, FFI, etc 2. Both communities are great. Before committing recommend to go through iss…

Wow - you weren't kidding - the rust port is total trash. What is even going on there?

I'm one of the maintainers of this project: we're happy to hear some constructive feedback and proposals for improvements, so please don't hesitate to speak your mind at github issues: https://github.com/yjs/y-crdt/issues .

The internals are still very hot and in a state of flux, as we 1st decided to go with porting the Yjs, then leave cleaning and optimizations for 2nd step after we have something, that's compatible with existing Yjs behavior.

Re: Automerge: a new foundation for collaboration software [video]

#27

Post by adeptima »

hanspagel wrote: post #10
adeptima wrote: post #8

Main takeaways from toying with both Yjs and Automerge: 1. Extremely difficult to build backend in other programming languages than Nodejs Rust implementations https://github.com/automerge/automerge-rs https://github.com/yjs/y-crdt You will cry looking at source code https://github.com/yjs/y-crdt/blob/main/yffi/src/lib.rs C-binding, FFI, etc 2. Both communities are great. Before committing recommend to go through iss…

I’m a bit biased, but I think 2022 will be the year of Y.js. What we’ve done or set up for the next year: * The Y-Collective to fund more and more related projects, like slate-yjs: https://opencollective.com/y-collective * The Hocuspocus backend you've discovered, which will become public in April or so * A cloud offering we’re bootstrapping to hopefully get even more money into the ecosystem * Y.js core support for…

I’m biased into Yjs too and bet on it. Yjs Rust port and other simply not ready for the prime and won’t be for a while. Bindings and unsafe Rust is the road to hell

Re: Automerge: a new foundation for collaboration software [video]

#28

Post by adeptima »

melony wrote: post #20
hanspagel wrote: post #10

Earlier quoted context omitted.

I’m a bit biased, but I think 2022 will be the year of Y.js. What we’ve done or set up for the next year: * The Y-Collective to fund more and more related projects, like slate-yjs: https://opencollective.com/y-collective * The Hocuspocus backend you've discovered, which will become public in April or so * A cloud offering we’re bootstrapping to hopefully get even more money into the ecosystem * Y.js core support for…

How do the performance and features of Yjs compare to Automerge?

It will depend on your use cases. Better to check updated roadmaps too. The final gap won’t be too big IMHO

Re: Automerge: a new foundation for collaboration software [video]

#29

Post by caladin »

adeptima wrote: post #8

Main takeaways from toying with both Yjs and Automerge: 1. Extremely difficult to build backend in other programming languages than Nodejs Rust implementations https://github.com/automerge/automerge-rs https://github.com/yjs/y-crdt You will cry looking at source code https://github.com/yjs/y-crdt/blob/main/yffi/src/lib.rs C-binding, FFI, etc 2. Both communities are great. Before committing recommend to go through iss…

> You will cry looking at source code https://github.com/yjs/y-crdt/blob/main/yffi/src/lib.rs

Am I missing something? You linked a file that is inherently going to be "un-Rusty" because it's meant to be an FFI shim for _non-Rust_ languages to use through a common C API that this file exposes.

Post reply on HN