joystick

If you just want to use plain HTML with JavaScript, take a peek at Joystick [1]. 100% plain HTML, CSS, and JavaScript based components (zero attribute hacks or compiler tricks). No external libraries for basic functionality (state, data fetching, url handling—all included or relies on native browser functionality). All a part of one full-stack framework that works out of the box. [1] https://github.com/cheatcode/joystick

> you still have to rely on third party library for routing, state management, querying etc. Take a peek at Joystick [1]. I designed it as the exact antithesis to this. It's full-stack (Node.js back-end with a fully ssr'd component framework designed for the long-term) and doesn't introduce any special paradigms (i.e., vanilla HTML, CSS, and JavaScript—no attribute tricks/compilers needed). Everything is designed to be a fixed-API with the only changes being added functionality (i.e., no random "hey this is deprecated now" rug pulls). Philosophy is described here: https://github.com/cheatcode/joystick#what-distinguishes-joy... [1] https://github.com/cheatcode/joystick

I'm always accepting refugees [1]. [1] https://github.com/cheatcode/joystick

Unless the framework you're using treats maintainability as a feature [1], not an afterthought. This is really just a long argument against bad framework design (which is fair), not frameworks. [1] https://github.com/cheatcode/joystick#what-distinguishes-joy...

:wave: https://github.com/cheatcode/joystick (But I sincerely hope it's not a fad as I've designed it to be the antithesis to the rabbit chasing and dogmatic nonsense that's plagued JS the last decade or so).

I'm working on fixing that clusterfuck (which paired with something like Red Goose would restore sanity): https://github.com/cheatcode/joystick.

Come to the dark side, we have cooookies https://github.com/cheatcode/joystick

HAProxy has blown my mind. I'm using it to build a deployment tool for Joystick [1] and it's a real treat to work with. I utilize this specific feature (enabling/disabling servers on the fly) and it worked on the first swing without issue. Made scaling a cluster of servers fairly effortless. [1] https://github.com/cheatcode/joystick

You'd dig Joystick: https://github.com/cheatcode/joystick. I designed it to be a natural transition from learning the fundamentals of HTML, CSS, and JavaScript into full-blown, component-driven UI development. Dirt simple API, no syntax tricks, no specialized knowledge. Just plain ol' HTML, CSS, and JavaScript organized into a system that's more productive than standalone files. It works on its own in the browser or as a part of a full-stack framework.

Yes, they are. This is why I built Joystick [1] to take a lot of the valuable concepts of modern web development frameworks and make them work with pure HTML, CSS, and JavaScript without any hacks, syntax tricks, etc. [1] https://github.com/cheatcode/joystick

There's hope: https://github.com/cheatcode/joystick.

The overhead is arbitrary if done properly. I did this in Joystick [1] and was shocked at how overcomplicated folks make it. You're literally just saying "render to static HTML on the server, and on the client, have a way to render a root component to screen and attach event handlers." Without any serious thoughts about optimization (practically none yet), a no-cache refresh/mount takes 227ms to DOMContentLoaded and 696ms to a full load. Here's the SSR I do: https://github.com/cheatcode/joystick/blob/development/node/... Here's the mount ("hydration"): https://github.com/cheatcode/joystick/blob/development/ui/sr... The only "magic" is that I embed the hydration logic into the built JS for the current page and it fires automatically on load (no need to add manual hydration code). [1] https://github.com/cheatcode/joystick

Having spent several years working with GraphQL (using it in multiple projects and teaching it to others), I've found that in the majority of cases just doing a plain JSON-RPC API is preferable and far easier to reason about for all skill levels. When I built Joystick [1], this is why I implemented the API system [2] as a JSON-RPC model, but stole the idea of validating inputs (optionally) and then on the client, optionally specifying tailored output (also optional—like how you can request specific fields back in GraphQL but instead of a custom query language, just pass an array of paths like ['customers.creditCard.expirationMonth', 'customers.creditCard.expirationYear'] for the specific data you want returned). What I learned implementing that is that the typing/querying for specific fields ideas is brilliant, but much better when it's f

You might dig Joystick: https://github.com/cheatcode/joystick.

For people concerned about the growing complexity of all this stuff, I'd appreciate you taking my approach for a spin: https://github.com/cheatcode/joystick. It's intentionally boring and simplistic. Good ol' fashioned HTML, CSS, and full-stack JavaScript (Node.js on the back-end).