Live data from Hacker News

Single page apps in depth (new free book)

singlepageappbook.com

21–30 of 32 posts

Re: Single page apps in depth (new free book)

#21
post #8

Earlier quoted context omitted.

I'd say databinding is useful for smaller convenience plugins, not for the architecture of larger JavaScript applications. From my quick skim this book is spot on.

It is your opinion that the answer to making a larger JavaScript application is one big bucket of state Object? Tell me you've got something better than that.

Seriously? So you think Backbone.js and the like are just a fad?

Re: Single page apps in depth (new free book)

#22
post #21

Earlier quoted context omitted.

It is your opinion that the answer to making a larger JavaScript application is one big bucket of state Object? Tell me you've got something better than that.

Seriously? So you think Backbone.js and the like are just a fad?

I'm not fond of the way Backbone.js works. It solves none of the hard problems of making an SPA. (AngularJS is guilty of this too, albeit from a different angle.)

Re: Single page apps in depth (new free book)

#23
I'v did some single apps. * https://trakrapp.com/ (server's certificate has expired) an issue tracking app. with Backbone, Jquery. * http://mei.fm/create Wwn's online stack editing app. (need to signin to get full functionality). A team structure the code with the help of Jquery, Mustache.js, Underscore. * http://rssminer.net/demo .yet another RSS reader. I write it with Jquery, Mustache.js, Underscore.

Re: Single page apps in depth (new free book)

#25
post #19

Don't call this a 'book'. I know it is a great plug but it is simply not true.

It is not a book because...?

I find the layout awful for a print version. And the PDF document has chapter links that lead to the website, rather than the page in the PDF.

I can live with that if I generate a PDF from web content, but I'd expect a book to have a better print version and a better quality PDF version...

Re: Single page apps in depth (new free book)

#26
post #24

This is quite nearly the PERFECT book, one that every web developer should read front to back.

I haven't read through the whole thing [1], but I really like the fact that he actually discusses different approaches when trying to achieve a goal and instead of just mentioning them. He has an opinion and is not afraid to express it and that's good because it encourages thinking and discussion.

[1] Only read through http://singlepageappbook.com/detail1.html (on Views)

Re: Single page apps in depth (new free book)

#27
post #19

Don't call this a 'book'. I know it is a great plug but it is simply not true.

It is not a book because...?

What distinguishes a book is the 'form factor'. Obviously we are talking about an e-book. Nonetheless little care has been put into producing a 'book': not TOC, no index, no page numbers, etc.

(Obviously this is all independent of the content.)

Re: Single page apps in depth (new free book)

#28
post #27

Earlier quoted context omitted.

It is not a book because...?

What distinguishes a book is the 'form factor'. Obviously we are talking about an e-book. Nonetheless little care has been put into producing a 'book': not TOC, no index, no page numbers, etc. (Obviously this is all independent of the content.)

These are outdated requests, maybe with the exception of the TOC, which soon should also be taken care of by technology [1].

Regarding the index, if you are willing to visit the single-page version, a simple CTRL-F gives you the 70 references to "DOM", for instance. Your modern browser quickly shows how those references are spread in the document. That is pretty much an optimal index to me, with an unlimited number of entries, rendering the separate and physically constrained notion of index obsolete.

And why pages? In today's world of wildly diverse screen sizes and resolutions, please let the content flow. I remember being led to the wrong place of a book in my college years just because the edition I consulted happened to different from the author's, but I found that reasonable in the paper age. Semantically demarcated concepts such as chapters or sections have always been referred in this way, and rightly so. If you think about it, page numbers only helped you locate verbatim excerpts such as "to be, or not to be" in [2]. A completely valid and efficient artifact of the pre-digital era, which has now become dispensable, just as indexes have.

[1] http://dev.w3.org/html5/spec/headings-and-sections.html#outl...

[2] http://www.gutenberg.org/files/27761/27761-h/27761-h.htm

Re: Single page apps in depth (new free book)

#29

Earlier quoted context omitted.

It is not a book because...?

I find the layout awful for a print version. And the PDF document has chapter links that lead to the website, rather than the page in the PDF. I can live with that if I generate a PDF from web content, but I'd expect a book to have a better print version and a better quality PDF version...

A few years ago nobody criticized an author for calling his work a book if it didn't have an electronic version. We are now clearly in a transition phase [1], but it is plain that soon it will be acceptable and in fact expected to forgo the print edition when publishing "a book". A significant threat to content preservation, but that's another story.

[1] http://www.nytimes.com/2011/05/20/technology/20amazon.html

Post reply on HN