atomic-server VS dioxus

Reading through https://atomicdata.dev/ seemed like a good option for notes/cms with collaboration.

Great read, wholeheartedly agree with your sentiments! We need to combine the vision of a web of linked data with the practicality of JSON. I think you’ll like Atomic Data, a project that I’ve been working on for almost three years now. It’s a modular specification that takes a strict subset of RDF to make it highly compatible with json. I’ve also written quite a bit of docs and some implementations, such as a server (written in rust) and a data browser (similar to notion), as well as a bunch of libraries.

I use sled in Atomic Server. Here's the actual sled usage.

Working on Atomic-Server, a graph database / CMS for sharing structured data and schemas. Currently, I’m working on a CRDT implementation - trying to have conflict-free event-sourced version control system. Kind of harder than I thought!

So for the past few years, I've been working on a new open specification, called Atomic Data. It takes inspiration from the semantic web, but is far more practical in its design and easier to use. Instead of only writing a spec, I also wrote a server / database, a client (browser GUI), and various libraries - all open source.

I've made a Database with a GUI, and Tauri helped me to make the desktop build. It's really promising project. It's very flexible in how you use it - I'm currently using its async runtime to run my Rust Actix server, and using the WebView to render a React app. Being able to easily create a desktop tray icon with actions is pretty cool. I'm really looking forward to Android + iOS support.

I'm currently writing an open source database + server that helps with this process (it creates subject pages, gives you a Gui, serializes to RDF and other formats), called atomic-server. I think using this is currently the fastest way to get linked data deployed to the semantic web!

I'll just take this opportunity to promote an open source, decentralised database that I've been working on, called Atomic-Server. It's fast (written in rust), features built in full text search, authorisation, dynamic forms, and it runs on low end hardware. It features a new specification called Atomic Data that combines the best of json, rdf and type safety.

I'm working on adding authentication to atomic-server, an open source graph database with dynamic, decentralized schema validation.

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI