Spanish Translation of Node.js (Part 18) (1110 words)
Node.js is an Open Source JavaScript runtime built on Chrome's V8 JavaScript engine supported by the Node.js Foundation
- What is Node?
Node.js is an environment in which you can run a program written in JavaScript (known as JS). Essentially, JS was made to run only through web browsers, which means that executing a JS program outside of a browser would normally throw an error. However, NodeJS took Chrome's V8 Runtime Engine for JavaScript and assembled it inside to allow for executing this language outside of a web browser.
The V8 Engine basically takes the JS code and converts it into a much faster machine code, which is a simpler low level code that the computer can execute without needing to first interpret it due to its simplicity and linear algorithmic structure.
Therefore, Node.js transforms your JS code into assembler-level machine code allowing you to use its capabilities as a scripting language, such as Python. This also allows you to basically take the functionalities available in languages like PHP and Ruby and apply them to JavaScript.
Contribution Specifications
- Translation Overview
In this translation, I continued with the events and methods referring Writable Streams. Among the events we can find drain, error, finish, pipe and unpipe. This documentation explains when these vents are emitted. For example, the error event is emitted when an error appears during writing or data channeling.
After that I started to work on Readable Streams, which are the ones that can be HTTP answers on client-side, HTTP request on server-side, FS read streams, zlib streams, etc.
Additionally, it is explained their functionality modes: flowing and paused. On the first mode data is read automatically from the underlying system and is sent to the app using events through the interface. On the second mode, the stream.read() method is called to read the data chunks from the stream.
I also worked on the three possible states in which the readable streams can be: null, true or false. These states will determine the data generation on the stream.
During this translation it brought my attention the way the word flush is translated because there are instances where it can be a function. However, depending on the context it can act as a verb, referring to the action of flushing, which is unloading data from a virtual space.
Similarly, the terms chunk and raise stand out due their adaptation to Spanish and the different synonyms that can be used but don’t adequately adjust the programming language, therefore, there was work involved in finding the right connotation.
- Languages
- Source Language: English
- Translated Language: Spanish
- Word Count
Number of words translated on this contribution: 1110 words, including a small number of coding instructions.
Proof of Authorship
The translation was submitted via CrowdIn and you can find all the related information on the following links.
My Crowdin Profile
My Crowdin Activity
My Github Profile
- Examples sentences in Spanish:
- When using [<0>writable.cork()</0>][] and <0>writable.uncork()</0> to manage the buffering of writes to a stream, it is recommended that calls to <0>writable.uncork()</0> be deferred using <0>process.nextTick()</0>.
Cuando se utilizan [<0>writable.cork()</0>][] y <0>writable.uncork()</0> para administrar el almacenamiento en buffer de las escrituras en un stream, se recomienda que las llamadas a <0>writable.uncork()</0> se difieran utilizando <0>process.nextTick()</0>.
- While in this state, attaching a listener for the <0>'data'</0> event, calling the <0>readable.pipe()</0> method, or calling the <0>readable.resume()</0> method will switch <0>readable._readableState.flowing</0> to <0>true</0>, causing the Readable to begin actively emitting events as data is generated.
Mientras se encuentre en este estado, adjuntar un listener para el evento de <0>'data'</0>, llamar al método <0>readable.pipe()</0>, o llamar al método <0>readable.resume()</0> cambiará <0>readable._readableState.flowing</0> a <0>true</0>, causando que el Legible comience a emitir eventos activamente a medida que se generan los datos.
- The primary intent of <0>writable.cork()</0> is to avoid a situation where writing many small chunks of data to a stream do not cause a backup in the internal buffer that would have an adverse impact on performance.
La intención principal de <0>writable.cork()</0> es evitar una situación en la que escribir muchas piezas pequeñas de datos al stream no cause una copia de seguridad en el buffer interno, eso tendría un impacto adverso en el rendimiento.
Previous Spanish translations for the project:
| Contribution Number | Translation Volume |
|---|---|
| N°1 | 1130 words |
| N°2 | 1331 words |
| N°3 | 1164 words |
| N°4 | 1117 words |
| N°5 | 1215 words |
| N°6 | 1215 words |
| N°7 | 1109 words |
| N°8 | 1123 words |
| N°9 | 1105 words |
| N°10 | 1131 words |
| N°11 | 1113 words |
| N°12 | 1119 words |
| N°13 | 1135 words |
| N°14 | 1120 words |
| N°15 | 1239 words |
| N°16 | 1350 words |
| N°17 | 1134 words |
Hi @isabella394,
Thank you for submitting your contribution!
Node.js is a very interesting project that contains many code values and terms related to computer science. Its difficulty relies on the fact that we must pay a lot of attention to the code in order to deliver the most accurate translation possible.
Your presentation post follows all the general guidelines, it contains all the needed information related to the project. You also included useful concepts you learned while working on this contribution, as well as examples.
You did a very good job with your translation. You used the correct vocabulary and you were careful with code values that should not be translated.
I really appreciate the effort you put in order to make sure your translation is as accurate as possible.
Keep up the good work!
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Chat with us on Discord
Thank you for your review, @marugy99! Keep up the good work!
Congratulations @isabella394! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :
Click here to view your Board of Honor
If you no longer want to receive notifications, reply to this comment with the word
STOPDo not miss the last post from @steemitboard:
Hi @isabella394!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @isabella394!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!
Congratulations @isabella394! You received a personal award!
Click here to view your Board of Honor
Congratulations @isabella394! You received a personal award!
You can view your badges on your Steem Board and compare to others on the Steem Ranking
Vote for @Steemitboard as a witness to get one more award and increased upvotes!