Rody

For all time, always ✨

[Rody @rodygosset]

Happy to share I’ll be speaking at React Paris 2026 !

[React Paris Conf' -by- BeJS @BeJS_]

The Full Conference Speaker Lineup ➕ Agenda are Live! 🔥

The ultimate #ReactParis 2026 squad is here; ready to blow your mind with cutting-edge #talks, deep dives, and game-changing insights.

ℹ️ All you need to know about this 2026 edition #programme 🧾 in the first comment 👇🏽

[Rody @rodygosset]

@devinjameson Awesome ! Looking forward to watching it if it’s recorded

[Rody @rodygosset]

@filipfalcon @foldkit Very cool !

[Rody @rodygosset]

@theo @TejasKumar_ Lakebed ?

[Rody @rodygosset]

@harrysolovay @jdegoes @devinjameson @ariazou Will the talks be recorded ?
If so, looking forward to that !

[Devin Jameson @devinjameson]

The latest @foldkit Blocks + Effect Layers preview is ready. I’ll keep refining it as feedback comes in.

What’s new:

- Simpler root setup: compose your application from Blocks, then pass the root ApplicationBlock to Program.make.
- Cleaner child OutMessage policies with better inference.
- Better support for optional children with keyed identities.
- Separate guides for migrating from stable and upgrading an earlier preview.

Installation instructions and copyable migration prompts are in the PR description.

https://t.co/6qXgWzhd0U

[Rody @rodygosset]

@devinjameson Valid point !
The “make” prefix makes the naming coherent with the actual meaning of each operation.

It does help hammer the “blueprint” analogy (constructing your program as values that are then passed to a runtime for execution).

[Rody @rodygosset]

@devinjameson I feel like this naming pattern would make app code easier to read, remove load / friction

[Rody @rodygosset]

@devinjameson Yes exactly! Sorry for the lack of clarity

[Rody @rodygosset]

@devinjameson For the core composition APIs, could namespaces and the receiver carry more context?

For example:
• Application.define(…) / Block.define(…)
• definition.bind(…) / definition.compose(…)
• composition.init(…) / .update(…) / .view(…)
• https://t.co/ShdWVqZ7En(…)

[Rody @rodygosset]

@devinjameson Next question: could EffectsLayer just be layer, or is there a specific reason for this specific naming ?

[Rody @rodygosset]

@devinjameson @anfi_ttv @maxwellbrown @foldkit @alchemy_run Slowly haha,
It works very well for basic use cases,
But to be honest, the more I consider it the more I come to the conclusion that it is taking the direction of a “we have Foldkit at home” experiment.

Just like Effect, I feel Foldkit is most beneficial when adopted fully

[Rody @rodygosset]

@theopomies @EvrygDotCom @EffectTS_ @topheman @jbmusso Yeah it definitely was

[Rody @rodygosset]

Had a good time !

[Antoine Coulon @c9antoine]

@EffectTS_ Paris #7 is now live 🔥

And starting with @rodygosset explaining us how Effect is a good fit for all sizes of apps!

First edition being recorded thanks to Inato folks, be ready for the replays 🎥

[Rody @rodygosset]

@thefubhy @EffectTS_ Very cool

[Rody @rodygosset]

@c9antoine @MirelaPriftix @devinjameson @EffectTS_ @EvrygDotCom I can do mine in English any time haha

[Rody @rodygosset]

@samgoodwin89 1) what

[Rody @rodygosset]

@devinjameson @c9antoine @EffectTS_ @EvrygDotCom Yeah ! Super excited to share my thoughts on the case for defaulting to Effect in most projects

[Antoine Coulon @c9antoine]

Back to @EffectTS_ community work in Paris next Tuesday with the 7th edition! The edition will probably be the first one ever recorded in Paris thanks to Inato folks 🔥🎥

Rendez-vous 7pm at @EvrygDotCom, 4 great speakers, 4 great talks ahead!

Registration link in comment 👇

[Rody @rodygosset]

@devinjameson Thank you ! Happy to contribute