This post is published in relation to the 
Repository
Introduction
Hello everyone!
Welcome to my 48th translation report for the Node.js project!
Today I decided to start a new file, even if this is quite short: domain.md!
Keep reading to check out more about this new translation report!
Enjoy!
Project Details
Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. It uses a non-blocking event-driven I/O model, which makes it a lightweight and efficient framework. I believe in open source projects and I think it's essential to work on this great project because the package ecosystem of Node.js, called npm, is the largest ecosystem of open source libraries in the world.
Given its importance, its translation into many languages is almost due.
I'll use my skills to make an high quality translation and maybe to learn something more about Node.js world.
Contribution Specifications
Translation Overview
This is my 48th translation for the Node.js project.
Today I started domain.md translation, a short file of medium difficulty, in fact I have already finished it. There have been new words but nothing extremely difficult.
However the final result was great: 1752 total words and 1306 clean words.
In this 48th part I started introducing the domain and which is its function, after I translated several chapters about errors, binding (implicit and explicit) and about the specific class, ending with domains and promises.
Words left in English
This is a list of words I considered to left in English in order to give a more understandable translation.
My choice is based both on the project owners guidelines and on the web research carried out by myself.
Difficult words/sentences to translate in Italian
In this report I have not met words or sentences which put me in serious difficulty or which I have not been able to translate properly.
What did I learn new?
- Event-Driven Programming - What is the Event-Driven Programming and what is its role in domain.md: it is a programming paradigm in which the flow of the program is determined by events such as user actions (mouse clicks, key presses), sensor outputs, or messages from other programs/threads. Event-driven programming is the dominant paradigm used in graphical user interfaces and other applications (e.g., JavaScript web applications) that are centered on performing certain actions in response to user input. This is also true of programming for device drivers (e.g., P in USB device driver stacks).
In an event-driven application, there is generally a main loop that listens for events, and then triggers a callback function when one of those events is detected. In embedded systems, the same may be achieved using hardware interrupts instead of a constantly running main loop. Event-driven programs can be written in any programming language, although the task is easier in languages that provide high-level abstractions, such as await and closures.
Source
Suggestions/Revisions for Project Owners (Pull Requests etc.)
None in this report.
Languages
- Source Language: English
- Target Language: Italian
- Experience: You can check my experiences into my translator application
Word Count
- Total Words: 1752
- Clean Words: 1306
Proof of Authorship
Feedback & Conclusion
It was a rather quiet translation, already completed. Who knows when I will find a long and complex file.
What do you think about it? Did you know what I learned today?
Let me know, leave a comment below!
Thank you very much for your time and see you in the next post!