Matteo Scotto

eng @InboxApp_

[shadcn @shadcn]

No model survives the "are you sure?" They all fold instantly.

[Matteo Scotto @442utopy]

@0xblacklight alright gonna try it today!

[Matteo Scotto @442utopy]

@joebell_ super curious, how do you make this composable?

[Matteo Scotto @442utopy]

@samgoodwin89 i really like the TemplateStringsArray trick to get the typesafe refs, nice stuff!

[Matteo Scotto @442utopy]

@samgoodwin89 lovely

[Matteo Scotto @442utopy]

The docs are still completely wip
Would not recommend them right now, but if you have your anti-slop shield ready: https://t.co/pPyfLsrHNG

[Matteo Scotto @442utopy]

`effect-orpc` brings Effect-native procedures to oRPC!

Bring typesafe services, effectful middlewares, yieldable errors and more.

Already used in production at multiple companies.
The branch for effect-v4 is already available as a pre-release.

Start with a very simple `eos` procedure:

[Matteo Scotto @442utopy]

Here's the source: https://t.co/RCE1doGR23

[Andrew Sherman 🇺🇦 @andrii_sherman]

We need to bring more attention to the situation we have with npm. Drizzle releases are completely blocked by npm because of "too many published versions" (we have 1397 versions)

There is no way for us to delete old versions, unpublish old versions, or really do anything except contact the support team. Of course, we did that >3 weeks ago, but there has been no action from the npm team at all. Drizzle has >11.5M downloads/week and is used by hundreds of thousands of developers across the globe, yet we're getting no help from npm

It's not like only 10 people are blocked. There are many teams and developers waiting for us to ship important features, improvements, and fixes (Imagine receiving a security report in this situation and having zero ways to release a patch). Npm support keeps sending bot replies saying they need more time to handle the case

I'm begging someone to help us find anyone from the npm team who can help us delete old versions that are not used by anyone anymore, or at least give us a way to ship releases again

ps why is having 1397 releases a problem at all?

[Matteo Scotto @442utopy]

@Neolectron bahaha

[Matteo Scotto @442utopy]

@KevinPicchi perso j'ai déjà une bonne partie des contenus sur insta qui sont auto translate, avec la bouche qui s'adapte etc c'est assez ouf

btw le papa Suisse très chaud en horlogerie c'est merveilleusement cliché, j'adore

[Matteo Scotto @442utopy]

@badlogicgames I read there is a refactor going on for the extensions APIs, do you have any shareable ETA?

Will it allow to further more customize the UI? It's really something I wish to have more control over to make it feel more like home

[Matteo Scotto @442utopy]

@dinwwwh yes! Sane defaults with control > bare api

[Kyle Mistele 🏴‍☠️ @0xblacklight]

@MichaelArnaldi @SickBots @EffectTS_ one refactor at a time ☠️

the nice thing about effect-orpc is we can adopt incrementally and have the router split between effect and vanilla oRPC procedures and the client and contract don't have to care

[Matteo Scotto @442utopy]

@stephenhaney to be fair, I don’t expect the design tool I’ll be using for the next 10 years to have been built in just a few months anyway

it’s already hard enough to build a good tool that actually brings something to the space, let’s not make it harder by racing against the clock