shaberman

software developer

[shaberman @shaberman]

@jarredsumner @NathanFlurry my dream for tsc7 was "runtime innovation", not "rewriting in golang"🥲🤷-- love the innovation & hopefully this stirs competition from v8/hermes/etc. thank you @jarredsumner !

[shaberman @shaberman]

@KevinVanCott Sounds awesome! We used prototypes and Object.create for some nice perf wins 🚀 in Joist as well: https://t.co/0bW3ejEsLr

[Joist ORM @Joist_Orm]

New blog post on using `unnest` again our bulk SQL updates https://t.co/D84NlUyfew #typescript #orm #postgresql🚀

[shaberman @shaberman]

@naman34 Ngl, you should just clone our Truss/tachyons abbreviations, they're better & shorter than TWs. 🙊😁 See https://t.co/lH9NzmQk3p for examples. Being semi-facetious/semi-serious. :-) Ty!

[shaberman @shaberman]

@naman34 Fwiw the css.display.flex, css.padding._16px API is okay-ish; I get inline is a huge step for stylex philosophically (given emphasis on clarity), but imo it is too verbose. For inline to work, you need really brevity imo, otherwise the JSX gets sprawly.

[shaberman @shaberman]

@naman34 Oh wow! I'll follow that PR--it would be amazing if it accepted a literal { color: blue }, so I could pass our Css.df.p2.color(color).$ dsl into it, but understood static analysis concerns.

[shaberman @shaberman]

@naman34 Nice! That was my hope as well 😅, something like "scan for https://t.co/bQif9L1QEM.$" => rewrite to top-level stylex.create => replace with apply but keep spreads/conditionals -- would be really amazing! i love stylex's "just javascript pojos" philosophy🎉

[shaberman @shaberman]

@dhh Would be great to have a blog post with "here are the rows in the database" and how they change through a few scenarios.

[Corey Quinn @QuinnyPig]

Microservices are what happens when your organization has communication problems and you decide the architecture should have them too.

[shaberman @shaberman]

@anOrdoLiberal @brankopetric00 If their ORM was Joist, it would have never happened https://t.co/Si9uGVhA8j

[shaberman @shaberman]

@bunjavascript if folks interested in official datadog support for bun could upvote https://t.co/t1in3TOAnj, the ddtrace team is watching that to gauge community/customer interest; for us this is our last blocker to bun in production😅

[shaberman @shaberman]

@dhh have you tried https://t.co/4NucHsvWPD? Imo really great, scales to "more than a handful of windows" much better than the built-in master/dwindle layouts; without it I would have tried migrating my #omarchy setup over to Niri/another scrolling WM by now

[shaberman @shaberman]

@petereliaskraft @petereliaskraft can I use the same database transaction to atomically commit my entities & the DBOS workflow change? The simplification of "save business data & queue downstream work" being an atomic operation is a huge win for database-as-a-queue pattern imo.

[Joist ORM @Joist_Orm]

Joist has had a "dry run" mode, great for building "what if" or "oracle" features, that wasn't documented until now: https://t.co/ti6geln4Ty #typescript #orm 🎉

[shaberman @shaberman]

@petereliaskraft Ofc its not perfect, but @Joist_Orm solves N+1s. Other issues from the paper Joist also solves (uncached reads & inefficient updates) are imo well-suited for ORMs b/c it's very hard to organize business logic as adhoc, hand-coded SQL that doesn't suffer the same problems.😅

[shaberman @shaberman]

@jmeistrich Amazing idea! I'm porting our @Joist_Orm docs over to Starlight solely to copy/paste your snippet into our setup and get our own llms.txt :-) ty!

[shaberman @shaberman]

@jarredsumner tsc 7.0 will be great, but ngl I was hoping the big announcement was a collab of @jarredsumner @tmikov @AndaristRake @ssalbdivad and @ahejlsberg et al teaming up to make a static hermes/mojo-style runtime + language to make tsc 10x faster w/o the port. :-)

[ArkType @arktypeio]

Introducing ArkType 2.1, the first pattern matcher to bring the power of type syntax to JS.

Fully type-safe and up to 100x faster than ts-pattern🧵

[Daishi Kato @dai_shi]

Why We Use Reflect for Proxy Handlers
Valtio Uses It to Cover Rare Use Cases
https://t.co/NNVRuDljnd