crank
React
crank | React | |
---|---|---|
13 | 1,696 | |
2,673 | 222,111 | |
0.1% | 0.6% | |
8.1 | 9.9 | |
8 days ago | 2 days ago | |
TypeScript | 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.
crank
-
Coroutines in JavaScript for Web Components
If you enjoy this approach, you might enjoy the Crank JS framework. https://crank.js.org/
> Crank uses generator functions to define stateful components. You store state in local variables, and `yield` rather than `return` to keep it around.
- Crank.js, the Just JavaScript Framework
-
A Proposal for an asynchronous Rust GUI framework
I'm very interested in seeing if using the commonly implemented forms of compiler support for async programming can also be well used for GUI programming. One wishawa[0] is also perusing this approach in Rust but I first came upon this idea from the crank-js[1] authors. It wasn't clear to me why that one never went anywhere. Was it failure with the approach or was React just a good solution in the space? I can say this though, there's something strikingly elegant about those initial samples of using JavaScript generators for components.
[0]: https://github.com/wishawa/async_ui
[1]: https://github.com/bikeshaving/crank
Take a look at crank.js, a JavaScript framework where components can be written as async functions or as generators. It seems similar to what you're trying to do :)
- UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries
-
Algebraic Effects – You Can Touch This (2019)
Well there's https://crank.js.org that uses native js generators where you would you normally put hooks in. Never used it but looked like a very neat idea.
-
What happens if you mix React, Mobx and generators*? Ok, let's do it!
Reminds me of https://github.com/bikeshaving/crank, which was rather fun for a PoC I made a while back.
-
Are my components supposed to render multiple times?
Strictly speaking, the framework hides this complexity away, but it still exists and it is the framework that's now paying the extra cost. Of course a framework is allowed, and should, when possible, hide away these things. For example Crank.js uses generators to allow for async Components as first class citizens, https://github.com/bikeshaving/crank, but they're still having to deal with the pitfalls of asynchronous work.
-
React State Museum - Examples to help portray the how, why, which, pros, and cons of various state management systems in the React ecosystem
To give the author of https://crank.js.org/ due credit, after reading through the descriptive posts I was impressed by the amount of thought and design that went into it.
-
What's New in React 18?
> What do you propose as an alternative?
There are lots of alternatives, but perhaps the simplest would have been to use async generators. This is how Crank[0] (mentioned elsewhere in this thread) works, and it allows you to do anything (AFAIK) that's possible with hooks with a much simpler and more testable API.
> So, sure, there are limitations and rules you have to pay attention to with hooks... but that's just programming.
No, it's not. The biggest problem with React hooks is that they are not composed of transferable knowledge, meaning memorizing these rules and patterns does not transfer outside of React; likewise, I can't use much of the knowledge I have already built up over many years of my career when using hooks. It's the same argument that's made against Rails, where you have to learn tons of Rails-specific idioms (on top of having to understand general concepts like relational database access patterns) instead of just writing code in a way that's more direct and intuitive for anyone.
My brain has limited RAM. The more things I have to keep in my head when developing against an API, the more likely I am to make a mistake. With every release of React, I seem to have to keep more and more of these details in my brain as I work. Contrast this with something like Svelte, where you really only need to fully grok about two concepts to use it effectively. I understand that this is the tradeoff the React team made, but I'm not convinced it's worth it.
[0]: https://crank.js.org/ and https://crank.js.org/blog/introducing-crank
React
-
Inflight Magazine no. 9
We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.
-
"Kawaii" tech logos by Sawaratsuki
Go to https://react.dev/?uwu=true for a surprise.
-
Building an Email Assistant Application with Burr
You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).
-
React 18.3.0 Is Out
Oddly, no info on changelog: https://github.com/facebook/react/blob/main/CHANGELOG.md
-
Preact vs React: A Comparative Guide
In this post, we get to know more about Preact, one of this year's trending libraries. And we'll compare it to React to see which one suits better for our projects.
-
Meet Cheryl Murphy: Full-Stack Developer, lifelong learner, and volunteer Project Team Lead at Web Dev Path
Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.
-
How to Build an AI FAQ System with Strapi, LangChain & OpenAI
Basic knowledge of ReactJs
-
Everyone Has JavaScript, Right?
Google Translate and many other libraries break React based sites if they are using refs.
I don't think that point it falls under "written on naive assumptions"
https://github.com/facebook/react/issues/11538
the issue says closed but you can easily catch it in various sites and use cases.
-
Integrate Bootstrap with React
This article serves as your comprehensive guide to mastering the art of combining Bootstrap and React seamlessly. Dive in to uncover the tips, tricks, and best practices to elevate your UI design game effortlessly.
-
React Server Components Example with Next.js
This isn’t an accident; when Meta introduced React Server Components, Dan Abramov explicitly stated that they collaborated with the Next.js team to develop the RSC webpack plugin.
What are some alternatives?
js-framework-benchmark - A comparison of the performance of a few popular javascript frameworks
qwik - Instant-loading web apps, without effort
async_ui - Lifetime-Friendly, Component-Based, Retained-Mode UI Powered by Async Rust
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
ava - Node.js test runner that lets you develop with confidence 🚀
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
SvelteKit - web development, streamlined
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
lit-element - LEGACY REPO. This repository is for maintenance of the legacy LitElement library. The LitElement base class is now part of the Lit library, which is developed in the lit monorepo.
vue-promise-dialogs - A tiny & modern library that allows you to work with dialogs as with asynchronous functions.
Tailwind CSS - A utility-first CSS framework for rapid UI development.