It's been about 4 years since I've used Briar, so take this with a grain of salt, but I found it extremely useful at an event where I was normally within WiFi distance of my friends, but we didn't have cell service. Like, we might be in the same conference room, just not actually near each other, and the site had shoddy internet service.
If we could connect to each other's phones as "hotspots," we could send messages over Briar that wouldn't get through any other way.
It also worked well with a local mesh net set up around the conference location for file sharing, but that didn't have internet access.
Not the intended use case from what I understand, but it worked surprisingly well, and better than the goTennas we tried the year before!
It's a good intuition. Indeed you can see it as ReaderTaskEither (albeit on steroids).
The fp-ts author is also an effect maintainer and recommends effect for new projects. fp-ts is not dead, but it's core goals (providing Haskell/PureScript-like types and type classes) have been mostly achieved.
Effect is an ecosystem with different goals from fp-ts.
This is for all intents and purposes, fp-ts 3. The projects essentially merged, Giulio Canti is working on it and fp-ts 2 is renaming methods to ease the transition to it.
Thanks, it renders a bounding box around each word that is recognized, you can then click on the box to fill it. It's very accurate if you give it an image with visible structured text.
> Notice how we're not using the ruler for measuring anymore. Instead, we're using it to represent the sizes of different objects.
Viewed like this, the fact that it uses inches vs m isn't significant, because 'inches' translates as 'units'. Even as a Brit, I can't imagine 1000 inches either, but I can tell something about two objects that are respectively 1000 vs 1200 inches/units.
