Upgrade to latest v13.6.7 and beyond

[kkokosa]

Hi,

I wonder how difficult it would be to upgrade to the latest versions of Yjs? I'm seriously considering using Ycs in my heavily Yjs-based project with .NET backend (because of my expertise and background).

So, I'd even consider contributing with such an update. But with my current understanding of Yjs, it is really hard for me to even estimate the amount of changes and work. And what's in the end missing because of using Yjs from two-years-ago.

While I see discussion in #5 about ydotnet, I just wonder does it still make sense or not to consider updating it?

[Horusiath]

HI @kkokosa, currently ycs has not maintainers. Over the 2 years, feature-wise there were only a handful of new features added like reordering array elements and (to be released in upcoming weeks/months) ability to provide weak references between document nodes and quote ranges of elements living in another node.

That being said there's a bunch of bug fixes that probably haven't landed in the last 2 years on Ycs side. It's hard to tell how significant they are.

On the other side ydotnet is based on the common core, Yrs (Rust port of Yjs) and its C FFI bindings, which are actively maintained and developed. I'm responsible for Yrs/FFI thing, while @LSViana is working on providing the .NET bindings. Maybe he could use some of your help.

It might be a feasible idea to model ydotnet API to become ycs drop-in replacement. This way people who can limit themselves to make use of subset of features that ycs offers can use it right now, while eventually we'll get it replced by common core-backed solution.

[kkokosa]

Thank you @Horusiath for in-depth explanation.

Sounds like my personal preference would be to just update this, pure .NET-based solution. BUT obviously, this doesn't make sense. And I don't have time for doing it.

So, we should probably go the other way around - working on ydotnet and maybe, eventually, make it a drop-in replacement for ycs.

My goal is to have yjs-compatible .NET backend based on, for example, SignalR and being able to plug-in into updates so I can, for example, persist them etc.