The front end framework for correctness: built on Effect, architected like Elm

epolanski 4 hours ago|

I love both effect and elm, but I cannot swallow yet another Vue/React crap even if it adds effect niceties.

Especially after having used ruby and elixir extensively after years of react/Vue, it feels so backwards (and LLM unfriendly) to split front and backend unless you have gargantuan reactivity needs (you don't).

I wish JS offered just one proper server side focused frontend solution.

hnsmomdpvp 5 hours ago||

Finally someone said it

oofbey 5 hours ago||

As agentic coding matures, this kind of project is the right direction. The mechanics of writing the code become less important. But having a language framework that naturally resists mistakes will become increasingly useful and important.

Similar to how Rust is obviously a better choice today than C++. Who cares if the language is “more difficult” to code in, if the agents are doing the coding. What we need is building blocks that make it harder to author bugs.

dflock 5 hours ago||

That's an interesting - and maybe correct - point. Looking at the examples, it seems very long winded and not something I would want to write myself - but maybe I don't need to care about that anymore, as you say!

Multicomp 3 hours ago||

This time around in the pre-covid days, F# had a surge of popularity, there was Fable and Giraffe and an elm-style set of frontends (the generic pattern is called MVU - Model View Update), it didn't take off because A) we are still a trend/fad-driven industry and B) there was no AI to help hold your hand in refactoring all of your apps.

These days? Doing this FE SPA framework for Effect/typescript familiarity or Fable for F# familiarity and a model-view update pattern can help one do CQRS better, force you to think about stronger Hexagonal Architecture patterns, and overall help your application care about long term correctness more without you having to hand code every discriminated union as such.

The LLM can't replace you, but it can be an enzyme that lowers the activation energy required to switch from bad old MVC mutable tag soup to MVU frontends with strong data interface designs held in sqlite-dbs-per-aggregate (if you are of a DDD or event sourcing taste, which this pattern does not require!)

triyambakam 4 hours ago|||

I was thinking about agentic coding as well and a few years ago I probably would have really been interested in this project. But now it sits at a lower abstraction where I care less since the agent is the one managing it. It's strange

whattheheckheck 5 hours ago||

And tla+ / sequence diagram / user flow diagrams / data models all in one "thing"

hey_lalit 2 hours ago|

[dead]