eureka
uhtml
eureka | uhtml | |
---|---|---|
11 | 14 | |
4 | 841 | |
- | - | |
1.8 | 9.0 | |
over 3 years ago | 15 days ago | |
HTML | ||
GNU General Public License v3.0 only | 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.
eureka
-
How to build a website without frameworks and tons of libraries
Here's an example of building a well-structured, maintainable web-site using JavaScript, HTML and CSS: https://github.com/wisercoder/eureka/tree/master/webapp/Clie...
It doesn't use React (imagine the horror!), instead it uses two tine 500-line libs.
-
React is 10 years old
> a literal 5-20x productivity boost
Not really. See a better way here: https://github.com/wisercoder/eureka
- Building a Front End Framework; Reactivity, Composability with No Dependencies
-
React is a fractal of bad design
I'm not quite seeing React being used, just JSX though? All the view and state updating is being done manually, but it looks fairly well-organised. There are small optimisations like debouncing onInput with a timeout (avoiding rapid re-rendering for every character typed): https://github.com/wisercoder/eureka/blob/master/webapp/Clie...
- Ask HN: Good resource on writing web app with plain JavaScript/HTML/CSS
- Can We All Just Admit React Hooks Were a Bad Idea?
- Ask HN: What happened to vanilla HTML/CSS/JS development?
-
I don't miss React: a story about using the platform
React works well for simple, non-interactive components. Complex, interactive components are going to have state. Stateful components don't work so well in React. If you want to update props in a stateful component, the recommendation is to replace the component entirely by changing its key. At the point all of the benefits of React (preservation of selection, caret position, scroll position etc.) vanish. You might as well use vanilla js instead of React.
What does using Vanilla JS look like? Here's an example: https://github.com/wisercoder/eureka It uses two tiny 500-line libs. It uses TSX files, just like React. It has components, just like React. It doesn't have incremental screen update, but neither does React, if your components are interactive and stateful.
- A Visual Guide to React Rendering
uhtml
-
Svelte frontend vs HTMX and hyperscript
I have to say that I am an extremist minimalist, so I use a nano-framework I developed for the frontend, with uhtml (https://github.com/WebReflection/uhtml) and some JavaScript libraries to help.
-
Xeito - A framework for building web applications
One of the main decisions I had to make early on was template handling, there are many approaches out there and of course, with React being the king, I first tried implementing a VirtualDOM complete with JSX support and whatnot... well that didn't really worked for what I was trying to achieve, so I moved into Tagged Template Literals (through µhtml) and tried to stick to standards as much as possible by building on top of the Custom Elements API.
- Anyone have multiple language syntax highlighting with treesitter working?
-
New Web Component Framework!
FAST rendering thanks to µhtml
-
Ardi: Welcome to the Weightless Web
Challenge: With declarative rendering, oftentimes entire DOM trees are re-painted because of simple prop or state changes that could have been handled faster by imperative DOM manipulation. I wanted a framework that, like Lit, only updated content or attributes that had changed instead of re-painting entire DOM elements and trees. Solution: I chose µhtml for the default templating system because it accomplishes this goal and other advanced templating features in a tiny bundle size. To make rendering even faster and smoother, I throttled uhtml's rendering using requestAnimationFrame.
-
Ask HN: What happened to vanilla HTML/CSS/JS development?
> There are lighter-weight shadow dom frameworks out there (than Vue/React/Angular) so why would you want to write one yourself?
You can even avoid a shadow DOM entirely:
https://github.com/WebReflection/domdiff
https://github.com/WebReflection/uhtml
-
I don't miss React: a story about using the platform
My next goal would be to discard snabbdom (and virtualdom) and use custom elements. For that I'm evaluating a library like https://github.com/WebReflection/uhtml and all it's ecosystem of utility
-
It's been 5 years since I've done Frontend work, getting back in the game
Yep ditched React since 2015, it's still the same mess today. They all not trying to encourage interoperability, and comes with their own build .. seriously? Frontend should be just libs! Use https://github.com/WebReflection/uhtml or lit-html where things should be highly dynamic.
-
Can I just jump into React if I already know the fundamentals of JS/HTML/CSS?
If it's for getting into job market, go for React. If it's for learning declarative ui, build cool stuff real quick without tooling, go with lit-html or bravely go with https://github.com/WebReflection/uhtml (it's more simple than anything else, yet powerful)
-
Hooks Considered Harmful
A tiny dom lib like https://github.com/WebReflection/uhtml is more than enough for very complicated UI, with understanding how events work, will be able to implement very thin state management on top. With game programming styled manual render() call here and there as needed, pretty neat.
What are some alternatives?
webcomponents - Web Components specifications
lit - Lit is a simple library for building fast, lightweight web components.
Ink - 🌈 React for interactive command-line apps
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
org-mode-site-template - A workflow for a complete site using the HTML publish option of Emacs Org-Mode
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
el - Minimal JavaScript application framework / WebComponents base class
developer.chrome.com - The frontend, backend, and content source code for developer.chrome.com
editable-website - A SvelteKit template for building CMS-free editable websites
prehistoric-simulation - Simulator in browser
10kbclub - A curated collection of websites whose home pages do not exceed 10 KB compressed size
inferno - :fire: An extremely fast, React-like JavaScript library for building modern user interfaces