Spanish Translation of Node.js (Part 3) (1164 words)

in #utopian-io6 years ago (edited)

Github Repository

https://github.com/nodejs/node

General Information & Project Details

Node.js is an Open Source JavaScript runtime built on Chrome's V8 JavaScript engine supported by the Node.js Foundation

- What is Node?

The Node environment comprises everything you need to run a program written in JavaScript(JS).

Node.js first started when the original developers of JS extended its functionalities from something you could only run in the browser to something you could execute on your computer as a independent application.

Now you can do much more with JavaScript than just creating interactive websites and web apps. Modern JavaScript has the same capabilites as other scripting languages like Python, and therefore it can do the same as these.

Both your browser's JavaScript and Node.js environment run on the V8 JavaScript runtime engine. This engine takes your JS code and converts it into a much faster machine code (machine code is a low level code that the computer can execute without needing to first interpret it).

Contribution Specifications

- Translation Overwiew

In this section, my translation was focused on the guides related to the Buffer functionalities, specifically on the Class Buffer building commands and the allocation and Management of the system's memory for the Buffer. The documentation is also related with the encoding parameters and methods used on Node.js

- Languages

- Word Count

Number of words translated on this contribution: 1164 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.

Node.js Crowdin page

My Crowdin Profile
My Crowdin Activity
My Github Profile

- Examples sentences in Spanish:

  • However, in the case where a developer may need to retain a small chunk of memory from a pool for an indeterminate amount of time, it may be appropriate to create an un-pooled <0>Buffer</0> instance using <0>Buffer.allocUnsafeSlow()</0> and then copying out the relevant bits.
    • Sin embargo, en el caso donde un desarrollador puede necesitar retener un pequeño pedazo de memoria desde un conjunto por una cantidad indeterminada de tiempo, puede ser apropiado crear una instancia de Buffer sin agrupar utilizando Buffer.allocUnsafeSlow() y luego copiando los bits relevantes.

  • Note that the <0>Buffer</0> module pre-allocates an internal <0>Buffer</0> instance of size [<0>Buffer.poolSize</0>] that is used as a pool for the fast allocation of new <0>Buffer</0> instances created using [<0>Buffer.allocUnsafe()</0>] and the deprecated <0>new Buffer(size)</0> constructor only when <0>size</0> is less than or equal to <0>Buffer.poolSize >> 1</0> (floor of [<0>Buffer.poolSize</0>] divided by two).
    • Tenga en cuenta que el módulo Buffer asigna previamente una instancia de Buffer interna de tamaño [Buffer.poolSize] que es usado como un repositorio para la rápida asignación de las nuevas instancias de Buffer creadas utilizando [Buffer.allocUnsafe()] y el constructor obsoleto new Buffer(size) solo cuando size es menor o igual que Buffer.poolSize >> 1 (piso de [Buffer.poolSize] dividido entre dos).

  • Calling [<0>Buffer.alloc()</0>] can be significantly slower than the alternative [<0>Buffer.allocUnsafe()</0>] but ensures that the newly created <0>Buffer</0> instance contents will <1>never contain sensitive data</1>.
    • Llamar a [<0>Buffer.alloc()</0>] puede ser significativamente más lento que la alternativa [<0>Buffer.allocUnsafe()</0>] pero garantiza que el contenido de la instancia de <0>Buffer</0> creada recientemente <1>nunca contendrá datos confidenciales</1>.

Sort:  

Greetings, @isabella394. Thanks for submitting your contribution!

  • The presentation of your post is good, as it satisfies the requirements for a complete evaluation of your contribution.
  • The translated content fits coherently the general meaning and use of the strings enlisted.
  • You've shown a precise use of the terminology of the project.
  • Good feedback process. Thanks for taking your time to consider different approaches to complicated sentences.
  • Good job. Keep it up!

Congratulations!

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, @alejohannes!

So far this week you've reviewed 1 contributions. Keep up the good work!

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!