Відео

I watched this because someone power scaled monad and put it against gogito

Still don't get it but less!

My favorite thing about pop up box captchas is when the traffic light barely stretches into the neighboring box by a pixel or two, and I don't notice it and need to do another one where the question is "select all horses made of clouds"

That code didn't really look that bad, I guess its because Im a game developer? I dont know.

The problem with your video is that you spend 80 seconds establishing the problem to be solved, show the solution exacly 3 seconds (from 1:18 to 1:21) and then wrap up. You need to first focus on where you put the check, then explain why it's better there.

Can you make more videos on category theory

Wow really well explained.

I wish Mathematicians used lambdas, currying, and partial applications more often, and were more familiar with type theory and proof assisting compilers such as Coq, Agda, and Lean4. Perhaps if highschools offered 4 years of programming in the same way schools offered four years of math, we could see more Mathematicians lean towards constructivism.

I do find it funny that you mention how companies being able to scrape data is a problem, then advertise a company doing that. The only reason that company exists is because it can get more data this way than if they were just doing everything themselves. (Because users will choose targets they never would have.)

Use Kotlin! There is null not the default.

Neither Monads nor Functors are a design pattern.

Very nice. Covered the basics in a very very short time. Keep it up.

Just in cay you don't really know the topic already: 0,5 playback speed might help to reveal some sense.

It is weird to put a precise mathematical name to my preferred pattern of programming. I always preferred monads over other type of functions such as functions that change given output parameters. Now I can sound very pedantic when talking about my program at work: "So the attribute function filter is a monad of the class. Any questions? Oh, of course, I will explain what a monad is. A monad of X is a monoid in the ..." My dream come true!

I believe the exampled code is wrong syntatically. Given that it is conceptually also not a monad but a functor. This lefts us with a wrongly titled and wrongly coded video.

In your JavaScript example, why didn't you make use of the null aware operator to safely access potentially null properties?

that's just an antibody smh

python cloud scraper seems enough

So basically; %>%

You were a single step from burst out laughing during the explanation 😂

I wonder how useful this would be in a large project, idk I feel like it would be less useful and it would break at some point

This... Is pretty cool, thanks!

I just wanted to learn more about monads so I could write better Rust code. 45 min later I've subbed and am on my way to watching the entire video catalogue.

Why is this superior to early return or ?. operator?

Made a video Made JS dev love Haskell JS dev tried Haskell (or any FPL) and died Saved the programming community Left

let firstFriendGender = database.fetch(username)?.friends?.first()?.gender; Here you go. Don't thank.

i thought that title was just gibberish and the video was a shitpost

And also, it's all about this: en.wikipedia.org/wiki/SKI_combinator_calculus

I can't believe I finally understand the shit! I've come across this years ago. I can't believe it had always been so simple. You've made me feel like a moron and a genius at the same time, congratulations

"fairly abstract"

more videos on DSA

In my world, >>= is a shift-to-right assignment

this category theory thing reminds me of group theory

Never met a Chanel this concise while remaining interesting and informational, btw I like your color schemes.

three boys in france, dind't eveen understood a single word lol

nice vid but endo is greek

Cool.

Perfeito!

I know I'm coming in late, but another nice minimal system is bitwise cyclic tag (BCT). Definitely worth checking out

A better explanation of a morphism maybe is like moving from a plumbing system of a city to the subway or electricity network, while mantaining some properties.

thank you

Most clear and concise explanation of monads that I've seen - amazing stuff

stames2319 saved me a bunch of typing by previously pointing out that a monad is not _the_ category of endofunctors (of X) plus an associative operator and an identity element of said operator but _one_ endofunctor with said extras. Now, I want to explain how this applies to Haskell because Haskell relies heavily on monads. Every Monad is a Functor … shouldn't that be endofunctor? Well, a Functor in Haskell is effectively an "endofunctor in the category of Haskell types and functions", so that resolves the ambiguity. That is, a Functor is a unary type function (kind * -> *) and an operation fmap :: Functor m => (a -> b) -> (m a -> m b) (The parentheses on the right are superfluous but I left them to make it clear that the type function m transforms types and fmap transforms functions to work on the transformed types.) Then we add an associative operator to get a monad, which we call bind: (>>=) :: Monad m => m a -> (a -> m b) -> m b with associative law: (m >>= f) >>= g = m >>= \v -> f v >>= g Note the lambda syntax (with the backslash and the -> arrow). We also need an identity element, which is called return (or pure, doesn't really matter, in Haskell) return :: a -> m a We then require left identity: return v >>= f = f v and right identity: m >>= return = m

Finally someone cuts to the chase and just explains it. THANK YOU.

I think the biggest misstep in this otherwise flawless video is this: right at the end, you blaze through all that math you've carefully built up and just assert that it is what it is in code. It's not clear what makes map an endofunctor, what the category is (Box or the object it holds?), or why we can call that a category. The transformation undergone through that endofunctor is also vague. Oh, and on second thought, I'm docking 10 points for sticking an undefined and totally handwaved addition operation in there between a value of type Box and the value returned from func.

After watching this video again after months and others of countless explanations + category theory, I think I'm finally beginning to get it

I am filled with regret for the day I became curious about what a Monad is after a computerphile video, so I searched for it, and now my feed is filled with Monad explainers that don't help me understand Monads. I've long since stopped caring, but keep being recommended more or less accurate-according-to-comments and jargon-heavy videos, this is my new hell. Thanks for trying, though.

Try and learn Haskell they said ... It will be fun they said ...

Merci de m’avoir aider ❤❤

thank you that was so helpful