IMHO, it's a matter of not being familiar with such way of writing code. Once you wrote a few lines yourself, it becomes much easier to read such code.
Anyway, I'm advocating to use it with caution, not in a "pointfree all the things" manner.
152 karma · joined December 11, 2014
Anyway, I'm advocating to use it with caution, not in a "pointfree all the things" manner.
RxJS's pipe: `stream$.pipe(map(x => something), filter(x => something)`
The article: `stream$.pipe(map(pipe(something, somethingElse))`
You can actually remove a friend - just slide the list to the left.
I think it depends on one's personality. I wrote the app because I needed something like this myself. There are many friends that I love to meet but I don't because of poor time management on my side and/or bad memory. The app is meant to help in such cases.
Hmm, I'm not a native English speaker and the similarity didn't occur to me. Might not be the most fortunate name after all... ;)
I will add some text to show in case of empty list. I agree the button (FAB) is difficult to find on large screens but it is part of the Material design guidelines (https://material.io/guidelines/components/buttons-floating-a...). I will think of some other approach.
The implementation in the tutorial is just an example - I wanted to provide a starting point for people who want to do something more complex.
I agree on the first point. As to the second, I didn't mean that having flatmap is the reason why we can combine Options and Lists. I meant that Options are composable with other Options and Lists are composable with other Lists.
I understand the problem of working with different monads. I looked into monad transformers at some point and found them difficult to work with so my approach now is to avoid mixing monad types (for example instead of having Future[Option[T]], just use a failed Future instead of None).