Great tutorial. NIGERIA stand UP!

Thanks.Nobody speaks about how to do unfamiliar tasks at all. This video is pure gold ..

@IjemmaOnwuzulike is there a part 2 ?

you use the word 'method' for a function, that is not really correct. An Object or a Class can have a method, a function lives on its own a is called a Function

How can we use .env file only with html, css and javascript without node. Or How can we hide our variable names or links in javascript?

Ijemma, Thank you so much for your videos. You're a wonderful teacher and an inspiration to all of us. As so many others have said, your videos are pure gold (this being the second one that I have watched). As you say, the map, reduce, some and every methods are so much easier to understand than the foreach method. A further simplification that they bring is that their result can (and should) be stored as a const (i.e. immutable) value, thus obviating the need to use a mutable let variable, as in the case of foreach. The latter is yet another complexity that we don't have to rack our brains over!

I like your way you teach by giving simple examples then go to difficult example. Is it also possible to speak a little slower?

great tutorial! thanks

Good video, you should make more videos, informative and clear

Great explains for begineers. Keep doing with live Example. Thank you a lot

Thanks for your vedio. Do you have next part of this vedio?

thank you so much

As a beginner, Python has really difficult documentation to wrap my head around.

Great that we push away responsibility and ownership 😂

Destructuring syntax 😂

Thank you so much.

Thank you so much. This is the best teaching on environmental variables so far

doesn't this unnecessarily bloat each cloud function that you export? for example, the dictionary cloud function includes every possible dictionary sub-function that you might need and when you make a change to one of those sub-functions, you must deploy the entire dictionary cloud function to update just a couple lines of code was this refactoring worth the tradeoff of more code per function and possibly slower start times?

Congratulations for the clear and easy going explanation! So far the best functor explanation on YT.

Coming back to this video to say it is amazing.

Very helpful and clear

You have excellent content. Pls keep making more videos. If you shift to Python I will sponsor you 😊

This is one of the coolest dev channel. Keep it up.

Best Functor video. Really simple.

Great explanation, helped me a lot!

when would you use forEach? What benefit does it have over a for loop

I actually understand now. Brilliant :) ❤

To be clear, if I push a project to GitHub and ignore the .env the .env file info will still be available for my page or, now that information will no longer be accessible through the git repo in terms of someone loading the app? Basically if I need an api for a map and it lives in the .env file, the api won't be accessible to the person trying to access the project from GitHub?

I love how you used your tips on how documentation should look like on your own video and made it clear concise and well sectioned, thank you so much for this video it was really helpful ❤

Functors are funky

Another useful part about ...rest syntax is destructuring: const obj = { a: "1", b: "2", c: "3" } // destructuring allows you to extract properties from an object const { a, ...rest } = obj console.log(a) // 1 console.log(rest) // { b: "2", c: "3" } // on the subject of destructuring, you don't have to extract `a` from `obj` as a variable called `a`, you can rename it: const { a: renamedA } = obj console.log(renamedA) // 1

This video is invaluable. Thank you for taking your time to explain FP concepts derived from category theory in a demistified, practical and clear way.

Thank you

Thank you fantastic explanation.

Just love your voice. Your lessons are great as well.

thank you very much! ❤

Calling this a functor is the silliest thing I’ve ever heard in my life

I really like array methods but I know that a for loop is better for performance. Because chaining maps and such, copies the array everytime and you need to create a closure object "() => {}" which also needs to be garbage collected. I really like how Rust transforms usage of chained array methods into 1 for loop under the hood. Making this declarative approach a syntactic sugar, which is best of both world: declarative for humans, imperative for the compiler. I hope the JS runtimes have or are going to optimise this.

nice is good and well, but... speed ? which way is fastest?

Amazing video ❤, like your style of explanation

This is the by far the best video on functors.

Great content!

Quick question: if I map to a different type, such as going from an array of strings to an array of ints, is it still a functor? If I do ["John", "Mary", "Kate"].map(name => name.length), thus changing the inner type, is it still a functor or a different kind of functor?

Excellent, precious video. Would you be so kind to do one about Monads? Please do one on monads. We desperately need one! Thanks 😃

KZbin auto translate is failing for me on this video. Could you add any translations to this vid? Seems useful.

I'm glad I found your channel it's a goldmine

Very clear and helpful tips for a very confusing topic!

Damn, super interesting tutorial!

This is really funny. This explanation of a Functor is really somewhat different from what I have seen from a C++ tutorial. To me it looks like a specific version of it, not the whole story. In that tutorial a functor was explained as an object that behaves like a function. It did this by directly implementing the function call operator, so that it could literally be called as if it where a real function. And ok, I know JS does not have operator overloading, so then it that map method and that then method are ways to replace that. But this is all not the issue. In that C++ explanation they where NOT talking about that whole identity rule, just about composition. They did not require that the created function should return a new data structure or a new functor, but the generated function was just returning a single value like an integer for example. Was that a wrong explanation? I would say, that identity thing is more important for Monads, which are basically very related, but which indeed require both a wrapped type as imput as well as that they return the that wrapped type (arrays or lists are a good example, but the Option and Result types in the Rust language are also great examples of monads). I am really interested in anyones reply on this, learn me more.

I too wanna say howdy to Don, Ramy, and Chadwick--Ijemma knows what's up