crank
astro
crank | astro | |
---|---|---|
13 | 505 | |
2,673 | 42,546 | |
0.1% | 2.2% | |
8.1 | 10.0 | |
9 days ago | 3 days ago | |
TypeScript | TypeScript | |
MIT 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.
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
astro
-
Composable architecture example: Go headless (best practices)
Astro
-
Building static websites
Case study 4: Astro
-
Setting up Doom Emacs for Astro Development
Astro is the new hot new web framework on the block. All the cool kids are using it. I've recently given up, drank the Kool-Aid, and gone all in on it.
-
Building a self-creating website with Supabase and AI
Built with Supabase, Astro, Unreal Speech, Stable Diffusion, Replicate, Metropolitan Museum of Art
-
The Subtle Case For and Against React
Astro to use every framework at once instead of just react? https://astro.build/
-
Run a Linux Distro in your Android device
Depending on the stack of the repository you are cloning, you might have to install additional dependencies. For this demo, I'm using my own website, which is a static website built with Astro.js. It which requires to have Node.js installed and Yarn for package manager.
-
Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
Database: turso [7] or neon postgres [8] with (drizzle orm) or cloudflare durable objects
1. https://github.com/withastro/astro
-
Ask HN: What's the simplest static website generator?
Maybe a bit too elaborate for your taste, but I've used https://astro.build/ and loved every bit of it.
-
How to Integrate Astro With ApostropheCMS pt. 1
Astro is an open-source JavaScript framework known for its versatility, performance, and new approach to web development. It enables developers to create fast, modern, content-rich web applications and sites using the "Bring Your Own Framework" (BYOF) model.
-
Growing a side-project to 100k Unique Visitors in one week
Astro was always on my list of things to learn. I've been using Remix and NextJS for a while, and I was interested in trying out a new framework. I decided it would be a good opportunity to build the site with it. This decision turned out to be a great one, as it saved me a lot of money on hosting costs later on.
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
React - The library for web and native user interfaces.
vite - Next generation frontend tooling. It's fast!
async_ui - Lifetime-Friendly, Component-Based, Retained-Mode UI Powered by Async Rust
eleventy 🕚⚡️ - A simpler site generator. Transforms a directory of templates (of varying types) into HTML.
ava - Node.js test runner that lets you develop with confidence 🚀
Hugo - The world’s fastest framework for building websites.
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.
fresh - The next-gen web framework.