Hey folks, author of Joystick here. A quick FAQ if you're curious: > Another framework, seriously? Yes. If you dig it, use it. If you don't, that’s cool, too.

Hey folks, author of Joystick here. A quick FAQ if you're curious: > Another framework, seriously? Yes. If you dig it, use it. If you don't, that’s cool, too. > Why would I use this and not React/Vue/Svelte/etc? Because it makes sense to you. Ergonomically, I designed Joystick components to be a beginner-friendly alternative to React (I worked with it from 2015-2021 and got tired of the constant API rug pulls). Joystick will either "click" for you or it won't. Feature-wise, it's far more robust than React while maintaining the same behavior (e.g., reactivity via state, passing props, etc). Performance-wise, I'd currently call Joystick "good enough for most stuff" and have plans to focus in on this more deeply as the framework reaches 1.0. > Why not web components? Two reasons: my OCD wouldn't let me do the dashed component names (along with forcing developers to provider a name) and the Shadow DOM thing was a brain teaser when I tried to use web components during the early prototyping stages of Joystick’s components. I would love to see a future version of Joystick use web components under the hood, but as of today: it's a "close but no cigar" for me. > Why not TypeScript? I love the idea of having types in JavaScript, I hate the idea of only being able to get that via a superset controlled by a corporation (however aligned with OSS values they might be). I think TypeScript is a brilliant idea, horribly implemented. I want Joystick to be as standards-aligned and easy to pick up as possible and TypeScript breaks both of those rules. As of today, TypeScript is a no-go for me in favor of vanilla JS. > Why would I trust an indie, solo-developer framework? Don't. Or do. I'm indifferent as long as you find value in what I've created. I want to build a solid business around Joystick (see the site for how) to support my efforts. That's the best guarantee I can offer. Short of getting rolled by a city bus (i.e., The Bus Factor), my sights are on 10 years out. In the words of Townes Van Zandt "I'll be here in the morning." > Why your own license? I love the idea of open source, but I've seen far too many pure-hearted, talented developers get run into the ground by it. I don't want to repeat their fate. I'd like to be able to earn a living from my work on Joystick beyond a job, sponsorships, or client work. To protect that as best as I can with limited resources, I wrote the SAUCR License (Source Available Under Commercial Restriction) [1]. It's designed as a happy medium: you can audit the source code to your heart's content and use it 100% free to build your apps, but reappropriating it is a no-go. [1] https://saucr.org https://saucr.org