[GoLUG] GoLUG meeting: Google's Material Design - an Implementation in React

[Ron / BCLUG]

Kyle Terrien wrote on 2024-10-08 19:40:

> Is this book a good resource?
> 
> https://eloquentjavascript.net/

It does look like it - well-written, pleasant type face, good examples.
I glanced at it and kept reading the entire chapter.


> I have been slowly working through it over the summer.  There are
> some chapters about asynchronous programming and the async
> keyword---the part I recall you said you had to think about until it
> “clicked”.  I haven’t reached that part yet, but I probably should
> hop to it.

Promises vs async/await are ... contentious and difficult.

Seems the general consensus is, async/await.



> Honestly, I’m still trying to figure out why Node.JS does things
> that way instead of utilizing a threaded event loop.

JavaScript is an asynchronous, single threaded language. Changing that
would break all previous code (probably).



I looked at the Higher-Order Functions chapter and saw something Steve 
might like regarding callbacks:

> Functions that operate on other functions, either by taking them as
> arguments or by returning them, are called higher-order functions.
> Since we have already seen that functions are regular values, there
> is nothing particularly remarkable about the fact that such functions
> exist. The term comes from mathematics, where the distinction between
> functions and other values is taken more seriously.
> 
> Higher-order functions allow us to abstract over actions, not just
> values. They come in several forms. For example, we can have
> functions that create new functions.



https://eloquentjavascript.net/05_higher_order.html