3 ms·
Thanks. This brings up the point that, if OP clarifies in his (already great) document, would really help. By using node.js, OP has implicitly made a statement
by fizixer 7y ago
Thanks. This brings up the point that, if OP clarifies in his (already great) document, would really help.
By using node.js, OP has implicitly made a statement of javascript as the server-side language of choice.
Even though there is some mention of one system doing multiple things, it would really help if OP adds a section about justification of an all-js approach. And especially, what OP's opinion is about programming in 'JS The Good Parts' (a-la Crockford) vs 'anything goes'.
I believe OP may have good opinions about how to approach JS programming. It would be great if that is added to the document.
In any case, I highly appreciate OP sharing this work. Thank you.
edit: OP address part of this in his comment [1]
[1] https://news.ycombinator.com/item?id=22116437 https://news.ycombinator.com/item?id=22116437
- fpereiro 7y agoHi there! - I choose js/node as my server-side language of choice. This is because I love both js the language and node itself, and so far haven't seen the need to try something else. That doesn't mean, however, that it should be the solution for everyone. Particularly if you don't like js - you're probably better off programming in a language you enjoy! - I have rambled a bit about js style here: https://github.com/fpereiro/ustack#mes5-a-javascript-subset https://github.com/fpereiro/ustack#mes5-a-javascript-subset . My approach, however, is very minimalistic and backward-looking (or aspiring to timelessness, if you're being very kind), so I recommend it very cautiously. You might be better off using more language features, particularly those that come in ES6-7-8. For all of this, I'd rather leave this content separately in the ustack repo.