A Modern JavaScript Tutorial

Post by xixixao » Tue, Dec 08, 2020, 3:55 AM UTC

useragent86 wrote: post #193

kaycebasques wrote: post #42

This is not a tutorial [1]. It's more like a guide [2]. [1]: https://documentation.divio.com/tutorials/ [2]: https://documentation.divio.com/how-to-guides/ Edit: I don't mention this to be nitpicky. I mention it because I wish that we would collectively start standardizing those terms. I think it would be helpful if, whenever we saw "… guide" or "… tutorial" we had a general idea about the structure and purpose of th…

I looked at those links. Here's what I got from them: 1. Tutorials "are lessons that take the reader by the hand through a series of steps." They "are oriented towards learning how." 2. How-to guides "take the reader through steps." 3. "How-to guides are wholly distinct from tutorials." If I found a "community" around a topic, do I then get to decide what words mean? By consensus, of course.

Post by Ankintol » Tue, Dec 08, 2020, 4:28 AM UTC

z3t4 wrote: post #185

Ankintol wrote: post #141

Earlier quoted context omitted.

The fact you ask this question gets at my point I think. For several years I've been writing a large computer algebra system(CAS) that runs on a webpage. Every time the user puts some input into a text box the CAS runs. Depending on the input it may run as many as ~40k lines of code. There are no coherent lines upon which to split the CAS as far as anyone developing it can tell. The CAS must run on the browser both t…

The trick is to not break it up. Adding more lose ends will just make the ball of twine more complicated. What you can break out though is independent code that is the same for many apps, that code can be made into a module and reused across apps. Pure mathematical functions can be turned into a library. But what could probably help keep your sanity for a CAS is to add a test case for every change to make sure the sa…

Post by bigiain » Tue, Dec 08, 2020, 4:37 AM UTC

ehutch79 wrote: post #156

hanoz wrote: post #152

Earlier quoted context omitted.

>There is one small comment at the top of the chapter, which says ‘Irony detected’. The whole chapter is littered with clearly tongue in cheek remarks.

People will absolutely not get that and take the advice to heart.

Post by throw_m239339 » Tue, Dec 08, 2020, 4:47 AM UTC

vorpalhex wrote: post #90

rictic wrote: post #81

Earlier quoted context omitted.

Unlike other languages, typescript adds zero runtime overhead, and the APIs that one writes in TS are trivially consumable from JS. Consuming JS from TS is also made as easy as possible, including the option to set types aside entirely for some parts of your code using the "any" type, which means "don't type check this, just trust me that it works". TS really is different from other compile-to-js languages in this re…

It adds in developer overhead and for someone writing in JS that is often what you are trying to minimize.

Post by heavyset_go » Tue, Dec 08, 2020, 5:33 AM UTC

halfmatthalfcat wrote: post #72

cgrealy wrote: post #69

Isn’t step 1 of “modern JavaScript” to install TypeScript? :)

Amazing how many JS devs I meet (or work with) that are against the very idea of Typescript.