busan VS tui-journal

I mentioned last week that I was implementing a simple load balancer in my actor system implementation to figure out what was missing. I spent most of my time fixing some bits around message sending, serializing actor addresses, and some bugs/cleanup.

Building out my first "pattern" (load balancer) in my actor system. Partly because the project is far enough along to be able to start building fun stuff and partly so I can find more missing bits that I haven't thought about (or forgot).

Still working on mt TUI app Tui-Journal After the big release the last weekend. Currently I'm working on integrating MakeFile the CI/CD pipelines and I'm contributing to other TUI projects to get familiar with other brilliant approaches for TUI applications in rust.

Here are links for the project on GitHub and on Crates.io

I'm working on new features for my app TUI-Journal, like enabling editing the journal via external editor which could be tricky on windows platform or if the user sets his default editor to be something external like vs-code.

As I wanted to build a robust back-end for my TUI-Journal app, I knew I needed the right tool for the job, and Golang proved to be the perfect choice for web servers.

I'm excited to introduce TUI-Journal, the go-to journaling and note-taking app for those who prefer living in the terminal like me. It offers a simple and intuitive interface for managing journal entries and notes (using a combination of VIM and Emacs motions), featuring two local back-ends to store your data: Plain JSON text and a SQLite database.

I'm working on a supposably simple journal app, which I want to over-complicate to explore as much as possible from rust echo-system. My plan to have three front-ends: (TUI, Desktop, Web) and three back-ends (simple json file, Database and micro-service). Still though with the very first stage (TUI front-end, with Json Backend)