https://en.m.wikipedia.org/wiki/Myers%E2%80%93Briggs_Type_In...
1,057 karma · joined July 26, 2020
https://en.m.wikipedia.org/wiki/Myers%E2%80%93Briggs_Type_In...
Do you think the banks are going to foot that bill? Of course not: it's us, the consumers.
Are you willing to have everything be a bit more expensive, for everyone, so that you, apple users, can have something a tiny bit more convenient?
If anyone else is interested, the app's website is https://trackercontrol.org
https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
Is there any reading on that? I'd love it to be true.
Has some reviews floating around the internet: https://metro.co.uk/2021/01/22/alcohol-free-spirit-sentia-pr...
The creator, David Nutt, has a long history of trying to bring attention to the problems alcohol brings.
George Carlin said, "Have you ever noticed that anybody driving slower than you is an idiot, and anyone going faster than you is a maniac?".
I think this thought applies to directedness as well.
Unless someone has real data on this, I'll keep to my anecdote of having worked with dozens and dozens of people from all over Europe and the Americas, and I can count with one hand how many people were actually productively direct and not just rude and immature.
I think I get the point you're trying to make, and I find it difficult that someone could make a list of all the things that "should be in by default" vs providing the building blocks.
People often compare it to P5, but somehow the first thing that came to mind when looking at it the first time (probably over a year ago) was D3, and that's some pretty high praise in my book haha
I do think this is about understanding, as it's not about syntax, or what feels nicer. It's about building blocks and what comes before what. Given the nature of the proposed library, to give the users an arbitrarily less abstract construct is a design mistake as I mentioned in another comment in this thread.
For example, I remember when I needed to flatten a bidimensional array in JavaScript, perhaps back in 2005, and the internet told me that I needed to flatten the array. So I learned then that array.flatMap() served that purpose: to flatten a bidimensional array. This is of course incorrect, but it took me many years until I found the concept again and understood what were the building blocks around flatMap, and what kinds of other abstractions it allowed.
I meant specifically the lack of flexibility in some regards because of the missing of monads and friends.
For example, we have a few newer languages, TypeScript and Kotlin come to mind, implementing the "null operator":
thing?.fieldA?.fieldB
While this is quite handy, and people unfamiliar with the Option monad will think that this new syntax is really cool, it poses two limitations:
1. It doesn't compose with other abstractions
2. I can't use this for my own abstractionsIf the language designers had chosen to take one step back and implemented it in a more generic way (in some sense, in the same as my other comment in this thread about implementing "map" without "reduce"), the feature could've still been implemented in the language, but without the limitations.
I'm not sure what you meant with this point:
> people lamenting the lack of monads in Java.
Do you mean that, because you don't see people lamenting, it's not a useful feature?
Despite our wishes around that, functional constructs do have a hierarchy of abstraction vs power, and skipping a layer is the type of design that backfires in the end, like with Java doubling down on the collection APIs without introducing monads explicitly for users.