domdiff
joystick
domdiff | joystick | |
---|---|---|
2 | 50 | |
210 | 198 | |
- | 6.1% | |
0.0 | 9.9 | |
over 1 year ago | 7 days ago | |
JavaScript | JavaScript | |
ISC License | GNU General Public License v3.0 or later |
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.
domdiff
-
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
-
Proposal to add efficient DOM diffing to browser
If by faster you mean faster than React I think there is evidence it can be. The author of the issue writes lots of dom utility and rendering libraries and I believe domdiff is more or less what he describes in the post:
https://github.com/WebReflection/domdiff
You can find it placed way above React in the usual JS rendering benchmarks:
https://rawgit.com/krausest/js-framework-benchmark/master/we...
Now it's not entirely clear whether these benchmarks convey something meaningful except for maybe the point that most frameworks are quite fast. That being said I think it's developer experience that really stands to improve. Thinking of view as a pure function of state was a great innovation, but existing implementations can end up fracturing the view into virtual doms and non-virtual. Then you end up with problems like D3 and React not coexisting.
I feel like I heard something from the lit-html folks that a long term aspiration was to integrate some learnings from the project into chrome, but I haven't been able to find where again.
There has been a trend in JS with libraries becoming idiomatic to the language to later have the issues they targeted be addressed natively (a la JQuery).
In general, I definitely appreciate your point about adding complexity to the platform, but I think when it comes to web technologies that ship has long sailed. I really see it as an opportunity to bring a lot of simplicity, chiefly filling that void that's birthed a billion JS frameworks.
Thanks for the thoughtful comment.
joystick
-
Simplicity Is an Advantage but Sadly Complexity Sells Better
I built a full-stack JS framework [1] that I thought would be a hit. As best as I can tell, because it lacks the complexity/word salad of existing solutions, it's mostly been ignored despite being (imo) an elegant solution to a long-standing problem.
[1] https://cheatcode.co/joystick
- Show HN: Joystick – A Full-Stack JavaScript Framework
-
Ask HN: Freelancer? Seeking freelancer? (April 2024)
SEEKING WORK, Tennessee, United States
Remote: Yes
I'm a full-stack, JavaScript/Node.js developer and designer. I'm the creator of the Joystick JavaScript framework [1], Push deployment service [2], and Mod CSS framework [3].
I also have experience with MongoDB, PostgreSQL, and MariaDB (limited but competent) and devops (K8s + Docker and bare-metal linux admin, the latter preferred for simplicity/stability).
Currently looking to take on clients who are open to using Joystick, Push, and Mod to design and develop their app. Because it's still at a pre-release version, I'm willing to work out deals around pricing to get some more test-cases under my belt. Ideal client is a solopreneur w/ funding or entrepreneur with previous experience + funding. Open to working with startups (early or established), but only on greenfield projects where use of Joystick is ok.
Email: [email protected].
[1] https://cheatcode.co/joystick
[2] https://cheatcode.com/push
[3] https://cheatcode.co/mod
- Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
-
Web Components Eliminate JavaScript Framework Lock-In
There is. I was frustrated by all of the chaos and built a solution [1]. Not too far of from an RC1 and then a 1.0 (which is being done slowly so I can freeze APIs and avoid the typical JS rug pulls).
[1] https://github.com/cheatcode/joystick
- Web Components Will Outlive Your JavaScript Framework
-
We should start to add “ai.txt” as we do for “robots.txt”
I've been (slowly) writing a new type of OSS license around this exact concept so it's easier to (legally) stop LLMs hoovering up IP [1] (under "derivative works not permitted").
[1] https://github.com/cheatcode/joystick/blob/development/LICEN...
- GitHub - cheatcode/joystick: A full-stack JavaScript framework for building web apps and websites.
- Joystick: A full-stack JavaScript framework for building web apps and websites
-
React is a fractal of bad design
Joystick [1] will let you go. No Stockholm syndrome. No lotion in the basket.
[1] https://github.com/cheatcode/joystick
What are some alternatives?
dom - DOM Standard
SvelteKit - web development, streamlined
modern-todomvc-vanillajs - TodoMVC with Modern (ES6+), Vanilla JavaScript
react-use - React Hooks — 👍
notemplate - NoTemplate is not a template library.
concise-encoding - The secure data format for a modern world
prehistoric-simulation - Simulator in browser
svelte-native - Svelte controlling native components via Nativescript
AlgoVis - A web page that visualizes a simple sorting algorithm.
next-runtime - The Next.js Runtime allows Next.js to run on Netlify with zero configuration
web-starter - Starter for Fastify + Web Components/Lit Web App. Includes Reload and web server restart on dev mode.
arduino-cli - Arduino command line tool