I wonder how module dependency manager like RequireJS
After rereading the last chapter of Scope & Closure of YDKJS
interesting code in my own words.
As a person with beginner’s mind, I always think I already know about
something but God knows that I know nothing about it.
To begin with, let’s this snippet speaks volume before we go any further.
Without familiarity with apply, call or bind, the snippet above would
be hardly understood. If you find it confusing, it’s well advised to review
apply before rereading my comments on the snippet. Here’s the best
I am sorry, she is too cute!
Well done! After reading the documentation about apply, I am sure you
understand the snippet more than I do. With that premise, I can say that you
recognize that the $mod or ModuleManager make any objects (modules)
we define persist throughout the runtime. Those modules resides in private
Let’s say I’d like to have a module that greets anyone I meet.
Here’s how I make use of it.
Right now, my heart burns with high dosage of cuteness. I really want to confess
this feeling to the ones I like the most, but I need to greet them before I do
that. Why not I make use of existing module (‘greeting’) we just defined? Don’t
repeat yourself they say!
Alright! Now I can confess my feeling to multiple girls at once! I am fabulous!
Oh, for that cute girl endowed with cute ponytail (if she happens to wear one), I have prepared a
special pick up line I borrow from a friend. I am sure I can touch her heart
List my pick up lines toward those cute girls.
You know what, I lie about me loving them. I am sure it’s not about “love”, it’s
a mere infatuation, a long lasting desire of attachment that would vanish in no
time. It’s hormonal. One thing I can tell them truthfully is that I love my
family and my hobbies. I am sorry darling.
Truth be told.
That’s it for today. I want to kiss ちえさ せれな on the cheek.