and i would like to reiterate that we love effect and we think you should use it whenever you can.
refreshing that civilized exchanges can still happen on this hellsite.
Wanted to share a few thoughts regarding the Effect part of this discussion, starting with saying that I do broadly agree with everything that was said and that's exactly why I'd like to add some "maintainer" perspective on the choices.
Congratulations to the whole team @namespacelabs !
We swapped out GitHub actions runners for the @EffectTS_ project with Namespace's runners and we haven't looked back.
Fantastic product and can't wait to see what's next from the team!
Today, I'm excited to share that we've raised a $42M Series B led by @scalevp, with participation from @NEA, @20vcfund and others, bringing our total funding to $65M.
The next 100 billion commits are coming faster than any infrastructure was built to handle.
We're building, from the ground up, the developer platform for this next wave of software development.
We already power software development for @SpaceXAI, @tryramp, @ElevenLabs, @SierraPlatform , @framer, @TrustVanta, and more than 1,000 of the world's most ambitious companies.
In the last 12 months, demand has surged, with total revenue growing 8x. We will use the funds to accelerate product development, expand our data centers, and continue hiring world-class talent.
This Week in Effect #138
→ Effect 4.0 Official Release
→ Cluster, Part 1 - Module of the Week 3 by @maxwellbrown
→ @RhysSullivan has shipped more Effect in production than @dillon_mulroy
More below:
https://t.co/Xjubj6Amu3
@refactorordie@foldkit Since you can use Effect as you would normally, you could probably leverage the Reactivity module or build a custom service. @devinjameson any other ideas on this?
I don't think the point about indentation matters at all - Foldkit code is still highly reviewable.
@refactorordie@foldkit I think mostly what I've heard so far is "This looks amazing ... but it's not React! And the React ecosystem is too good to leave behind!". I've left my thoughts on those points in other replies.
@keel_zy@foldkit As I’ve said in other replies, this is just a matter of time, and I don’t expect it to take long to get to a point where Foldkit is competitive in its ecosystem.
In January we started using the Effect 4 beta on the backend. Last week, we fully switched from a mix of Fastify + zod + tRPC + Sentry integration to one merged Effect Http router + native @sentry support. Halved our p50 response time and less memory leaks. Next up: the frontend!
We rebuilt the Effect v4 runtime from the ground up.
In our benchmarks against v3:
→ 5× smaller bundle
→ 6.4× concurrent task throughput
→ 86% less memory per fiber