this repo has no description
Why
+14
-10
+14
-10
WHY.md
+14
-10
WHY.md
···
3
3
> This file aims to explain my choices. Not that I need to explain myself
4
4
> but hey, we all feel accountable for our stupid actions sometimes.
5
5
6
-
## The `rsffi` Rust NIF library
6
+
## The 25 branch
7
7
8
-
I am just very attached to the love of my life Rust. And I think
9
-
the Rust way of doing things might come in handy somewhere down the road.
10
-
Plus, on JavaScript, FFI'ing is fairly easy, I almost write more JS/TS in my
11
-
life than Rust and Gleam...
12
-
Erlang on the other hand is kind of a scary thing. Rust is comfy! 🥰
8
+
Few days after the Rust 2024 edition release, having new experiences with gleam Lustre and a really messy repository...
9
+
Three great reasons for a clean slate.
10
+
Git branch 25 is yet another restart for me writing on Lumina. With past experiences and a clear vision, `master` does a good job, so this one will do even better.
13
11
14
-
### Markdown to HTML rendering in Rust instead of natively in Gleam
12
+
### Choices made
15
13
16
-
I think it's a good idea to have a Rust NIF for rendering markdown to HTML.
17
-
I've had it work with `kirala` (Gleam), but I think it's a good idea to have
18
-
the kind of control over it that I had in the pure Rust version.
14
+
- **Gleam** as the main language on frontend.
15
+
Not having multiple language branches about this.
16
+
- **TailwindCSS** as the main CSS framework.
17
+
- **Lustre** for building the UI.
18
+
- **Rust** as the main language on backend.
19
+
- More specifically, the `axum` library instead of `actix-web`.
20
+
- Rust 2024 edition from the start.
21
+
- **PostgreSQL** as the main database. **SQLite** for testing.
22
+
- **WebSockets** for real-time communication between the client and the server.
19
23
20
24
## The `gleam` language
21
25