At this point tofu states to be a set of functional recipies.
I think, we should establish a more specific philosophy, emphasize the certain problems, which tofu is aimed to solve.
A clearly defined set of use-cases would help to answer the "Why do I need tofu?" question and to determine the direction of future development.
Tofu for people who use monadic procedure tagless final encoding often
It has no united and forced vision.
It has no preferred way to create your application. You can apply tofuization to a small part of your code or write a small or a big application from scratch, they can be different and that's great
Tofu thinks that modularization is good, using tagless final sublanguages as modules benefit greatly
Tofu doesn't have a preferred platform, today we supporting Cats-Effect 2, Monix, and ZIO, tomorrow Cats-Effect 3, and even Project Reactor are on the go.
Tofu is build on the production experience, it doesn't attempt to catch its followers luring them using synthetic benchmarks
At this point
tofu
states to be a set of functional recipies.I think, we should establish a more specific philosophy, emphasize the certain problems, which
tofu
is aimed to solve. A clearly defined set of use-cases would help to answer the "Why do I need tofu?" question and to determine the direction of future development.