igal.dev
@prisma.io sw eng. @kysely.dev co-lead. @zod.dev contributor.
🥰 TypeScript, FaaS & DBs. coined Tofu (OpenTofu). opinions are mine.
github.com/igalklebanov
523 posts
861 followers
369 following
Regular Contributor
Active Commenter
comment in response to
post
100% the neon dude.
comment in response to
post
we have @pkg.pr.new for that. pushing preview builds for PRs, the long-living `next` branch, etc. people can play around with these or the playground.
there were a few times where we rolled back and redesigned an API idea before release. if that would have hit `latest` on `npm` prematurely - ouch.
comment in response to
post
prepare for support hours? 😬
comment in response to
post
from a perspective of someone who doesn't read the docs. 🫠
comment in response to
post
it's out!
comment in response to
post
that's more of a comparison between an orm and a query builder. you needed an orm. it's fine.
you were not "holding it right" in some parts, and complaining about sql more than about kysely.
unmatched type-safety.
github.com/thetutlage/m...
comment in response to
post
dynasty.
comment in response to
post
omg, so many times.
comment in response to
post
in other words, what are the queries you're gonna execute on this table? what `where`s are you using?
e.g. if all you do is `where a = ?` and `where a = ? and b = ?`, all you need is a composite index `(a,b)`, probably*. 🤞
* - run some `explain`s to see actual query plans to test assumptions.
comment in response to
post
what are the access patterns?
comment in response to
post
query builders to the rescue.
comment in response to
post
github.com/thetutlage/m...
comment in response to
post
לגמרי. החדר-משרד שלי קפוא. זה מחרפן.
comment in response to
post
🙌
comment in response to
post
using ai nowadays even tho you know it wastes your time more often than helps you:
- fear of being left out - if it ever becomes good good.
- fear of not holding it right and "they" will find out. a new form of imposter syndrome.
comment in response to
post
nah bro, we see you. 💪
comment in response to
post
your mileage may vary. 😬
comment in response to
post
some heroes don't wear capes.
comment in response to
post
it uses a library with wish.com level type-safety.
comment in response to
post
am i being followed? 🙀
comment in response to
post
we also need to verify that faas vendors ship `require(esm)` enabled node.js environments i guess.
comment in response to
post
too soon. lots of brownfield codebases still on cjs setups that are painful to migrate (both technically and politically).
i'm for shipping dual until node.js versions that don't support `require(esm)` reach eol.
comment in response to
post
these template coc's are too wordy for them, and too much work for us.
comment in response to
post
i'll investigate. don't expect this thing hitting core.
comment in response to
post
write a dialect, or kysely.dev/docs/recipes... into cf's api.
comment in response to
post
league involved. gotta be.
comment in response to
post
"type-safety". 🫠
comment in response to
post
tough love makes michael jacksons. 🫠
comment in response to
post
the op's about people who follow randomly, to get follow backs, and unfollow you if you don't. that's weird behavior that existed for ages in other platforms, e.g. soundcloud, but really doesn't make any sense in this context.
comment in response to
post
i normally follow people i know personally (for the same reason), but also follow high profile people from the ecosystem - the feed shows if they create a new project, star a project (can find out about something before it trends), a repo's stars view has a tab for people i follow.
comment in response to
post
yeah got confused as well. needs simplification - things that get installed during `npm i` (which are split into things that are used in your app, and tools used in CI - both dangerous), and things that don't.
comment in response to
post
build time runs in CI and is possibly exposed to production secrets.
comment in response to
post
but do they use them? 🫠