This post is published in relation to the 
Repository
Introduction
Hello everyone!
Welcome to my 45th translation report for the Node.js project!
Today I started and finished a new medium file: deprecations.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 45th translation for the Node.js project.
Today I started and finished a new file called deprecations.md which deals with APIs, methods, modules, properties and everything that has been deprecated in Node.js.
It was quite easy and I didn't have any particular issue, the final result is great as always: 2931 total words and 1365 clean words.
In this 45th part I translated the whole file introducing which are the main deprecation types and listing and explaining all 108 deprecations.
It was quite interesting because it's a file that refers to several topics already discussed.
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?
- Userland - What is a Userland (or User Space) and what is its role in deprecations.md: it refers to all code that runs outside the operating system's kernel. Userland usually refers to the various programs and libraries that the operating system uses to interact with the kernel: software that performs input/output, manipulates file system objects, application software, etc.
Each user space process normally runs in its own virtual memory space, and, unless explicitly allowed, cannot access the memory of other processes. This is the basis for memory protection in today's mainstream operating systems, and a building block for privilege separation. A separate user mode can also be used to build efficient virtual machines – see Popek and Goldberg virtualization requirements. With enough privileges, processes can request the kernel to map part of another process's memory space to its own, as is the case for debuggers. Programs can also request shared memory regions with other processes, although other techniques are also available to allow inter-process communication.
Source - Type System - What is Type System and what is its role with Type Checking and Compile-Time in deprecations.md: it is a set of rules that assigns a property called type to the various constructs of a computer program, such as variables, expressions, functions or modules. These types formalize and enforce the otherwise implicit categories the programmer uses for algebraic data types, data structures, or other components (e.g. "string", "array of float", "function returning boolean"). The main purpose of a type system is to reduce possibilities for bugs in computer programs by defining interfaces between different parts of a computer program, and then checking that the parts have been connected in a consistent way. This checking can happen statically (at compile time), dynamically (at run time), or as a combination of static and dynamic checking. Type systems have other purposes as well, such as expressing business rules, enabling certain compiler optimizations, allowing for multiple dispatch, providing a form of documentation, etc.
Source - Compile-Time - What is the Compile-Time and how it works with Type Checking in deprecations.md: it refers to either the operations performed by a compiler (the "compile-time operations"), programming language requirements that must be met by source code for it to be successfully compiled (the "compile-time requirements"), or properties of the program that can be reasoned about during compilation. Compile time refers to the time duration during which the statements written in any programming language are checked for errors.
Source - NPN - What is the NPN (Next Protocol Negotiation) or ALPN (Application-Layer Protocol Negotiation) and how it works in deprecations.md: it is a Transport Layer Security (TLS) extension for application layer protocol negotiation. ALPN allows the application layer to negotiate which protocol should be performed over a secure connection in a manner that avoids additional round trips and which is independent of the application layer protocols.
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: 2931
- Clean Words: 1365
Proof of Authorship
Feedback & Conclusion
Hoping to find a new interesting and hard file to challenge and study with.
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!