chore: remove performance section of ES6 page (#3181)

Information linked is out of date. Including an ES6 page is probably
something that needs to be re-thought entirely.

Fixes: #3176

Author: Trott

locale/ar/docs/es6.md

@@ -27,12 +27,6 @@ layout: docs.hbs
 node --v8-options | grep "in progress"
 ```
 
-## ماذا عن أداء ميزة بعينها؟
-
-يعمل فريق V8 باستمرار على تحسين أداء ميزات اللغة الجديدة للوصول في نهاية المطاف إلى التكافؤ مع نظرائهم المنقولين أو الأصليين في EcmaScript 5 والإصدارات السابقة، ويتم قياس التقدم الحالي على موقع [six-speed](https://fhinkel.github.io/six-speed) حيث يُظهر الأداء الخاص بميزات ES2015 وESNext بالمقارنة مع الميزات الأصلية المقابلة لها في الـ ES5.
-
-يتم العمل على تحسين الميزات المقدمة ابتداء من ES2015 وما بعدها بالتنسيق عبر [خطة أداء](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY) حيث يجمع فريق الـ V8 وينسق ما يجب تحسينه، كما يصمم المستندات التي من شأنها التطرق لتلك المشاكل.
-
 ## لقد قمت بإعداد بنيتي التحتية للاستفادة من علم `--harmony`. هل يجب علي إلغاء ذلك؟
 
 إن السلوك الحالي لعلم `--harmony` هو تمكين **المميزات التي سيتم شحنها** فقط. ففي نهاية المطاف هي تعتبر مرادفاً لـ `--es_staging`، وكما ذكر مسبقا فإن هذه الميزات تعتبر كاملة ولكن غير ثابتة بعد. إذا أردت أن يتم ذلك بأمان، خصوصا في بيئة إنتاجية فيجب عليك أن تأخذ بعين الاعتبار حذف هذا العلم حتى يتم شحن تلك الميزات افتراضيا مع الـ V8، ومن ثم مع الـ Node.js. إذا أبقيت على هذه الميزات مفعلة، فيجب أن تتوقع تَوَقُف شيفرتك عن العمل في ترقيات قادمة من الـ Node.js إذا غير الـ V8 من مسمياتهم لاتباع المعايير أكثر.

locale/en/docs/es6.md

@@ -27,12 +27,6 @@ You may list all the *in progress* features available on each Node.js release by
 node --v8-options | grep "in progress"
 ```
 
-## What about the performance of a particular feature?
-
-The V8 team is constantly working to improve the performance of new language features to eventually reach parity with their transpiled or native counterparts in EcmaScript 5 and earlier. The current progress there is tracked on the website [six-speed](https://fhinkel.github.io/six-speed), which shows the performance of ES2015 and ESNext features compared to their native ES5 counterparts.
-
-The work on optimizing features introduced with ES2015 and beyond is coordinated via a [performance plan](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY), where the V8 team gathers and coordinates areas that need improvement, and design documents to tackle those problems.
-
 ## I have my infrastructure set up to leverage the --harmony flag. Should I remove it?
 
 The current behaviour of the `--harmony` flag on Node.js is to enable **staged** features only. After all, it is now a synonym of `--es_staging`. As mentioned above, these are completed features that have not been considered stable yet. If you want to play safe, especially on production environments, consider removing this runtime flag until it ships by default on V8 and, consequently, on Node.js. If you keep this enabled, you should be prepared for further Node.js upgrades to break your code if V8 changes their semantics to more closely follow the standard.

locale/es/docs/es6.md

@@ -27,12 +27,6 @@ Puede detallar todas las funciones *in progress* disponibles en cada versión de
 node --v8-options | grep "in progress"
 ```
 
-## ¿Qué ocurre con el performance de una característica en particular?
-
-El equipo V8 trabaja constantemente para mejorar el rendimiento de las nuevas características del lenguaje para eventualmente alcanzar la paridad con sus homólogos nativos o transpilados en EcmaScript 5 y versiones anteriores. El progreso actual se registra en la web [six-speed](https://fhinkel.github.io/six-speed), que muestra el rendimiento de las funciones de ES2015 y ESNext en comparación con sus nativas homólogos ES5.
-
-El trabajo para optimizar las características introducidas con ES2015 y posteriores se coordina a través de un [plan de rendimiento](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY), donde se reúne el equipo V8 y coordina áreas que necesitan mejoras, y elaboran documentos para abordar esos problemas.
-
 ## Tengo mi infraestructura configurada para aprovechar la bandera --harmony. ¿Debo eliminarlo?
 
 El comportamiento actual del indicador `--harmony` en Node.js es habilitar solo las funcionalidades en **staged**. Después de todo, ahora es sinónimo de `--es_staging`. Como se mencionó anteriormente, estas son características completas que aún no se han considerado estables. Si desea jugar de forma segura, especialmente en entornos de producción, considere eliminar este indicador de tiempo de ejecución hasta que se envíe de forma predeterminada en V8 y, en consecuencia, en Node.js. Si mantiene esto habilitado, debe estar preparado para futuras actualizaciones de Node.js que puedan romper su código si V8 cambia su semántica para seguir más de cerca el estándar.

locale/fr/docs/es6.md

@@ -27,12 +27,6 @@ You may list all the *in progress* features available on each Node.js release by
 node --v8-options | grep "in progress"
 ```
 
-## What about the performance of a particular feature?
-
-The V8 team is constantly working to improve the performance of new language features to eventually reach parity with their transpiled or native counterparts in EcmaScript 5 and earlier. The current progress there is tracked on the website [six-speed](https://fhinkel.github.io/six-speed), which shows the performance of ES2015 and ESNext features compared to their native ES5 counterparts.
-
-The work on optimizing features introduced with ES2015 and beyond is coordinated via a [performance plan](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY), where the V8 team gathers and coordinates areas that need improvement, and design documents to tackle those problems.
-
 ## I have my infrastructure set up to leverage the --harmony flag. Should I remove it?
 
 The current behaviour of the `--harmony` flag on Node.js is to enable **staged** features only. After all, it is now a synonym of `--es_staging`. As mentioned above, these are completed features that have not been considered stable yet. If you want to play safe, especially on production environments, consider removing this runtime flag until it ships by default on V8 and, consequently, on Node.js. If you keep this enabled, you should be prepared for further Node.js upgrades to break your code if V8 changes their semantics to more closely follow the standard.

locale/ko/docs/es6.md

@@ -69,26 +69,6 @@ V8 엔진에 계속해서 새로운 기능이 추가되고 있습니다. 정확
 node --v8-options | grep "in progress"
 ```
 
-<!--
-## What about the performance of a particular feature?
-
-The V8 team is constantly working to improve the performance of new language features to eventually reach parity with their transpiled or native counterparts in EcmaScript 5 and earlier. The current progress there is tracked on the website [six-speed](https://fhinkel.github.io/six-speed), which shows the performance of ES2015 and ESNext features compared to their native ES5 counterparts.
-
-The work on optimizing features introduced with ES2015 and beyond is coordinated via a [performance plan](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY), where the V8 team gathers and coordinates areas that need improvement, and design documents to tackle those problems.
--->
-
-## 특정 기능의 성능은 어떻습니까?
-
-V8 팀은 새로운 언어 기능의 성능을 향상시켜 EcmaScript 5나 그 이전 버전의 네이티브 코드 또는
-트랜스파일된 코드와 동등해질 수 있도록 끊임없이 노력하고 있습니다. 현재 진행 상황은 웹 사이트
-[six-speed](https://fhinkel.github.io/six-speed)에서 확인할 수 있습니다. 이는 ES2015
-및 ESNext 기능의 성능을 네이티브 ES5와 비교하여 보여줍니다.
-
-ES2015 이후 도입된 기능의 최적화에 대한 작업은
-[성능 계획](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY)을 통해 조정됩니다.
-성능 계획 문서에서는 V8 팀에서 개선이 필요한 부분을 모아 분류하고, 이 문제들을 해결하기 위해
-설계한 문서를 확인할 수 있습니다.
-
 <!--
 ## I have my infrastructure set up to leverage the --harmony flag. Should I remove it?
 

locale/pt-br/docs/es6.md

@@ -27,12 +27,6 @@ Você pode listar todas as funcionalidades *em progresso* disponíveis em cada v
 node --v8-options | grep "in progress"
 ```
 
-## E sobre a performance de uma funcionalidade em particular?
-
-O time do V8 está constantemente trabalhando para melhorar a performance de novas funcionalidades da linguagem, para eventualmente encontrar uma paridade com a sua contraparte transpilada ou nativa no EcmaScript 5 ou anterior. O progresso atual é registrado no site [six-speed](https://fhinkel.github.io/six-speed), que mostra a performance das funcionalidades do ES2015 e do ESNext comparadas com as suas respectivas contrapartes nativas do ES5.
-
-O trabalho de otimizar as funcionalidades introduzidas com o ES2015 e além são coordenadas via um [plano de performance](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY), onde o time do V8 encontra e coordena áreas que necessitam de melhorias, além de criar documentos para atacar esses problemas.
-
 ## Eu tenho a minha infraestrutura configurada para suportar a flag --harmony. Eu devo remove-la?
 
 O comportamento atual da flag `--harmony` é habilitar somente funcionalidades **em homologação**. Além disso, ela agora é um sinônimo da flag `--es_staging`. Como mencionado anteriormente, estas funcionalidades estão completas, mas não foram consideradas estáveis ainda. Se você deseja rodar sua aplicação de forma segura, especialmente em ambientes de produção, considere remover esta flag até que ela seja lançada por padrão no V8 e, consequentemente, no Node.js. Se você deseja a manter habilitada, você deve estar preparado para atualizações futuras do Node.js que podem quebrar o seu código caso o V8 mude a sua semântica para seguir o padrão de maneira mais fiel.

locale/ro/docs/es6.md

@@ -27,12 +27,6 @@ You may list all the *in progress* features available on each Node.js release by
 node --v8-options | grep "in progress"
 ```
 
-## What about the performance of a particular feature?
-
-The V8 team is constantly working to improve the performance of new language features to eventually reach parity with their transpiled or native counterparts in EcmaScript 5 and earlier. The current progress there is tracked on the website [six-speed](https://fhinkel.github.io/six-speed), which shows the performance of ES2015 and ESNext features compared to their native ES5 counterparts.
-
-The work on optimizing features introduced with ES2015 and beyond is coordinated via a [performance plan](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY), where the V8 team gathers and coordinates areas that need improvement, and design documents to tackle those problems.
-
 ## I have my infrastructure set up to leverage the --harmony flag. Should I remove it?
 
 The current behaviour of the `--harmony` flag on Node.js is to enable **staged** features only. After all, it is now a synonym of `--es_staging`. As mentioned above, these are completed features that have not been considered stable yet. If you want to play safe, especially on production environments, consider removing this runtime flag until it ships by default on V8 and, consequently, on Node.js. If you keep this enabled, you should be prepared for further Node.js upgrades to break your code if V8 changes their semantics to more closely follow the standard.

locale/ru/docs/es6.md

@@ -39,17 +39,6 @@ ECMAScript в различных версиях Node.js на основе таб
 node --v8-options | grep "in progress"
 ```
 
-## А как насчет производительности конкретного функционала?
-
-Команда V8 постоянно работает над улучшением производительности новых языковых функций, чтобы в
-конечном итоге достичь равенства со своими транспилированными или нативными аналогами в EcmaScript 5
-или более ранних версиях. Текущий прогресс отслеживается на веб-сайте [six-speed](https://fhinkel.github.io/six-speed),
-который показывает производительность функций ES2015 и ESNext по сравнению с их родными аналогами ES5.
-
-Работа по оптимизации функций, представленных в ES2015 и более поздних версиях, координируется с помощью
-[плана производительности](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY),
-где команда V8 собирает и координирует сферы, требующие улучшения, и разрабатывает документы для решения этих проблем.
-
 ## Моя инфраструктура настроена с использованием флага --harmony. Должен ли я удалить его?
 
 Текущее поведение флага `--harmony` на Node.js состоит в том, чтобы включать только **подготовленный** функционал.

locale/zh-cn/docs/es6.md

@@ -27,12 +27,6 @@ Node.js 是针对 [V8](https://v8.dev/) 引擎构建的。通过与此引擎的
 node --v8-options | grep "in progress"
 ```
 
-## 对于一个特定的功能，它的特性又如何呢？
-
-V8 团队现正在努力持续工作，他们借助 EcmaScript 5 或是更早时代的语言规范，利用转译或是本地相当的技术以提高新语言的功能特性，使之达到平衡。目前研发进度记录可以在 [six-speed](https://fhinkel.github.io/six-speed) 查询到，它会告诉你 ES2015 和 ESNext 的性能究竟如何（和本地的 ES5 同等技术相比）。
-
-特性优化的工作也随着 ES2015 到来，以上计划是通过[执行计划](https://docs.google.com/document/d/1EA9EbfnydAmmU_lM8R_uEMQ-U_v4l9zulePSBkeYWmY)，有一个 V8 团队在那儿收集整理相关信息，并协调需要提高性能、设计追踪问题的文稿等部门。
-
 ## 我有我自己的基本框架，可以利用 --harmony，所以我可以移除这个标记吗？
 
 目前来说，`--harmony` 在 Node.js 的作用是让 **staged** 特性起作用。它本质上等同于 `--es_staging`。如上所述，有些特性尚未完全确认是稳定的，所以如果你希望一个安全的环境（尤其是在发布环境），你应该考虑移除这个运行时的环境标记，直到它在 V8 中以默认形式发布，或者在 Node.js 中落地。如果你开启了这个开关，你应该有对未来 Node.js 升级而造成代码破坏（无法正常工作）的准备，比如 V8 引擎做了更改，它的语法变得更接近标准。