Probably better wait for them to reach stability first

From a recent discord discussion: depends what you mean by performance, many times performance bottlenecks in JS are due to bad management of concurrency, thanks to structured concurrency and observability it becomes much easier to spot and optimize those issues. There are apps in frontend running at 120fps that use effect intensively, so most likely effect won't be your perf problem. In regards of memory, it doesn't use much more memory than a normal program would, there are a few more allocations compared to non effect code but usually this is no longer the case when the non effect code does the same thing as the effect code. The advise would be start using it and monitor your code, optimise out of need not out of thought, optimizing too early is the root of all evils in software design

@@michaelarnaldi6680 Those are some interesting points, thank you.

RxJs is first and foremost "just" Observables. Effect offers streams but that's just a teeny tiny group of modules in relative terms when compared to the scope of Effect which is a full blown effect system, standard library, schema encoding&decoding, dependency injection, etc. etc. etc. (the list goes on and on).

It's so unintelligible that without having wrote a single line of Effect code you correctly understood what it does :) (ofc learning to write it is a different task, it is like learning anything new, think of learning React for example). I think the main issue here is understanding of "pipe" (normal as it is not a standard) that is function composition, so a.pipe(f, g) is g(f(a)),. In the code snippet everything but the first line is a Higher Order Function that modifies the behaviour of the original effect, in short, line-by-line: 1) creates a request 2) declare that we are interested in the success response and we want to fail otherwise 3) after the response is successful we want to extract the json of the body 4) declare that we want to timeout after 1 second 5) in case of failures we want to retry using an exponential backoff policy 6) we want to instrument the call with an opentelemetry span named getTodo with attributes Note that Effect is lazy, meaning just invoking that function won't do anything, only when executed effects actually occur, so you can change behaviour such as saying "hey, for this code I want it wrapped in a try-catch and want to print the error" or really any other kind of behaviour change, think of it like templating a program rather than issuing a sequence of instruction. The same code without Effect is about 200 lines and it is almost impossible to understand what is going on when reading it.

@@michaelarnaldi6680 I'm starting to get it now, thank you. Looking at pipelines the "Elixir" way really cleared up any confussion that I've had with this snippet, looking forward to trying out Effect!

Given that you can use it even for small parts of an app it is more akin to a library, that said if you use it for everything it can feel like a framework

Effect has `@effect/schema` for this instead of Zod.

You didn't watch the video carefully, the slide even says you don't need zod.

They are compatible indeed, we have production users of both, Effect runs everywhere that JS runs. I guess the reason logos weren't there is just because of space

LOL