joystick
jsx
Our great sponsors
joystick | jsx | |
---|---|---|
49 | 14 | |
194 | 1,944 | |
5.2% | 0.1% | |
9.7 | 0.0 | |
7 days ago | 5 months ago | |
JavaScript | HTML | |
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.
joystick
- Show HN: Joystick – A Full-Stack JavaScript Framework
-
Ask HN: Freelancer? Seeking freelancer? (April 2024)
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
- Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
-
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).
[1] https://github.com/cheatcode/joystick
- Web Components Will Outlive Your JavaScript Framework
-
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...
- GitHub - cheatcode/joystick: A full-stack JavaScript framework for building web apps and websites.
- Joystick: A full-stack JavaScript framework for building web apps and websites
-
React is a fractal of bad design
Joystick [1] will let you go. No Stockholm syndrome. No lotion in the basket.
[1] https://github.com/cheatcode/joystick
-
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.
jsx
-
I am having to pass down 8+ props even for simple components. What are some common ways to mitigate this? (Typescript)
Svelte syntax? Yes, there is upcoming initiative JSX 2.0 which includes shorthands like that. However, have no idea whether it will be released any time soon. So let's say "this is part of React/JSX 1.0" (shrugging)
-
Why TypeScript is the better JavaScript
Inherent support for JSX in the language itself
-
Node.js やReact、ESM、Viteの説明
JavaScript + HTML(DOM)= JSX
-
Alpine.js
FWIW, the className prop is a React thing not a JSX thing. Other libraries which use JSX will happily accept a plain class prop. The React limitation is abstraction leakage: props are not attributes, they map to DOM properties.
But to the point that JSX is a DSL, that limitation is specifically because React itself is very tightly coupled to DOM semantics… but JSX explicitly has no built in semantics[1].
1: First sentence of https://facebook.github.io/jsx/ - “JSX is an XML-like syntax extension to ECMAScript without any defined semantics.”
-
React - Introducing JSX
JSX stands for 'JavaScript XML' and is a syntax extension for JavaScript. It is used to create DOM elements that are then rendered in the React DOM. Although it looks like HTML, it is actually an XML-like syntax specifically written for use in React. Interestingly, JSX is not valid JavaScript either. JSX needs to be compiled by a tool like Babel to be translated into regular JavaScript that a browser can understand. Put simply, JSX describes what the UI should look like, and React takes care of properly rendering it.
- Web lagnunages to learn
-
My thoughts on Mithril.js
Alternatively, you can use JSX syntax (like with React), but then you need build-tools.
-
Incrementally adopting TypeScript in a create-react-app project
Note: For React component files (JSX) we'll use .tsx to maintain JSX support and for non React files we'll use the .ts file extension. However, if you want you could still use .ts file extension for React components without any problem.
-
Sciter, the 5 MB Electron alternative, has switched to JavaScript
I’m concerned that you’re falling into the same trap here with integrating your own variant of JSX, and mulling over adding more things like hyphens in unquoted object literal keys.
JSX is popular enough that it’s safe, ECMAScript isn’t going to break it, but your alterations to JSX are already significantly incompatible: you have being equivalent to JSX("input", {"class": "search"}, null), but the JSX everyone else is using has that equivalent to JSX(input.search, {}, null). I’m not certain if your JSX syntax is supposed to be able to be used with React code or anything else that uses JSX syntax, but if yes then it’ll be broken in a significant number of cases so that it’s worse than useless, and if no, well, it’s going to be misleading, and what if JSX did get merged into ECMAScript in some form? Then you’d be incompatible with ECMAScript again.
Same deal with hyphens in unquoted object literal keys: it’s not part of ECMAScript now, but just because it’d be a syntax error now doesn’t mean it always will be. Decorators in TypeScript are a good example of things going badly wrong even when an extremely popular project is involved.
I say: if you want to go JavaScript, go JavaScript, maaaaaybe plus standard JSX conforming with <https://facebook.github.io/jsx/>, and no further. Even if what you do is obviously superior, &c. &c. I’d apply the same reasoning on your fork of CSS: you introduced it for a good reason back then, but now it’s just friction, even if it’s a little better in a vacuum (and maybe it is in parts, maybe it isn’t in other parts).
-
Do you think HTML is a programming language
Then it might be time for a pull request which identifies these parts as JSX.
What are some alternatives?
SvelteKit - web development, streamlined
htm - Hyperscript Tagged Markup: JSX alternative using standard tagged templates, with compiler support.
react-use - React Hooks — 👍
React - The library for web and native user interfaces.
concise-encoding - The secure data format for a modern world
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
svelte-native - Svelte controlling native components via Nativescript
prepack - A JavaScript bundle optimizer.
next-runtime - The Next.js Runtime allows Next.js to run on Netlify with zero configuration
vite - Next generation frontend tooling. It's fast!
arduino-cli - Arduino command line tool
ember-render-modifiers - Implements did-insert / did-update / will-destroy modifiers for emberjs/rfcs#415