congrats on the book, and on previous books. just wanted to comment that i appreciate the choice of including javascript, and i think a lot of other people might too
i learned python for vfx work and for scientific computing, so i've used it plenty. but since learning javascript and using it in the browser for graphics and signal processing prototyping, the fact that you can write straightforward inner-loop/for-loop code without feeling like the language is on your back for doing something terribly "unpythonic" is awesome (where i interpret "unpythonic" in a lot of cases to actually be something like, Don't go there cause this language is too slow for that!). but then you also have like map/filter/reduce available, do you can use all the modern, ergonomic stuff too
also, with javascript examples available in a straightforward html page, the focus is on what the code *does*. you're looking at the output, and see that 1) it works, and 2) it does something of interest to you, before you view source and check out what the interesting thing is made of. i feel like a lot of people who aren't really from a programming background might feel the same: that they don't really want to "just show me the code" from the outset; they want to see from the outset that what is being produced is worthwhile enough to justify the investment in trying to understand what's going on. the focus on "the rendered output of the program" rather than on "pages full of text that i have to figure out how to run just to see what it does" is helpful for that kind of audience
(for reference, the types of things that got me interested enough to learn javascript were like, the big page of D3 examples, P5.js and creative coding with Processing, looking at js1k/demoscene kind of things. all stuff that can be saved out to an html page, explored with the browser console, and put in a codepen or jsfiddle)
anyway, i saw in another answer that you mentioned a rosetta code style book, and i thought that would be really good too, cause a lot of people learn well that way too
ds6042 karma
congrats on the book, and on previous books. just wanted to comment that i appreciate the choice of including javascript, and i think a lot of other people might too
i learned python for vfx work and for scientific computing, so i've used it plenty. but since learning javascript and using it in the browser for graphics and signal processing prototyping, the fact that you can write straightforward inner-loop/for-loop code without feeling like the language is on your back for doing something terribly "unpythonic" is awesome (where i interpret "unpythonic" in a lot of cases to actually be something like, Don't go there cause this language is too slow for that!). but then you also have like map/filter/reduce available, do you can use all the modern, ergonomic stuff too
also, with javascript examples available in a straightforward html page, the focus is on what the code *does*. you're looking at the output, and see that 1) it works, and 2) it does something of interest to you, before you view source and check out what the interesting thing is made of. i feel like a lot of people who aren't really from a programming background might feel the same: that they don't really want to "just show me the code" from the outset; they want to see from the outset that what is being produced is worthwhile enough to justify the investment in trying to understand what's going on. the focus on "the rendered output of the program" rather than on "pages full of text that i have to figure out how to run just to see what it does" is helpful for that kind of audience
(for reference, the types of things that got me interested enough to learn javascript were like, the big page of D3 examples, P5.js and creative coding with Processing, looking at js1k/demoscene kind of things. all stuff that can be saved out to an html page, explored with the browser console, and put in a codepen or jsfiddle)
anyway, i saw in another answer that you mentioned a rosetta code style book, and i thought that would be really good too, cause a lot of people learn well that way too
View HistoryShare Link