hotshoe · HackerTrans

3 yıl öncediscuss

React on the front-end because of eco; Fastify on the backend w/ Postgres. I host React w/ Remix for light-duty SSR, but real work gets done on the backend. I'm moving away from metaframeworks as single solution -- they're easy, but keeping biz logic on the be makes it much easier to swap out fe and better for testability IMO. I'll prob shift over to Solid once / if Start ever ships, else Qwik.

hotshoe

3 yıl öncediscuss

Seems like it always took me 3 steps to plug in a usb-a cable.

1. Doesn't easily insert so assume I've got it upside down. Flip. 2. Still doesn't easily insert so inspect, and realize it had it right the first time. 3. Insert for real this time.

I don't miss usb-a, but it was a vast improvement over the rs-232 and parallel port cables that preceded it.

hotshoe

3 yıl öncediscuss

React-aria hooks provide freedom tailor your own components w/o needing to work around the limitations of general purpose controls, while retaining correct interactivity behaviors (the hard part). React-aria has steeper learning curve but well worth it IMO, as I spent more time working around/hacking UI frameworks like MUI, Mantine, etc., to fit my needs that just comes naturally w/ react-aria. There is also react-aria-components (RAC) that went beta a couple weeks ago, which Adobe team is pushing at the start point, use hooks only when needed. Since RAC is just glue on top of hooks, only small incremental hit to bundle size, and lets you have cake and eat it too (e.g., I'm now using RAC 80% of time for declarative approach, also unstyled, and hooks for special cases). If want styled, can go spectrum -- also layer onto of hooks, there ay many options

hotshoe

3 yıl öncediscuss

One minor correction (sort of), just noted in docs that kysely provides a built-in camel case plugin, for transforming camel to snake case so, eg.g, createdAt to created_at in db. Not as flexible as arbitrary transform but it serves my needs perfectly.

hotshoe

3 yıl öncediscuss

I've been evaluating both (kysely, drizzle), and I'm leaning towards Kysely. Drizzle is the latest, but both are moving fast if you look at the git insights. I find Kysely more enjoyable and straightforward -- intellisense autocompletions work better (for me at least), and the expression builder combined w/ helper methods like jsonArrayFrom offer a lot of flexibility over how to shape the output, so you're in full control, which is one of the reasons I wanted to explore alternatives to primsa in the first place. I had actually decided on kysely, but am taking another look at drizzle because of recent support for relations added. The added support is a nice addition, but there's boilerplate one needs to write to take advantage of and, frankly, I just find it easier to get same results w/ kysely, again, w/ added flexibility (it is not trying to be an orm). Some things I really like about drizzle are not needing to generate schema and lets you map column names (e.g., created_at db col maps to createAt object name). Drizzle can also infer types from schema, but, I haven't found this to be a big pro relative to kysely because 1) it takes very little effort to build a zod schema that "satisifies" the kysely type definitions and 2) I'm overriding the drizzle inferred types anyway to get the finally runtime checks implemented (e.g., is a cuid2 of 16 len, not just is a string). I've also been using prisma-kysely, which gives me ubiquitously supported prisma tooling for handling migrations, etc.

edit: while not exhaustive, I'm seeing better perf (by about 20%) using kysely compared to drizzle for identical queries on planetscale. Take this with a grain of salt since I've made no attempt to measure exhaustively, or optimize -- just using "as-is" so to speak, but thought it would be with noting and nothing to indicate to me that drizzle offers big perf improvement over kysely as has been suggested. Thanks for this post btw. Drizzle is hot and shiny right now (Theo just promoted big time), but after taking a second look at drizzle and in the process of writing up my thoughts here, it's become clear to me that I'm sticking w/ kysely.

hotshoe

3 yıl öncediscuss

Remix for me. Tried the new shiny objects (solid, qwik, svelte) and made it pretty far, but ecosystem just isn't there yet and fond myself spending more time making up for the gaps than worth the benefits these platform offered. Nextjs appdir is half-baked right now and handling of mutations is a joke, so you're left on with stable/pages version, knowing you're incurring technical debt with every line of code written.

comments