From 815c620a770413298b4aa3fcb091d48052146d21 Mon Sep 17 00:00:00 2001 From: Robert Jefe Lindstaedt Date: Mon, 25 Jan 2016 02:46:06 +0100 Subject: [PATCH 1/2] ep: ws in core --- 003-ws-in-core.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 003-ws-in-core.md diff --git a/003-ws-in-core.md b/003-ws-in-core.md new file mode 100644 index 0000000..1fe3cbb --- /dev/null +++ b/003-ws-in-core.md @@ -0,0 +1,30 @@ +| Title | ws in core | +|--------|-----------------------------| +| Author | @eljefedelrodeodeljefe | +| Status | DRAFT | +| Date | 2015-01-25 02:34:00 | + +## Description + +This EP proposes having the current [websockets/ws](https://github.com/websockets/ws) userland implementation in core. +Efforts have already been made on nodejs/node#4842. It is understood that +adaptions to style and simplicity need to be done in order to conform with +`node` core. + +## Motivation + +> `websockets` are the primary reason for companies, which have **not** decided +to make a commitment towards `node` to use `node` anyways. For a wider adoption +of the language this is a critical point. + +The above statement is the observation of the author. + +However in order to gain momentum as a language, the experience should be as +performant, secure and well documented as possible. Userland development is to +be believed not holding enough capacity to meet those requirements. Especially +issues like `Buffer(number)`, however dangerous they are, can only be +effectively secured via backporting code through the language's LTS. + +## Note + +This document is in progress. From dd2b60c0a0e924faaadfe911e6d71169291b0182 Mon Sep 17 00:00:00 2001 From: Robert Jefe Lindstaedt Date: Mon, 25 Jan 2016 12:48:58 +0100 Subject: [PATCH 2/2] weaker wording --- 003-ws-in-core.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/003-ws-in-core.md b/003-ws-in-core.md index 1fe3cbb..a9a5d17 100644 --- a/003-ws-in-core.md +++ b/003-ws-in-core.md @@ -13,9 +13,9 @@ adaptions to style and simplicity need to be done in order to conform with ## Motivation -> `websockets` are the primary reason for companies, which have **not** decided -to make a commitment towards `node` to use `node` anyways. For a wider adoption -of the language this is a critical point. +> `websockets` are a foot-in-the-door feature for companies, which have **not** +decided to make a commitment towards `node` to use `node` anyways. For a wider +adoption of the language this is a critical point. The above statement is the observation of the author.