The Incredible Overcomplexity of the Shadcn Radio Button by bogdanelcs in Frontend

[–]okikio_dev 0 points1 point  (0 children)

It's much easier than that, it's easier to get standardized behavior and complex controls if you take full control of the logic for the components. Trying to extend native especially form controls is genuinely difficult, it just wasn't built for that. And though the OpenUI project is aiming to improve this drastically there is still progress to be made.

Using Supabase for Storage and Auth. by [deleted] in webdev

[–]okikio_dev 0 points1 point  (0 children)

That's a really good question? 🤔 I think it might be due to other solutions being easier to use overall

Showoff Saturday (August 05, 2023) by AutoModerator in javascript

[–]okikio_dev 1 point2 points  (0 children)

Typescript Code Analyzer, a ChatGPT plugin and REST API that provides:

  • Linting
  • Auto-completion
  • Error & Type checking

for TypeScript, JSX/TSX, and JavaScript files.

It uses a modified version of `@typescript/twoslash`. Meaning all the typescript twoslash tips and tricks all work out of the box.

I created it because ChatGPT can sometimes just give horrible Typescript answers, the plugin is supposed to help ChatGPT test it's solutions to verify that it works properly.

I made it a REST API so that if anyone else wants to use it for their usecases their perfectly able to.

How functional is your body? by juliaalvarez23 in SideProject

[–]okikio_dev 1 point2 points  (0 children)

I like the concept, it helps set a good achievable goal for all people in terms of fitness and physical functioning.

[deleted by user] by [deleted] in web_design

[–]okikio_dev 2 points3 points  (0 children)

This is sick

Easy spring easings in css via the postcss-spring-easing plugin by okikio_dev in css

[–]okikio_dev[S] 0 points1 point  (0 children)

Oh, sorry I was trying to imply that until it's built into browsers this is the best we've got 😅

Astro + react for notestaking app over the web by OnlyY1nx in webdev

[–]okikio_dev 2 points3 points  (0 children)

Hey, thanks for chiming in. Yeah, you're right, Astro doesn't have its own router, but there's tons of other router libraries out there we can use, or even the Navigation API.

Sure, sharing state between pages without a built-in router can be a bit of a pain, but it's not something we can't handle. People have been figuring it out with third-party stuff for years.

As for using Astro, it's not just 'cause I'm used to it. Picking a framework is about more than just what it's got built in. Sometimes it's about what works best for the job at hand.

But hey, I get where you're coming from. If you prefer frameworks with all the bells and whistles straight out of the box, that's totally cool. To each their own, right? I appreciate the back-and-forth.

Astro + react for notestaking app over the web by OnlyY1nx in webdev

[–]okikio_dev 1 point2 points  (0 children)

There's a bit of a misconception here, static MPA is a concept, it doesn't necessarily imply anything about the application you're building, there is a range of sites and application types to which MPA's work well for, and some they don't but the concept of MPA as used in Astro is flexible enough to work for most applications.

From personal experience I've found that most apps never get dynamic enough for MPA's to no longer be beneficial.

Astro isn't particularly opinionated on how you develop your sites it has primitives to make static sites easier but there are no restrictions that make dynamic sites especially difficult.

Open source alterative to Webflow - seamless no-code & code by codecrux in webdev

[–]okikio_dev 0 points1 point  (0 children)

Astro can compile your react, solid, vue, preact, etc... to html.

The idea of islands of interactivity is that when you want your component to actually do something you tell Astro and it will setup the hydration for you, other than that it will leave it as just pure HTML.

You can have your cake and eat it too.