eureka VS joystick

Here's an example of building a well-structured, maintainable web-site using JavaScript, HTML and CSS: https://github.com/wisercoder/eureka/tree/master/webapp/Clie...

It doesn't use React (imagine the horror!), instead it uses two tine 500-line libs.

> a literal 5-20x productivity boost

Not really. See a better way here: https://github.com/wisercoder/eureka

I'm not quite seeing React being used, just JSX though? All the view and state updating is being done manually, but it looks fairly well-organised. There are small optimisations like debouncing onInput with a timeout (avoiding rapid re-rendering for every character typed): https://github.com/wisercoder/eureka/blob/master/webapp/Clie...

React works well for simple, non-interactive components. Complex, interactive components are going to have state. Stateful components don't work so well in React. If you want to update props in a stateful component, the recommendation is to replace the component entirely by changing its key. At the point all of the benefits of React (preservation of selection, caret position, scroll position etc.) vanish. You might as well use vanilla js instead of React.

What does using Vanilla JS look like? Here's an example: https://github.com/wisercoder/eureka It uses two tiny 500-line libs. It uses TSX files, just like React. It has components, just like React. It doesn't have incremental screen update, but neither does React, if your components are interactive and stateful.

SEEKING WORK, Tennessee, United States

Remote: Yes

I'm a full-stack, JavaScript/Node.js developer and designer. I'm the creator of the Joystick JavaScript framework [1], Push deployment service [2], and Mod CSS framework [3].

I also have experience with MongoDB, PostgreSQL, and MariaDB (limited but competent) and devops (K8s + Docker and bare-metal linux admin, the latter preferred for simplicity/stability).

Currently looking to take on clients who are open to using Joystick, Push, and Mod to design and develop their app. Because it's still at a pre-release version, I'm willing to work out deals around pricing to get some more test-cases under my belt. Ideal client is a solopreneur w/ funding or entrepreneur with previous experience + funding. Open to working with startups (early or established), but only on greenfield projects where use of Joystick is ok.

Email: [email protected].

[1] https://cheatcode.co/joystick

[2] https://cheatcode.com/push

[3] https://cheatcode.co/mod

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).

[1] https://github.com/cheatcode/joystick

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...

Joystick [1] will let you go. No Stockholm syndrome. No lotion in the basket.

[1] https://github.com/cheatcode/joystick

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.