‹ BackHN Continuity

Thread

Topcoat is pushing the boundary of server applications with Rust

113 points · 100 comments · sagacity

  1. jdw64 · · focus · HN ↗
    Has anyone here tried it?
    1. bickfordb · · focus · HN ↗
      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

      1. carllerche · · focus · HN ↗
        Do you have feedback on what you don’t like re: the migration system? It is inspired by drizzle. Is it something we missed or just not a fan of that style entirely?
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.