Shared data types for building collaborative softwareProject mention: Todos: The Hard Parts | dev.to | 2021-09-15
But still, frontend development is pretty damn hard! And that makes sense. Web applications can have interfaces as complex as IDEs and data exchange layers as complex as distributed databases.
Collaboration suite, end-to-end encrypted and open-source.Project mention: CryptPad Forms: Wrangling conditional sections is a nightmare and a half. | reddit.com/r/cryptpad | 2021-10-17
Yeah I don't like how their Forms app works at all, but you should post this on their GitHub repo where they're more likely to see it: https://github.com/xwiki-labs/cryptpad/issues
Share your workspace with team members and collaborate on code in real time in AtomProject mention: Looking for pair programming coding challenges | reddit.com/r/learnprogramming | 2021-04-26
Teletype for Atom might be what you're looking for. Also, haven't used yet, but a quick Google search shows me something like this also exists.
String-wise sequence CRDT powering peer-to-peer collaborative editing in Teletype for Atom.Project mention: 5000x Faster CRDTs: An Adventure in Optimization | news.ycombinator.com | 2021-07-31
And I'm not surprised these techniques have been invented before. Realising a tree is an appropriate data structure here is a pretty obvious step if you have a mind for data structures.
To name it, I often find myself feeling defensive when people read my work and respond with a bunch of links to academic papers. Its probably totally unfair and a complete projection from my side, but I hear a voice in my head reword your comment to instead say something awful like: "Cool, but everything you did was done before. Even if they didn't make any of their work practical, usable or good they still published first and you obviously didn't do a good enough literature review if you didn't know that." And I feel an unfair defensiveness arise in me as a result that wants to find excuses to dismiss the work, even if the work might be otherwise interesting.
Its hard to compare their benchmark results because they used synthetic randomized editing traces, which always have different performance profiles than real edits for this stuff. Their own university gathered some great real world data in an earlier study. It would have been much more instructive if that data set was used here. At a glance their RAM usage looks to be about 2 orders of magnitude worse than diamond-types or yjs. And their CPU usage... ?? I can't tell because they have no tables of results. Just some hard to read charts with log scales, so you can't even really eyeball the figures. So its really hard to tell if their work ends up performance-competitive without spending a couple days getting their enterprise style java code running with a better data set. Do you think thats worth doing?
📑 Collaborative document editing using Markdown (by nextcloud)Project mention: Using the web interface throws many (hidden) 404's | reddit.com/r/NextCloud | 2021-02-01
It may very well be expected behaviour. See for instance this on Github.
Are you hiring? Post a new remote job listing for free.