Programming JavaScript Applications: Robust Web Architecture With Node, HTML5, and Modern JS Libraries

Elliott’s book fits neatly into that category of JavaScript books that are about praxis — books that are not about specific libraries or language features or programming paradigms, but about doing “real development” on “real teams”. It is close kin with

If you’re already fairly well-read in the “JavaScript praxis book” arena, then most of this is going to be review. Elliott covers functions as first-class objects and functional style JavaScript (see also
internationalization — which is something that I was very glad to see and is one of the reasons that I’ll be recommending this one to people looking to build “professional” applications.

The other thing I wanted to point out here was that Elliott goes back and forth between programming JavaScript for the browser and programming JavaScript for Node, and the transitions aren’t always clear. I expect this will get cleaned up a bit as they work it through editing for the final printed version. In either case, I am glad that he gives coverage to both in the same book, rather than marginalizing one or the other to a ghetto chapter.

—-

Footnotes:

[1]: To be fair: almost all of the technical book publishers that I know of are doing this lately — i.e., releasing

[2]: I go back and forth on this bit of critique. If you’re “all theory” then you’re potentially losing out on providing some value because you’re discussion is too far away from the real problems; but if you’re too close to “the real thing” then you’re just talking about that specific situation or tool-chain and it winds up being about addressing that problem with that tool, and not really “that class of problem”. Elliott is somewhere in the middle here, listing only slightly toward “too specific” and only in a couple of places.

[3]: The PDF I have of this book has a little more, and some slightly different content than the version I read on my Kindle. Again: “Early Access Editions” and all that… Borderline four stars … and I think when it ‘s completed and fully edited, it fair might be. ( disclosure : I read an early access edition ; O’Reilly [ 1 ] has been doing that a fortune recently … ) Elliott ‘s book fits neatly into that class of JavaScript books that are about praxis — books that are not about particular libraries or language features or programming paradigm, but about doing “ very exploitation ” on “ real teams ”. It is stopping point kin with Nicholas Zakas Maintainable JavaScript, and ( to an only slenderly lesser extent ) Addy Osmani ‘s Learning JavaScript Design Patterns. And like … Design Patterns, I found myself thinking once or doubly : This reserve is like that in that it is an excellent and timely model of “ how to do it the right room ” and/but it besides feels like it might be looking besides microscopically at specific libraries or techniques ? and consequently is it going to feel dated in 6-12 months ? [ 2 ] If you ‘re already reasonably knowing in the “ JavaScript practice book ” arena, then most of this is going to be reappraisal. Elliott covers functions as excellent objects and functional style JavaScript ( see besides Functional JavaScript, others ) ; vogue and linting ( see besides Maintainable JavaScript, others ) ; different approaches to the faculty blueprint and separation of concerns ( see besides : Learning JavaScript Design Patterns, others ) ; and some other subjects. [ 3 ] The one subject I saw in here that I had n’t seen anywhere else was on — which is something that I was very glad to see and is one of the reasons that I ‘ll be recommending this one to people looking to build “ master ” applications.The other thing I wanted to point out here was that Elliott goes back and forth between programming JavaScript for the browser and program JavaScript for Node, and the transitions are n’t always clear. I expect this will get cleaned up a act as they work it through editing for the final examination printed version. In either case, I am glad that he gives coverage to both in the same book, preferably than marginalizing one or the other to a ghetto chapter. — — Footnotes : [ 1 ] : To be fair : about all of the technical koran publishers that I know of are doing this recently — i, releasing “ early access Editions ” and “ MEAPs ” and the like. [ 2 ] : I go back and forth on this piece of criticism. If you ‘re “ all theory ” then you ‘re potentially losing out on providing some prize because you ‘re discussion is excessively far away from the real number problems ; but if you ‘re besides close to “ the very thing ” then you ‘re just talking about that specific situation or tool-chain and it winds up being about addressing that problem with that cock, and not very “ that class of problem ”. Elliott is somewhere in the middle here, listing only slenderly toward “ excessively specific ” and only in a couple of places. [ 3 ] : The PDF I have of this book has a small more, and some slenderly different content than the version I read on my Kindle. again : “ early access Editions ” and all that …

source : https://enrolldetroit.org
Category : Social

Trả lời

Email của bạn sẽ không được hiển thị công khai.