joystick
next-runtime
Our great sponsors
joystick | next-runtime | |
---|---|---|
49 | 12 | |
194 | 601 | |
5.2% | 3.3% | |
9.7 | 9.3 | |
3 days ago | 13 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
- 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.
next-runtime
-
5 Ways to Redirect URLs in Next.JS
I say "when it works" because it's not necessarily supported by all hosts. For example, Vercel of course supports it, but Netlify doesn't currently appear to. As for other hosts, you'd need to verify with them, but I'd imagine it varies.
-
My 2023 Year in Review
View on GitHub
-
4./ Client components in static and dynamic routes before Next 13
Note: at the time of writing this, there is a bug in Next (13.4.7). Although Next guarantees that you can use both app router and pages router in the same project, there is a bug that causes a full page reload when you browse from an app route to a pages route or vice versa. This is unfortunate but does not influence our tests.
-
My experience deploying a Next.js application on Netlify (using Next App Router)
So adding an edge function was the only workaround I found. Apparently it's an issue they're working on and I think it should be set as high priority since trailing slashes matter for SEO.
- What is server costs (resources) with Next.js ISR?
-
Next.js rewrites
Here are a great guide on what to use when: https://github.com/netlify/netlify-plugin-nextjs/blob/main/docs/redirects-rewrites.md
-
Netlify: Improved workflow and new role for pricing changes
It also seems like an unconscious acknowledgement that their add-on services (form handling, post-processing, identity, analytics, auth, etc.) are woefully inadequate in some cases and uncompetitive in others. $20/mo for form handling beyond 100 submissions? Okay, maybe. But the feature set is so bare it's laughable. There's minimal to no customization for notification emails, no confirmation emails, and their post-processing for form detection will bring the speed of your build pipeline to its knees on any serious site. On one site turning off post-processing yielded a build time reduction of more than double the actual build time of the site.
Not to mention the fact that by foregoing any concept of a server and forcing everything into some flavor of lambda they've created a scenario where every framework with any such functionality requires open source shepherding to function on their platform[0]. At best they've diluted their initial mission and at worst they've created an unmanageable mess. They can't even make Next.js work on their platform without causing what should issue 404s to return 500s instead[1]. The SEO implications for that are a potential death sentence and that issue has now been open for five months.
I was very optimistic about Netlify at the outset, and it worked great and still continues to work great for our test cases where we've deployed individual LPs. Where the pain seems to start is anything above a thousand pages or more, which is also coincidentally where the stakes start to get higher. I don't know how they could expect anyone at an enterprise or growing business to seriously scrutinize this platform and view it as ideal with that in mind.
[0]: https://github.com/netlify/netlify-plugin-nextjs
-
Next.js measurement: Serve images in next-gen formats even when using next/image
I don't think Netlify supports WebP currently: https://github.com/netlify/netlify-plugin-nextjs/issues/687
- Vercel Welcomes Rich Harris, Creator of Svelte
-
Make a Custom Portfolio Site Generator with StepZen's Developer Publishing Pack
I made the template here using NextJS, because Netlify has a NextJS plugin, which automates the process of using serverless functions. I inserted the call to my StepZen GraphQL endpoint in the pages/api folder to keep sensitive info off the client.
What are some alternatives?
SvelteKit - web development, streamlined
prepack - A JavaScript bundle optimizer.
react-use - React Hooks — 👍
services - Real World Micro Services
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
arduino-cli - Arduino command line tool
ember-render-modifiers - Implements did-insert / did-update / will-destroy modifiers for emberjs/rfcs#415
htmx - </> htmx - high power tools for HTML
React - The library for web and native user interfaces.