There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.
If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.
Join the Discussion. Help a fellow learner on their journey.
Ask or answer a question about this exercise by clicking reply () below!
You can also find further discussion and get answers to your questions over in Language Help.
Agree with a comment or answer? Like () to up-vote the contribution!
In the previous excersizes, when we defined an emitter, we had to call .emit() on it to start processing data. what is the equivelent in this excersize?
I understand that the interface generates the events internally( after calling the callback? )
the method event.emit() will make event occurs and relative data will add to this event. I mean emit() method is a way that we can make event occurs. However, in system, events automative occurs, we don’t need to make it occurs. The thing we need to do is assign the events which we want systems detect it by method on(). This thing mean if you don’t pass event in to method on(), system will ignore that event.
Thanks for the FYI, I appreciate it.
However, if that’s true, than that further adds to the claims that Javascript (and apparently Node as an env) is incredibly YOLO.
I mean, You want to stream line-by-line as output? Well, just set up a readline Interface, and override its Input property as a ReadStream ‘line’ event, and listen on it!
…And that’s it! It’ll just invoke automatically!
…Okay, why?
According to Node’s API, their explanation is that: “The most common way is to listen to a ‘line’ event”, but why?
There are already a few instances in which Javascript / NodeJS functionality is implied, rather than being made explicit. But this takes the cake.
You listen to an event to invoke it? Man, that’s wild. I’d never have guessed that on my own, studying this thing already feels needlessly counter intuitive.
Never had that issue when learning C, C# and Java, on any level. Heck, even complex arguments for Regex.
) below.
) to up-vote the contribution!