joystick VS SvelteKit

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

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.

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

---

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

[2] https://dribbble.com/rglover

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.

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

[2] https://cheatcode.co

How about plain HTML, CSS, and JavaScript? [1]

[1] https://github.com/cheatcode/joystick#writing-a-component

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

I've always sat on the design, marketing and front-end side of the fence, so this was my first attempt at making a 'full' web app.

Here's the stack I used:

- SvelteKit (https://kit.svelte.dev/)

Hello internet. I just published a new blog post on how to implement dark mode with SvelteKit, optionally with PostCSS and TailwindCSS:

Hi, Sveltian today I would like to share you how to stop theme flickering after we refreshing a page while we using Daisy UI with Sveltekit

I just started a project and chose this stack:

- SSR SvelteKit with Hydration (https://github.com/sveltejs/kit)

ZenStack generates queries that target either SWR or TanStack, making it compatible with a wide range of full-stack frameworks such as Next.js, Remix, SvelteKit, Nuxt, and more.

SvelteKit is a top pick for Svelte developers.

Creating a portfolio website can be a practical way to showcase resumes, projects, and blogs. As someone who leans more towards backend development, I found myself in the situation of wanting to establish an online presence without drowning myself into the complexities of React or dealing with the manual development with plain HTML, CSS, and JavaScript. It was in the search for a simpler alternatives that I found Svelte, and its meta-framework, SvelteKit.

// See https://kit.svelte.dev/docs/types#app // for information about these interfaces declare global { namespace App { // interface Error {} interface Locals { id: string; email: string; } // interface PageData {} // interface Platform {} } } export {};

SvelteKit: The modern, blazing-fast web application framework that simplifies development with its intuitive approach and seamless transitions

Aha another Play user.

I took over a rather large Play project at work and it feels like the worst parts of Rails, then there's a poorly-implemented, old ReactJS + bootstrap frontend on it.

Would highly recommend taking a look at Sveltekit [0] with TypeScript and drizzle-orm if you want a full-stack experience.

[0] - https://kit.svelte.dev/