4 ms·
I wouldn't worry. Even the simplest and most friendly effects library: https://effect.website https://effect.website Shows clearly why they will never be a mai
by threeseed 1y ago
I wouldn't worry. Even the simplest and most friendly effects library: https://effect.website https://effect.website
Shows clearly why they will never be a mainstream concept. The value proposition is only there when you have more elaborate concurrency needs. But that is a tiny fraction of the applications most people are writing today.
- lblume 1y ago> the simplest and most friendly effects library Highly unlikely. JavaScript simply isn't a language built with this kind of evaluation model in mind, so an external library introducing completely orthogonal concepts surely should not be modeled as "most friendly". Don't get me wrong — Effect can be great! But the library also deliberately does not market itself as simple, rather as modular and multi-faceted, a "toolbox" from which developers may (should?) choose some tools and omit others. A language that supports effects first-hand, like the proposed "Ante", would provide a much a more expressive, possibly simpler, and definitely friendlier approach than TS effect ever could.
- marcosdumay 1y agoYeah, if you impose that effects must only be used to enforce code correctness, then only code that is hard to write correctly will benefit.
- deleted 1y ago[deleted]
- codethief 1y ago> The value proposition is only there when you have more elaborate concurrency needs I see the value every day when I look at a shitty piece of JavaScript or Python code that secretly modifies some global state behind the scenes. Or when I want to do dependency injection without resorting to frameworks doing some magic. Yes, I could drill my dependencies through the entire call stack, and often do because it's nicely explicit. But stuff like `logger` really doesn't belong in the function signature if it can be avoided.