yew-beyond-hello-world
Soccer
yew-beyond-hello-world | Soccer | |
---|---|---|
1 | 3 | |
18 | 0 | |
- | - | |
10.0 | 9.5 | |
almost 2 years ago | 5 months ago | |
Rust | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
yew-beyond-hello-world
-
Htmx, WebAssembly, Rust, ServiceWorker Proof of Concept
There is a nice Rust-only web framework already - yew.
One of the examples https://github.com/security-union/yew-beyond-hello-world
Soccer
-
Ask HN: What apps have you created for your own use?
A soccer tracking app for who is playing and who isn't and what positions.[^1] A weight tracking application.[^2] A time tracker for how many hours my daughter was driving.[^3] An app to help my wife randomly pick meals for the upcoming week.[^4] Logic (CLI) to organize finances with hledger. A back end to work with all my offline-first web apps (the first 3 apps).[^5]
[^1]: https://github.com/jon49/Soccer
-
HTML First – Six principles for building simple, maintainable, web software
I've successfully used this pattern (HTMX hypermedia style) to create an offline-first web app SPA[^1]. One of the pages is pretty dynamic and I wasn't sure if I would need a traditional front end library to work with it. But, nope, hypermedia to the win, it worked fine without a front end framework.
To build it I used my own library called HTMF[^2]. I started out using mpa-enhancer[^3] but found that that pattern is a little to janky sometimes. I think reloading a page every time on every interaction uses too many resources for a browser especially when you use a phone that doesn't have as much power as a laptop.
But overall I find the pattern very easy to use and keeps the complexity down.
I think some of the issues with traditional SPAs is that they have a lot of state and state is nonlinear in complexity. But using templating systems makes the complexity more linear in nature.
Also, I find libraries like React to be overly complex for what it does, see above. The way React works is just odd and counter intuitive. All for problems that are easy to solve. I do think there are places for a React-like library is needed but those are for websites that are inherently highly state-based. But most websites aren't state-based even ones that appear to be state-based at first.
The websites I work on are usually just forms and forms are pretty powerful and can get you a long ways before you need to go outside of that paradigm.
[^1]: https://github.com/jon49/Soccer
[^2]: https://github.com/jon49/htmf
[^3]: https://github.com/jon49/mpa-enhancer
-
Htmx, WebAssembly, Rust, ServiceWorker Proof of Concept
I've created an offline-first web app which is based on service workers. I've created another one that could be pushed to the back end (like on Node.js) that would be just a straight MPA app. I guess both of them could be pushed to the back end if needed. Since I just use them for myself I don't worry about them not working without JS enabled. But I created HTMF, similar to HTMX but made to be a progressive enhancement from the get-go.
https://github.com/jon49/Soccer \
What are some alternatives?
wasm-service - HTMX, WebAssembly, Rust, ServiceWorkers
submillisecond - A lunatic web framework
htmf - A minimalist partial html swapping library similar to HTMX and other libraries which create an MPA app and enhances it with a focus on HTML forms.
MealPlanner - A Meal Planner to figure out what we are going to eat each week. Written with Razor Pages and HTMF. https://meals.jnyman.com/
- - Hyphen - An elegant custom element base class
WeightTracker - Back end for saving data for weight tracker.
axum-browser