dali VS beubo

Tangentially related, I've written a barebones assembler for Android .apk files once (strictly speaking, the assembler is for .dex files, but it also comes with a set of tools to package and sign .apk files). It's written mainly in Nim and provides enough primitives to allow creating Java "stubs" for native .so libraries, so that .apk-s can be built in Nim WITHOUT JDK AT ALL. The Android NDK is still kinda needed/useful, though IIRC mainly for access to adb, and especially adb logcat (which you'll need A LOT for debugging if you try to use this contraption).

I'd love to One Day™ Rewrite It In Rust.

The .dex assembler itself is at: https://github.com/akavel/dali — you may like to check out the tests at: https://github.com/akavel/dali/tree/master/tests to see how using it looks like.

An example project with a simple .apk written purely in Nim (NO JDK) is at: https://github.com/akavel/hellomello/tree/flappy (unfortunately, given Nim's poor packaging story, it's most probably already bitrotten to the extent that it can't be quickly and easily built & used out of the box). I recorded a presentation about this for an online Nim conference — see: https://www.youtube.com/watch?v=wr9X5NCwPlI&list=PLxLdEZg8DR...

https://github.com/akavel/dali was one (a fully hand-written assembler for Android .apk files); I managed to write a rudimentary flappy-bird-like prototype in it and did a presentation: https://www.youtube.com/watch?v=wr9X5NCwPlI&list=PLxLdEZg8DR... but on shelf now, didn't get much attention, and I don't feel bad about it. Had some roadblocks, but managed to overcome them, and I'm honestly surprised how the core effort was basically easy to implement and how the formats were open and relatively simple. (The main real issues I had were that debugging via adb logs was tiresome when something was not working.) What was funny about this project was that I started it with basically a thought of: "there will be probably some annoying roadblock at some point that will make it unviable to continue; I accept that and will be ok with stopping once I stumble upon it; but I don't see one clearly from the start [I did some quick initial research how the formats & the bytecode look and they seemed rather simple], and I'm really curious how far I can get if I decide to not think about this possible roadblock". Turns out I was able to get all the way to the end :D

I'm working on https://github.com/uberswe/beubo - It's a CMS similar to Wordpress but written in Go. It's still very early and it has a lot of bugs but what will make it powerful is plugins and themes. Performance is the biggest difference between Wordpress, plugins will most likely use RPC/gRPC which means they could be written in any language.

I'm mostly writing it for use with my own projects like https://tournify.io but it would be awesome if a few others found it useful too. It's a nice way for me to practice my Go programming skills.

A CMS written in Go. It’s still very early and it has the basics of user creation, multiple domain support, themes and user management by default. What will make it really powerful is plugins.

Plugins are still being developed and currently use the go plugin package which is really good for performance but can be bad for security and compatibility with versions and operating systems. I plan to either move over to using RPC instead or supporting both options.

Everything is available on GitHub under the MIT License.

https://github.com/uberswe/beubo