tealr VS sycamore

working more on tealr more specifically tealr_doc_gen

Fixing some short comings in tealr that people discovered. Also, making hv_lua work with tealr and ideally start adding that fishfight.

Fantastic! Very happy to see this move forward at such a fast pace. We’re implementing scripting in Fish Fight via the tealr crate, which wraps mlua (and rlua).

Hopefully the last hand on https://github.com/lenscas/tealr for a new release. Mostly going over the documentation. Laying less emphasis on teal and more on "Hey, using this you can express a more typesafe api to lua and can actually easily document it.".

tealr, my wrapper around rlua and mlua to focus on (among other things) being better able to describe your api in the form of types: Getting it to a point to release a new version. Which is all about allowing people to document they API that they created for lua/teal. This documentation gets written to the definition files when generating them. In addition, you can also ask tealr to generate a instance.help(page:Option) method on your types. When doing this, the documentation gets made available through this function. By default it prints out "type level" documentation for this type, as well as what other pages are availalbe. When given a string, it shows the documentation for that page instead. Pages that belong to methods also automatically include the type signature.

This requires some new features in my Rust <-> Teal FFI library tealr https://github.com/lenscas/tealr which is now also close to getting a new release, with the only thing I want to do is fix how its TypedFunction work (right now, it always contains a lua function, even if it was made inside of Rust, which puts some needless limits on it).

After that it is time to finish mlua support for tealr . As well as making it better at dealing with api's like tealsql has made.

In case anyone is interested: Issue about it here https://github.com/lenscas/tealr/issues/17

Can you try removing the println! at https://github.com/lenscas/tealr/blob/cee2363a14c53b995a69efb2b4cbd84010905276/tealr_derive/src/lib.rs#L155?

Perseus is a fast frontend web development framework for Rust with built-in support for reactivity using Sycamore, server-side rendering, and much more. Sycamore is a frontend library that allows you to build interactive user interfaces with Rust. I’d say that Perseus is to Sycamore as Next.js is to React, so it’ll be helpful for you to have a fair understanding of Sycamore before jumping into using Perseus — although it’s not necessary to follow along in this article.

Now, I considered whether to spend more time fixing everything that now failed in sycamore 0.9. But there are major changes ahead which would require yet another major refactoring, to the point where I am not sure whether it would not be more of a rewrite than a refactoring, given my previous experiences with sycamore.

Sycamore.

Sycamore, Yew, or Seed if you want a full-stack solution. (Or Leptos if you want something that's faster but less mature.)

There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.

Sycamore is a reactive library for creating web apps in Rust and WebAssembly. https://github.com/sycamore-rs/sycamore

I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.

If you want to do fullstack/SPA stuff, check out Sycamore, Seed, and Yew.

If you want to do front-end SPA development, take a look at Yew, Seed, or Sycamore.

I have written a front-end (website) application in Rust that is used internally in production. I wouldn't recommend to use something like sycamore, leptos, dioxus, yew for you next puplic web-app now but i can absolutely see how this is used in the future as those libs mature.