@yewstack/maintainers
Hi everyone, who maintains the Yew framework. You've all added awesome improvements :rocket:
It's an important issue to talk about providing either backward compatibility or easy portability.
The story:
I've released sources the biggest Yew App I ever made: https://github.com/rillrate/rillrate/tree/trunk/pkg-dashboard
RillRate is the real-time UI library that embeds a live and fully customizable web dashboard to an app.
The idea of the project is to reduce UI development costs as much as possible. The frontend part is fully created using the Yew framework.
I originally created the Yew framework to make a specific dashboard for trading purposes but found since I use the same codebase I can make even more - the dashboard that can be adopted to any project and, for example, can render live charts like BI, or live video to make monitoring app for broadcasting needs.
Compatibility:
Today I have a massive codebase that represents an average active user of the Yew framework. I think we can use rillrate as the reference project to estimate how radical changes can affect users of the Yew framework.
Ideally, with the new changes, we will be able to maintain either backward compatibility or easy porting, and also make sure that everything works just as reliably. We can say that this issue is the question: how to make Yew prod ready? I already used it a lot and I can say the Yew is ready to use in a serious project. The remained thing is to add a process of backward compatibility checking.
My project can be a good tool to achieve it. At first, I'm ready to adapt it to the radical, but important changes of the Yew framework. The second reason is RillRate is a big app and it uses some core ideas that I consider important in Yew like agents.
Suggestion:
I think it will be good if you can check my sources to see how I use the Yew framework and to think are there changes that I should try to use in the project first to check I can port it to the upcoming Yew version. My sources are not very tidy, but that's better because they look more like an ordinary work project.
If you will have any questions about how to build and try rillrate, feel free to ask :handshake: The shortest way to try it is to run do/try script and connect to localhost:6361 with the browser.
therustmonk
commented
2 years ago
@yewstack/maintainers Hi everyone, who maintains the Yew framework. You've all added awesome improvements :rocket: It's an important issue to talk about providing either backward compatibility or easy portability.
The story:
I've released sources the biggest Yew App I ever made: https://github.com/rillrate/rillrate/tree/trunk/pkg-dashboard RillRate is the real-time UI library that embeds a live and fully customizable web dashboard to an app. The idea of the project is to reduce UI development costs as much as possible. The frontend part is fully created using the Yew framework.
I originally created the Yew framework to make a specific dashboard for trading purposes but found since I use the same codebase I can make even more - the dashboard that can be adopted to any project and, for example, can render live charts like BI, or live video to make monitoring app for broadcasting needs.
Compatibility:
Today I have a massive codebase that represents an average active user of the Yew framework. I think we can use rillrate as the reference project to estimate how radical changes can affect users of the Yew framework.
Ideally, with the new changes, we will be able to maintain either backward compatibility or easy porting, and also make sure that everything works just as reliably. We can say that this issue is the question: how to make Yew prod ready? I already used it a lot and I can say the Yew is ready to use in a serious project. The remained thing is to add a process of backward compatibility checking.
My project can be a good tool to achieve it. At first, I'm ready to adapt it to the radical, but important changes of the Yew framework. The second reason is RillRate is a big app and it uses some core ideas that I consider important in Yew like agents.
Suggestion:
I think it will be good if you can check my sources to see how I use the Yew framework and to think are there changes that I should try to use in the project first to check I can port it to the upcoming Yew version. My sources are not very tidy, but that's better because they look more like an ordinary work project.
If you will have any questions about how to build and try rillrate, feel free to ask :handshake: The shortest way to try it is to run
do/tryscript and connect tolocalhost:6361with the browser.Hugged everyone and thank you! :hugs: