More to come at TDC Floripa!

We will also be on stage on June 13, this time in the JavaScript & Node.js Track, where our Software Architect, Talysson Oliveira, will explore functional programming in TypeScript using Effect-TS—a rising library that combines performance and pragmatism for scalable applications.

A must-see session in the JavaScript & Node.js Track!

#Codeminer42 #TDC2025 #TypeScript #EffectTS #FunctionalProgramming #JavaScript #TechEvents

#EffectTs has a pull stream on i/o for both the CLI and node commands coupled with a composable API.
Knots that can be untangled, in other words.
My go to things now are #Typescript #EffectTs for anything that might get out of hand and #Babashka to pipe things around shell land.

Way deep in the \@effect/platform repo there's an example on how to use their HttpClient api

#EffectTs

https://github.com/Effect-TS/effect/blob/main/packages/platform/test/HttpClient.test.ts

effect/packages/platform/test/HttpClient.test.ts at main · Effect-TS/effect

An ecosystem of tools to build robust applications in TypeScript. - Effect-TS/effect

GitHub
Turns out I was wrong and there are things you can do with #Arrowlets that you can't do with #EffectTs.
Now in Fletcher, the Work type is just Effect<never>
Overloading the monad interface so you can call it one of two ways is deeply cursed imo.
#Typescript #EffectTS
Cannot get my head around how to get the input in #EffectTs. Writing effects that use the R value directly seems impossible by design, and I can't figure out what juju the Effect.custom function requires, even through the flatMap implementation seems so straight forward.
There's an old #React adapter for #EffectTs in #Typescript, I'm wondering if I should bring it up to snuff.
Also noticed they don't have an EventTarget effect, that I definitely need.
Like seriously, wat? #EffectTs