It’s not a rust thing. Custom markup is usually implemented in rust frameworks using macros. If mixing macros and logic becomes a problem, we can change how the macros are implemented.

I haven't tried to the web app part but I've tried Toasty. The API seemed to be a little simpler and nicer to use than SeaORM for me. Here are a few things I liked in Toasty:

- In SQLite UUIDs are default stored as compact blobs instead of inefficient varchar/text (SeaORM)

- Timestamps were easier via jiff instead of chrono (SeaORM)

- Model structs use the actual name of the $table instead of being named like $tablemodule.(Model|ActiveModel) (SeaORM) they are just $Table. This makes writing libraries a little simpler that need to use entity struct's from two separate modules/crates otherwise you get a name collision on Model/ActiveModel and need to do alias imports.

- There's an API to fetch related data to a query similar to Django ORM. IIRC this is missing from SeaORM

- The query expression language doesn't cover as much of SQL as SeaORM but seems to be enough for most web apps.

- I didn't like how the migration system works. I would skip that part of the library

I have tried it. It feels pretty good to use, but you have to keep in mind that it's very early software. They currently break the API every other week, and it's still missing a lot of fundamental features. I have made a few basic web apps with it, and on v0.8.1 it was still missing a lot of reactivity which meant you had to use Javascript to bridge the gap.

We’re using it to build our web app (https://uncook.xyz) and while it’s a slight departure from my team’s NodeJS background it’s been pretty cool to work with

Luckily there's a lot of people who write prototype code, toy projects, and other "non-production" code that can experiment with a new project like this

Go use Java then.

I'd rather honestly than false confidence, there's something admirable about being this clear for sure

> write it in C and ask an LLM to weed out the memory bugs?

because a non-determinist chain of reasoning is not the same as a fully deterministic algorithm. Its the best tool when a deterministic system is not feasable.

If you go that way, why not write LLVM Intermediate Representation? And if you know your server arch anyway, why not write machine code?

I personally like Rust for web applications a lot because you can catch many bugs at compile time instead of during tests or runtime.

Why bother with rust when you can write it in C and ask an LLM to weed out the memory bugs?

Here is a idea, why not combine both? Have the advantage of Rust its build in checks and LLMs independent checks. Now you get both for a even more safe program.

Why bother with asking an LLM to weed out the memory bugs when you can write it in Rust?

Why bother with C when you can get an LLM to write it in Rust and not waste tokens on finding memory bugs