5 ms·
I didn't expect to see this here yet. We opened up the repo because we ran out of private CI usage. A blog post is coming next week :). Happy to answer question
by carllerche 2mo ago
I didn't expect to see this here yet. We opened up the repo because we ran out of private CI usage. A blog post is coming next week :). Happy to answer questions here though.
One thing to keep in mind, the main reason for Topcoat to exist is that many organizations are already using Rust for infrastructure-level or performance sensitive reasons and often just want to build a web app using the programming language they already use.
- jonahx 2mo agoI'll say that first code snippet is a fantastic TLDR.
- swaptr 2mo agoGreat initiative from the folks at tokio. How does it aim to be different from loco.rs https://github.com/loco-rs/loco https://github.com/loco-rs/loco?
- carllerche 2mo agoBoth Loco and Topcoat aims to be "batteries included" but that means very different things to each project. Topcoat aims to make it easy to build reactive apps without writing any browser JS (or Rust). It uses a similar strategy to Hotwire, HTMX, Datastar, ... It also will default to using the Toasty ORM (though topcoat is modular so you a swap it out). Topcoat is very young and there is a lot more to build.
- dxxvi 2mo agoThe last loco.rs release was 1 year ago. I wonder what happens with it.