Repository

https://github.com/nodejs/i18n

Project Details

Node.js, by definition, is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside the browser. This means that now it is possible to execute a program written in JS outside a web browser such as Google Chrome, Safari, etc. This creates an extension to what the language can do, besides just creating interactive websites. With the help of the V8 JavaScript runtime engine, it can now take the code and convert it into a faster machine code, e. g., Node.js eliminates the waiting and continues to take care of the next task.

From my personal perspective, Node.js represents an advantage for the coders to write code, since it still has all the capabilities and functionalities JavaScript offers, but now in a more extended way. Also, thanks to all the time I have been contributing with this project, I have realized the huge amount of time and effort that the Node.js team has taken in order to make it as good as it is and also to improve it with every single upgrade.

You can take a look at their Crowdin project here.

Contribution Specifications

• Translation Overview

This is the 45th translation I made for the Node.js project, and on this contribution I started translating the WRITING-AND-RUNNING-BENCHMARKS.MD folder, which I define as follows:

-- WRITING-AND-RUNNING-BENCHMARKS.MD: The intention of this folder is to inform the writer on how to write and run benchmarks on the Node.js project. It starts by showing the requirements to write the different types of benchmarks, their way of execution and its way of creation. It also shows a not-so-short list of comparisons of the different versions of the benchmarks. I find this very useful for the coders since it shows that the project itself is interested on showing (and somehow teaching) their writers how to do things correctly by informing them about the different ways to do a task.

Now, nothing within this contribution is either complex or hard to understand, since it is basically a tutorial. However, there is a thing I would like to mention to show the difference between three things: benchmark, benchmarker and benchmarking.

Let's start with benchmark. In the computing area, a benchmark is the act of running or executing a computer program, a set of programs or any other operations in order to asses the relative performance of an object, usually by running a number of standard tests and trials against it. So basically, a benchmark is a test, and its function is to measure the performance of a hardware, a software or a computer itself. These tests can be used to compare how well a product works against any other. So, the higher value of the results means the fast the component, software or overall computer is.

There are plenty of softwares that realize a computer benchmark, and those are the so called benchmarkers. The different computer programs that realize the tests and trials. One example is the one shown in the picture below, CrystalMark, and it shows the overall rating of each of its components.

And benchmarking is just the practice of comparing business processes and performance metrics to industry best practices from other companies. The dimensions usually measured are quality, time and cost. Now, even though there is not a single benchmarking that has been universally adopted, it does exist a 12-step methodology that helps to develop one.

The 12 stage methodology consists of:

1. Select subject
2. Define the process
3. Identify potential partners
4. Identify data sources
5. Collect data and select all partners
6. Determine the gap
7. Establish process differences
8. Target future performance
9. Communicate
10. Adjust goal
11. Implement
12. Review and recalibrate

As I mentioned, there are many different ways to develop a benchmark, however, the process is similar.

SOMETHING IMPORTANT TO KNOW

The word benchmark was translated to prueba de rendimiento, while the words benchmarking and benchmarker were kept untranslated.

Examples of strings translated:

1. EN: Basics of a benchmark

SP: Conceptos básicos de una prueba de rendimiento

2. EN: Basic Unix tools are required for some benchmarks.

SP: Se requieren herramientas básicas de Unix para algunas pruebas de rendimiento.

3. EN: Most of the HTTP benchmarks require a benchmarker to be installed.

SP: La mayoría de las pruebas de rendimiento de HTTP requieren que se instale un benchmarker.

References:

-- Wikipedia. Benchmark (https://en.wikipedia.org/wiki/Benchmark_(computing))

-- Wikipedia. Benchmarking (https://en.wikipedia.org/wiki/Benchmarking)

-- Computer Hope. What is a Benchmark? (https://www.computerhope.com/jargon/b/benchmar.htm)

• Languages

I translated from English to Spanish.

I have translated over 100,000 words utilizing the Crowdin platform and this has given me experience to always grant great quality translations.

• Word Count

I have translated 1,053 words. This contribution has been made between the dates Feb/1/2019, when I realized the translation, and Feb/2/2019, when I realized the corrections.

Previous translations on this project:

• Part 1
• Part 2
• Part 3
• Part 4
• Part 5
• Part 6
• Part 7
• Part 8
• Part 9
• Part 10
• Part 11
• Part 12
• Part 13
• Part 14
• Part 15
• Part 16
• Part 17
• Part 18
• Part 19
• Part 20
• Part 21
• Part 22
• Part 23
• Part 24
• Part 25
• Part 26
• Part 27
• Part 28
• Part 29
• Part 30
• Part 31
• Part 32
• Part 33
• Part 34
• Part 35
• Part 36
• Part 37
• Part 38
• Part 39
• Part 40
• Part 41
• Part 42
• Part 43
• Part 44

Proof of Authorship

My Crowdin profile

Word Count