yjs VS Paste JSON as Code • quicktype

One idea is just to use fewer random bits in peerIDs. Yjs (https://docs.yjs.dev/) gets away with just 32 random bits. If you compromise and use 64 random bits, then even a very popular doc with 1 million lifetime peerIDs will have a < 10^-7 lifetime probability of collision.

I've seen it come up often in collaborative text editors.

Also see: https://github.com/yjs/yjs

You are absolutely right that XML is better for document structures.

My current theory is that Yjs [0] is the new JSON+XML. It gives you both JSON and XML types in one nested structure, all with conflict free merging via incremental updates.

Also, you note the issue with XML and overlapping inline markup. Yjs has an answer for that with its text type, you can apply attributes (for styling or anything else) via arbatary ranges. They can overlap.

Obviously I'm being a little hypabolic suggesting it will replace JSON, the beauty of JSON is is simplicity, but for many systems building on Yjs or similar CRDT based serialisation systems is the future.

https://github.com/yjs/yjs/

Note: https://github.com/yjs/yjs for collaborative "document edition, and user cursors"; has WebRTC, web socket, matrix.org backend

CCP needs to revamp proto anyway, due to recent exploits... practically, nothing really prevents 'em from using some sort of CRDT's to make the state of the sig view eventually consistent (yjs lib, if we're speaking frontendian).

Yjs framework: Because it is a CRDT implementation which provides collaborative editing and offline-first capability.

No problem. The database CRUD features are just helpers as an abstraction on top of yjs: https://docs.yjs.dev/. Eweser adds schemas in the form of typescript types to make using it simpler, more structured, and interoperability easier.

Quicktype automates the generation of code from JSON data. It's a real timesaver when dealing with complex JSON structures in your applications.

Nice! JSON schemas are really useful, we use them a lot for code generation. Another library that does this for multiple languages is https://quicktype.io/ . It's great, but not so actively developed.

Quicktype is a speedy way to transform JSON data into well-structured, type-safe code in any programming language. Can help simplify the process of generating models and serializers from JSON, schema, or GraphQL—for secure, efficient data handling. 6-20PM finds it a "Godsend to convert JSON into data structures in any language."

Good candidate modules for these initial conversions are utility functions and code related to external APIs or specifications. It is possible to automatically generate TypeScript type definitions from Swagger contracts, GraphQL or JSON schemas to be included in your project. as well as you can use website called https://quicktype.io/ to generate types and interfaces in order to user them in your tsx or ts file.

Using Codable structs is better than dictionaries. Paste the JSON into https://quicktype.io/ and it will create the structs for you.

May be quicktype.io?

Check out quicktype.io. You can paste in your JSON and it will build your model for you. There's even an option for creating constructors. And you can choose your programming language. I usually spend some time cleaning it up a bit. It's not the perfect solution and I don't use it all the time, but it sure saves time for complicated models.

Hello. I used quicktype.io to try and implement an api in my code.