Comment by jbandela1 | Hacker News Reader

Comment by jbandela1 | Hacker News Reader

Kudos to the author for making this framework.

I am using this for my personal project: https://www.biblemaze.com which is a Bible trivia game.

Here are some things I like about Seed:

1. The Elm architecture seems to flow nicely in Rust.

2. The way of defining the elements on the page is more Rust like rather than html like. I initially tried Yew which is another similar framework, but since I am a more backend developer, I found writing in a more Rust style more comfortable than writing in a more html-like dsl. Other with different experiences may be more comfortable with more html-like syntax.

3. Very easy to perform REST API calls. I am using Actix for the backend, and I have a shared library that declares the types which both the backend and frontend use. This is one big advantage for using Rust for both backend and frontend, in that you never have to worry about your types getting out of sync.

4. In general as to why Rust for the front end, apart for being able to share types, for more complex algorithms, for me, having a compiled language with an emphasis on safety and that tries to ensure correctness as much as compile time (and especially pattern matching) makes writing complex code more enjoyable for me.

5. Excellent documentation on the Seed website. There are lots of examples and walkthroughs of basics as well as examples of how to do stuff like integrate with Javascript libraries.

Anyway, thanks again to the authors for making and supporting such an awesome library.

- This is one big advantage for using Rust for both backend and frontend, in that you never have to worry about your types getting out of sync.

One thing to be aware of here, you may have users with stale clients after deploying an update to the server. e.g. picture someone who leaves a tab open for a week and then comes back to it and interacts with your app some more without refreshing.

Text based serializations will tend to be more forgiving of changes in the RPC schema (in the sense of erroring out when required fields are missing), while more compact serializations are more likely to incorrectly decode a message when they should fail.

The quick and dirty solution to this is to have a client response handler that checks for a header set on responses to ensure its a compatible version, then prompt a page refresh if not.

At this point, I feel like this is the most consistent way. There are notable web apps that do this. There are plenty of good reasons for this, including caching and service workers.

It feels dirty because you’re not handling these issues silently. But it’s explicit, clear and it enables a consistent and performant experience.

I wish more people thought this way about computing.

An equally-quick but not-at-all-dirty version of this is to use the Accept header and do content negotiation. There is a solution to this exact problem in the HTTP spec.

One thing you can do in the shared library is to have a version number constant that is always passed in the rpc. That way if the client is stale, it can easily be detected, and you only have to change 1 place when you update the shared structs.

> This is one big advantage for using Rust for both backend and frontend, in that you never have to worry about your types getting out of sync.

Of course this is a hack compared to Rust BE and FE, but I’ve been finding that auto-generating Typescript type definitions from a Pydantic (Python) API works pretty nicely. Of course, what’s going on under the hood there is all a lot uglier than a beautiful modern compiler with an expressive modern type system, but it’s cool that it works.

When I learned of Pydantic, my first thought was "This is a lot like Serde in Rust".

Very fun! Is it possible to remove the '-' symbols once a new path has begun? They were blocking previous paths, which also may be the point.

Thank you. It seems this is in reference to my game. If so, please contact me on my email (in my profile) so we can discuss further in detail.

It's not a big deal, thanks.

Reply on news.ycombinator.com