joystick
redwood
Our great sponsors
joystick | redwood | |
---|---|---|
46 | 114 | |
186 | 16,682 | |
1.1% | 0.4% | |
9.7 | 10.0 | |
3 days ago | 6 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | 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.
joystick
-
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).
-
Web Components Will Outlive Your JavaScript Framework
I was excited for web components, but the API was lacking (the final tipping point that led me to build Joystick [1]). I just couldn't get on board with a web-standard that eschewed HTML in favor of stuff like this [2] where list items are attributes. The hyphenated namespace thing has always made my eye twitch, too (silly, I know).
[1] https://github.com/cheatcode/joystick
[2] https://github.com/mdn/web-components-examples/blob/main/edi...
-
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...
-
React is a fractal of bad design
Joystick [1] will let you go. No Stockholm syndrome. No lotion in the basket.
-
The Great Gaslighting of the JavaScript Era – The Spicy Web
If you share the sentiment of the author and want to get on the road to recovery, I submit Joystick [1]. I had similar frustrations to this and decided to do something about it [2].
[1] https://github.com/cheatcode/joystick
[2] Please give it an honest a look and save the XKCD "muh standards" comic and accompanying snark for after you've taken it for a spin.
-
Ask HN: Freelancer? Seeking freelancer? (March 2023)
SEEKING WORK / Remote
Location: Tennessee, US
Remote: Preferred
Contact: [email protected]
---
Full-stack JavaScript developer (any front-end JS framework; Node.js on back-end with adaptability to Deno and Bun). Founder @ CheatCode and author of the full-stack JavaScript framework, Joystick [1] (fully-integrated UI framework a la React with a batteries-included Node.js back-end).
I specialize in designing and building full-stack apps, handling all UI design [2], front-end development, and back-end development. Using Joystick, I can deliver a high-quality result very quickly that can be picked by any junior-level JS developer due to the simplicity and web standards-adherent approach of the framework.
Recent Testimonial:
“We worked with Ryan to develop an internal security monitoring tool for the Coinbase security team. Ryan was great to work with. He’s an excellent developer and communicator with great vision and eye for the UI. I highly recommend working with Ryan and CheatCode if you’re looking to ship a high-quality piece of software."
- Xavier Cadena
---
-
Ask HN: What would be your stack if you are building an MVP today?
Joystick [1] using MongoDB as the primary database. Run a few instances on VPS and then a load balancer in front. This is how I run my site [2] following a massive amount of headaches and random downtime fighting w/ a k8s cluster. Zero downtime since I moved it over in October.
-
Alpine.js
How about plain HTML, CSS, and JavaScript? [1]
[1] https://github.com/cheatcode/joystick#writing-a-component
-
GitHub Is Sued, and We May Learn Something About Creative Commons Licensing
This may be of interest to others here. After reviewing the existing OSS licenses, I decided to write my own (SAUCR: Source Available Under Commercial Restriction—pronounced "saucer"). I'm still working on formalizing the details of it so others can use it, but if you're curious there's an example here [1].
tl;dr it gives specific permissions as to what derivative works are and are not permitted while making the source available for others. The key being: you can be as permissive or as limited as you want in how your code is used.
[1] https://github.com/cheatcode/joystick/blob/development/LICEN...
redwood
-
Release Radar • February 2024 Edition
Frameworks are a theme with this month's Release Radar, so here's another. Redwood is a full-stack, JavaScript/TypeScript web application, designed to scale with you. It uses React frontend for the frontend and links to a custom GraphQL API for the backend. The latest version includes a bunch of breaking changes such as moving to Node 20.0, the Redwood Studio, and highly requested GraphQL features such as Realtime, Fragments, and Trusted Documents, the server file, new router hooks, and heaps more. If you've previously used Redwood, you'll probably want to upgrade to version 7.0. The team have put together a handy migration guide for you to follow.
-
The Current State of React Server Components: A Guide for the Perplexed
The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.
-
What will happen to the full-stack framework in the future?
Although there are quite a few opinionated battery-included frameworks that have picked up everything for you like RedwoodJS, Blitz, and Create-T3-App, you still need to choose between them and hope that they will remain mainstream and well-maintained in the future. So how should we choose?
-
NextJS vs RedwoodJS
Web development frameworks in JavaScript, such as NextJS and RedwoodJS, have gained popularity among developers. Choosing the right framework, library, or tool for a project is crucial for efficient development. Developers often seek the best tools to save time and avoid reinventing the wheel.
-
Is Next.js 13 + RSC a Good Choice? I Built an App Without Client-Side Javascript to Find Out
Next.js 13 ignited the first wave of attention to React Server Components (RSC) around the end of last year. Over time, other frameworks, like Remix and RedwoodJS, have also started to put RSC into their future road maps. However, the entire "moving computation to the server-side" direction of React/Next.js has been highly controversial from the very beginning.
-
Enhancing Redwood: A Guide to Implementing Zod for Data Validation and Schema Sharing Between the API and Web Layers
I'm currently experimenting with the fantastic Redwood framework. However, while going through the excellent tutorial, I didn't find any guidance on using data validation libraries like Yup, Zod, Vest, etc. So, I had to do some investigation and came up with a solution. This article describes the implementation of validation with Zod in a fresh Redwood app. You can find the sources at this github repository.
-
ZenStack: The Complete Authorization Solution for Prisma Projects
RBAC is one of the most common authorization models - users are assigned different roles, and resource access privileges are controlled at the role level. Despite its limitations, RBAC is a popular choice for simple applications, and some frameworks (like RedwoodJS) have built-in support for it.
-
🏆 Top 5 full-stack JS frameworks in 2023 - which one should you pick for your next project? 🤔
Check it out here: https://redwoodjs.com/
-
Implementing Flexible Authorization in RedwoodJS Projects
RedwoodJS is an opinionated full-stack framework for building modern web applications. It makes some of the most critical decisions for you - like using React for UI development, GraphQL for API, and Prisma for database programming, etc. - so you can stop struggling with choices and focus on building your app.
-
Is Prisma ORM ready for production?
Also, there are lots of exciting web frameworks that use Prisma as their default ORM layer (like RedwoodJS which is built by the founder of GitHub, Amplication which recently raised $6.6M in seed funding, Wasp (YC W21) or KeystoneJS) which should give you some more validation that Prisma is being used in a lot production applications :)
What are some alternatives?
remix - Build Better Websites. Create modern, resilient user experiences with web fundamentals.
Next.js - The React Framework
Blitz - ⚡️ The Missing Fullstack Toolkit for Next.js
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
Gatsby - The best React-based framework with performance, scalability and security built in.
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
Refine - A React Framework for building internal tools, admin panels, dashboards & B2B apps with unmatched flexibility.
Nuxt.js - Nuxt is an intuitive and extendable way to create type-safe, performant and production-grade full-stack web apps and websites with Vue 3. [Moved to: https://github.com/nuxt/nuxt]
KeystoneJS - The most powerful headless CMS for Node.js — built with GraphQL and React
SailsJS - Realtime MVC Framework for Node.js
node-express-boilerplate - A boilerplate for building production-ready RESTful APIs using Node.js, Express, and Mongoose