What do you think?
Rate this book
Reactive Programming with JavaScript
Reactive Programming with JavaScript
- GenresProgramming
264 pages, Paperback
First published August 31, 2015
1 person is currently reading
5 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 3 of 3 reviews
May 27, 2016
If I had to define this book in a single word, I'd had to go with "unfocused".
Now, with that title, you'd expect to learn about the principles that drove the design of things like "ReactJS". But it doesn't. This is not about Reactive Programming. It's about ReactJS. And it's not about Reactive Programming, it's about Reactive Funcional Programming.
Well, you'd still expect it to come with some conclusions about ReactJS, right? Wrong again.
Most of the time you'll spend reading things that have absolutely no relation with reactive programming, functional reactive programming or even ReactJS. There is a long rant about C++ which ends with no conclusion at all and gives no pointers on how it connects to the whole. There is another discussion about INTERCAL which leads to nowhere -- maybe, except, the author's bank account for the number of words.
At some point, the author finally discusses a bit of functional programming talking about
If it was possible to run tests over the content of the book, the amount of content out of a coverage on a BDD about Reactive Programming would point that about 90% of it is never tested. It's content that talks absolutely nothing about reactive programming, with large portions being repeated over and over again (which makes me, once again, wonder why Packt pays for reviewers when this kind of bullshit happens).
"This book is about ReactJS", the author says in the introduction, but there are only 4 chapters about ReactJS, with terrible JavaScript and absolutely no explanation on why things are being designed that way.
You want a review in a single phrase? Ok, that phrase would be "stay away from this book".
Now, with that title, you'd expect to learn about the principles that drove the design of things like "ReactJS". But it doesn't. This is not about Reactive Programming. It's about ReactJS. And it's not about Reactive Programming, it's about Reactive Funcional Programming.
Well, you'd still expect it to come with some conclusions about ReactJS, right? Wrong again.
Most of the time you'll spend reading things that have absolutely no relation with reactive programming, functional reactive programming or even ReactJS. There is a long rant about C++ which ends with no conclusion at all and gives no pointers on how it connects to the whole. There is another discussion about INTERCAL which leads to nowhere -- maybe, except, the author's bank account for the number of words.
At some point, the author finally discusses a bit of functional programming talking about
map,
filterand
reduce, but it goes nowhere from there and a whole chapter with 10+ pages have a single paragraph about real, focused talk about functional programming; the rest is just more rambling going to nowhere.
If it was possible to run tests over the content of the book, the amount of content out of a coverage on a BDD about Reactive Programming would point that about 90% of it is never tested. It's content that talks absolutely nothing about reactive programming, with large portions being repeated over and over again (which makes me, once again, wonder why Packt pays for reviewers when this kind of bullshit happens).
"This book is about ReactJS", the author says in the introduction, but there are only 4 chapters about ReactJS, with terrible JavaScript and absolutely no explanation on why things are being designed that way.
You want a review in a single phrase? Ok, that phrase would be "stay away from this book".
October 1, 2016
Forse il peggior libro che abbia letto quest'anno.
Tanto per cominciare non parla assolutamente di Reactive Programming, ma solo di ReactJS, e neanche tanto.
Due terzi abbondanti del libro sono un'analisi critica degli scritti di Douglas Crockford. O meglio, di 4 o 5 paragrafi dei suoi libri, ripetuti fino alla nausea.
Quando cita Immutable.js, che avrebbe qualche funzionalità reactive, si limita a riportare la lista delle funzioni, senza spiegare niente.
Le spiegazioni su ReactJS sono al limite del comprensibile, e il codice è tra i peggiori che abbia mai visto in vita mia. Sembra che abbia preso pessimo codice scritto per jQuery e l'abbia infilato dentro la funzione render() di un paio di componenti. God-components, tra l'altro, che nemmeno sfruttano la modularità di ReactJS.
Da dimenticare.
Tanto per cominciare non parla assolutamente di Reactive Programming, ma solo di ReactJS, e neanche tanto.
Due terzi abbondanti del libro sono un'analisi critica degli scritti di Douglas Crockford. O meglio, di 4 o 5 paragrafi dei suoi libri, ripetuti fino alla nausea.
Quando cita Immutable.js, che avrebbe qualche funzionalità reactive, si limita a riportare la lista delle funzioni, senza spiegare niente.
Le spiegazioni su ReactJS sono al limite del comprensibile, e il codice è tra i peggiori che abbia mai visto in vita mia. Sembra che abbia preso pessimo codice scritto per jQuery e l'abbia infilato dentro la funzione render() di un paio di componenti. God-components, tra l'altro, che nemmeno sfruttano la modularità di ReactJS.
Da dimenticare.
September 16, 2015
parts were good. the parts i liked were more about computer programming history. i didn't care for the code examples (which were long and involved for their value)
Displaying 1 - 3 of 3 reviews