css-scope-inline
htmf
| css-scope-inline | htmf | |
|---|---|---|
| 9 | 4 | |
| 647 | 24 | |
| 1.2% | - | |
| 6.2 | 4.7 | |
| 9 months ago | 2 months ago | |
| HTML | JavaScript | |
| 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.
css-scope-inline
- Tailwind V4 Is Finally Out
- How do you do, fellow web developers? A growing disconnect
-
Inline Scope for CSS
May also be interesting to people here: https://github.com/gnat/css-scope-inline
16 lines for short vanilla syntax, scoped animations, and shorthand media queries like Tailwind.
- Nue CSS: A Scaleable Alternative to Tailwind, BEM, and CSS-in-JS
- HTML First – Six principles for building simple, maintainable, web software
- Show HN: Vanilla CSS Tailwind alternative in 16 lines
- Show HN: Vanilla CSS Tailwind alternative in 18 lines
- Tailwind alternative: Inline Scoped CSS
- Htmx Tailwind Alternative: Inline Scoped CSS
htmf
-
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
- Things you forgot because of React
- Htmx, WebAssembly, Rust, ServiceWorker Proof of Concept
-
Ask HN: Getting tired of complexity in web development
I wrote a js lib similar to HTMX, which I call HTMF[1]. Unlike HTMX I try to stay as close to the metal of the current semantics as possible. So, all interactions are based off of forms. I also tried to keep the wording similar to HTML/JS semantics. It's pretty small lib but pretty amazing how far I can get with it. These days I mainly build offline-first apps with it. But I built it in such a way that it can easily be a progressive enhancement to an MPA app.
[1]: https://github.com/jon49/htmf
What are some alternatives?
openrun - Open source alternative to Google Cloud Run and AWS App Runner. Easily deploy internal tools across a team.
v5-docs - 📚 Source code and documentation for the official docs website.
- - Hyphen - An elegant custom element base class
pib - PHP in Browser (powered by WebAssembly)
Fragmentify - Django like template inheritance for XML
yew-beyond-hello-world - yew rust tutorial