atomic-server VS awesome-wasm-langs

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.

Cross-language support for over 30 programming languages for eBPF user space programs

wot

Just about every language can compile or transpile to WASM:

https://github.com/appcypher/awesome-wasm-langs

There are also curated lists of languages that compile down to Wasm available on Github, so there is a ton of opportunity to choose your own adventure.

My current plans are to investigate TinyGo / C# NativeAOT-LLVM / other languages that can compile to Wasm once our host side stabilises a little bit (lots of churn right now!)

Yeah, it's pretty cool. Here's a nice list of all the repositories and stuff like that

It’s planned to use WASM, which would allow to use basically any language you’d want (ok, any lang having a WASM compiler or VM), including Lua.

While waiting for placement at Andela, I started something. I wanted to create a community of developers who had already worked on WebAssembly projects in the past. A bit of a back story is in order now. During my exploratory phase before I settled for web development, Web Assembly was announced. So on a whim, I created a Repo to keep track of languages that compile to web assembly. The repo ended up getting over three thousand stars. I honestly didn’t expect it to blow up as much as it did, but it did. That feat fueled my interest in Web Assembly. As I was saying, I wanted to gather Web Assembly developers together for a purpose - to create a common web assembly runtime, a canonical runtime. My attempt at community building didn’t go so well. I sent a couple of emails, and DMs to no avail, or so I thought. It was during this time that Syrus Akbary reached out to me, he pitched the idea he had to build an awesome web assembly runtime, Wasmer, and that he would want me to be involved. He was really excited, and so was I. The only thing was that he said he had to lay down some of the groundwork first. So he worked on it for about a month. Now that I think about it, I should have stuck to him while he laid down the work because when he showed me the progress he had made, I was awe-stricken, but also disadvantaged. A lot of work had been done. Here we were trying to build the web assembly runtime that would take the world by storm, but my knowledge of Rust was meager. Keeping up was hard. Eventually, I had to leave the project, he was incorporating Wasmer as a company, so relocation was being discussed but I wasn’t interested in going to the US. But I think the major deciding factor for me was that I didn’t really align with the management of the project.