The front end framework for correctness: built on Effect, architected like Elm
31–40 of 53 posts
Re: The front end framework for correctness: built on Effect, architected like Elm
#32I don't know, as far as I can tell the demo on the homepage is bugged? Or maybe I misunderstand how it's supposed to work? If I click reset after 2 seconds and then click add 1 right after it, the reset never fires. What's up with that, that's not what I expected to happen?
Re: The front end framework for correctness: built on Effect, architected like Elm
#33Re: The front end framework for correctness: built on Effect, architected like Elm
#34How is Effect, for those who have used it? It's good that algebraic effects are becoming more mainstream.
Cons: The API surface is huge so there is a steep learning curve.
Re: The front end framework for correctness: built on Effect, architected like Elm
#35Earlier quoted context omitted.
I use it from years, it's the only sane way to write typescript. The learning curve is steep tho. In any case it's a hard technology to sell, you don't appreciate it from hello worlds. In fact you hate it for trivial programs. It shows it's benefits at scale. Lots of tools like T3 and opencode use it at their core because they solve non trivial problems made of queues, retries, dependency injection, schemas, etc. I'v…
T3? Isn’t T3 just a TRPC boilerplate kinda thing?
Re: The front end framework for correctness: built on Effect, architected like Elm
#36I don't know, as far as I can tell the demo on the homepage is bugged? Or maybe I misunderstand how it's supposed to work? If I click reset after 2 seconds and then click add 1 right after it, the reset never fires. What's up with that, that's not what I expected to happen?
Re: The front end framework for correctness: built on Effect, architected like Elm
#37I don't know, as far as I can tell the demo on the homepage is bugged? Or maybe I misunderstand how it's supposed to work? If I click reset after 2 seconds and then click add 1 right after it, the reset never fires. What's up with that, that's not what I expected to happen?
Re: The front end framework for correctness: built on Effect, architected like Elm
#38I don't know, as far as I can tell the demo on the homepage is bugged? Or maybe I misunderstand how it's supposed to work? If I click reset after 2 seconds and then click add 1 right after it, the reset never fires. What's up with that, that's not what I expected to happen?
Agreed - I hit "Reset after 2 seconds", I hit "Add 1", and sure - it adds one, but it also unexpectedly cancels the reset. Which I don't expect from the description, and I also don't expect from the code. --- So outside of the simple "This is broken..." feedback, I want to further pick on this example: Don't fucking hide the imports. Especially don't fucking hide the imports if you're showing example code, and you're…
Re: The front end framework for correctness: built on Effect, architected like Elm
#39The project seems super interesting and I've been following since the creator went on an effect podcast I listened to. My only gripe/concern is the fact that the docs are so glaringly AI (likely claude) generated which is something I've come to not expect from technical documentation writing specifically. All in all though, the verbosity tradeoff for explicit design choice here is the right one and I think it does be…
a) Actually ship docs, and use AI to help (I also do a ton of hand editing and review cycles)
b) Have poor docs coverage because I’m handwriting everything
I’ve chosen A, but plan to do a few weeks of docs rewrites before I ship 1.0.0. I would rather it sound like me.
Re: The front end framework for correctness: built on Effect, architected like Elm
#40The project seems super interesting and I've been following since the creator went on an effect podcast I listened to. My only gripe/concern is the fact that the docs are so glaringly AI (likely claude) generated which is something I've come to not expect from technical documentation writing specifically. All in all though, the verbosity tradeoff for explicit design choice here is the right one and I think it does be…