This post is published in relation to the 
Project details and translation's reason
Node.js is a Javascript runtime. The project title refers to the node word, and indeed Node.js is closely related to this concept. It is a fascinating project and it has a considerable potential.
Below you can read some significant features of Node.js:
- Node.js is open source and takes full advantage of the power of communities to get better over time.
- Node.js relies heavily on the concept of scalability, in fact thanks to this feature it has the ability to generate network applications which also are based on the scalability.
- The concept of "events" in node is implemented and rethought, in fact the old concept used by other event library systems is replaced on Node with the event runtime. This "cycle of events" is activated through the calling process.
- Node.js is also designed to have an interface that makes it easy to use.
- Node distinguishes itself from other similar systems thanks to the absence of operating system threads.
These motivations are a great incentive to translate this project. Briefly I consider interesting two factors: the first one is how Nod.js differs from the majority of similar projects, the second one is its being completely open source. These two characteristics are so relevant that they stimulate me to translate it.
Github
Check out the whole project on Github
Contribution specification
My role as a translator consists in translating the strings I find during my translation work in the most appropriate way, from the English language to the Italian one.
This translation work is divided in two phases:
The first one is the work of simple translation and the second one consists in understanding the contexts and understand what kind of specific words should be translated and which not (for example because they are too technical to be translated).
Translation Overview
This is my sixth post of the project Node.js. For each post done, I gain more experience about Node, which as already mentioned above is a very technical project.
In these thousand words I found different topics depending on the folder treated:
- Folder Perf_hooks.md LINK (folder that I have completed):
In this folder I faced topics related to performance and timing, and other topics concerning Async operations.
- Folder process.md LINK (which I have not concluded):
In this folder I have translated sentences with topics related to events (old topics like calling and listening have been repeated).
I am very glad to have the opportunity to develop a new training experience, thanks to Node.
Excerpts of my work
Below I propose some significant strings that help to better understand the work I have done translating these 1000 words:
##Perf_hooks.md
Anync operation...
The following example uses the Async Hooks and Performance APIs to measure the actual duration of a Timeout operation (including the amount of time it to execute the callback).
Perfomance
Class: PerformanceObserverEntryList
The PerformanceObserverEntryList class is used to provide access to the PerformanceEntry instances passed to a PerformanceObserver.
performanceObserverEntryList.getEntries()
Returns: {PerformanceEntry[]}
Returns a list of PerformanceEntry objects in chronological order with respect to performanceEntry.startTime.
Process.md
Event...
Event: 'disconnect'
If the Node.js process is spawned with an IPC channel (see the Child Process and Cluster documentation), the 'disconnect' event will be emitted when the IPC channel is closed.
Calling...
Normally, the Node.js process will exit when there is no work scheduled, but a listener registered on the 'beforeExit' event can make asynchronous calls, and thereby cause the Node.js process to continue.
Languages
Source language: English
Target language: Italian
To check my previous experiences as a translator you can consult my application
Word count
Words Translated: 1030
Proof of authorship
You can lookup Crowdin project on the following link, as well as the summary of my activities