Editor-Box VS vox

I have an idea to replace posting on Facebook/Twitter where you sell your and your readers privacy with posting on your own blog.

To achieve this, blogging platforms (I am aiming to WordPress right now) must remove the obstacles in user experience: people stopped blogging and switched to Facebook because posting on FB has more profits: it is easier (just visit front page of FB instead of logging to wp-admin and doing next steps), you have all content in one place (FB wall shows your posts and your friends posts etc) and tickles your ego (you immediately get likes and shares while on your blog barely anyone comment your post)

I am working on plugins and tools to remove this distance: front-end editor box for your blog ( https://github.com/kkarpieszuk/Editor-Box ), plugin to subscribe to other blogs and see their content as part of your blog, plugin to give local likes for posts, broadcast your content to other blogs...

Everyone will have kind of their own Facebook on their own WordPress blog.

I am WP plugin developer as my main job but all above I am doing in my free time as a hobby.

If anyone is interested in collaborating to make the network a bit less occupied by big techs, please reach me here https://github.com/kkarpieszuk/Editor-Box (create an issue or pull request if you have an idea how to extend this plugin) or find my email address at https://muzungu.pl/o-mnie/ (in Polish but you will easily find the address)

I chase the same goal with Vox, although it is written in D.

Just somewhere to point me, because while I do understand SSA a bit though I can't seem to make progress learning about it (dont know where from). I found https://github.com/MrSmith33/vox/blob/master/internals.md which kinda feeds me information but probably not enough.

Looking for contributors to Vox programming language/compiler: Statically typed, compiled and embeddable language, primarily focused on gamedev. It uses custom backend to keep low compile-times and small size. Written in D language.

https://github.com/MrSmith33/vox

Because it is easier to have a free-list in a dedicated array arena, so you could reuse memory when you free it (and you need to grow arrays when you fill them). I was lazy and did 13 array arenas each dedicated to allocating fixed size chunks, from 16 bytes to 64k bytes. Bigger sizes currently go to malloc/free. And I restrict arrays to PoT sizes, so they only request PoT sized chunks from array arenas.

I use this approach in Vox compiler. Everything is stored in arenas including AST nodes and IR. I'm in the process of documenting the design, but I added a bit of description on memory management and IR storage

Tip: Should probably use the Github permalink https://github.com/MrSmith33/vox/blob/35ec440d0c9a475cd4add6093d122cd249b03be9/source/be/reg_alloc/linear_scan.d#L891-L918 so later readers do not go to some random line after you change that file :)

Here is a CI build