The book is in two sections, the first being an overview of just all what falls under the "mobile" umbrella and provides a few ways of organizing those pieces. It works to provide information applicable to the first two principles. The second section of the book focuses on the third principle and goes mostly deeply into mobile web applications, which Fling sees as the answer to the platform and carrier fragmentation present in other solutions. The question of web apps vs Native apps has created some interesting discussion and Fling falls into the 'leaning towards web apps' camp, though he is pragmatic throughout this book.

That pragmatism is extremely attractive and a large part of what makes this book worthwhile. It is obvious while reading that Fling doesn't just talk about how things should be done, but he follows his own advice in his writing and presents what he believes will make for the best solutions. If there is a place where idealism will lead to the quick and ugly death of an idea it would be the mobile space. Compromise isn't just something that may make sense at times, it is often forced right into the platform by carriers or others. Fling doesn't back away from this and acknowledges when there are multiple routes, none standing out as ideal. He is very up front in sections where his technical reviewers had other opinions and presenting other options that they felt might be better. Fling tries to give succinct coverage to what he sees as the better possible options and leaves the choices to the reader, now armed with enough information to dig deeper.

Fling's clarity and up front appraisal of the considerations in the mobile space lead to him describing one of the most prominent limitations of his own book. Besides the obvious that it can't go into great depth on every mobile technology there is the fact that this information has a limited shelf life. In the fifth chapter, Developing a Mobile Strategy, Fling gives a set of seven rules that he believes should be followed in the process of creating a strategy. The second rule is, Believe What You See, Not What You Read and the following chapter contains the admonition, "Don't trust any report, fact, or figure that is more than a year or two old. It is most likely wrong. For example, the majority of assumptions about mobile development pre-iPhone are no longer applicable." According to Fling, barring a revision this book has a shelf life of roughly a year or two. After that one should really be looking to more recent resources. On the other hand, anyone even thinking about jumping into the fray, should be reading this right now.

This limitation is the only thing that causes me to not rate the book as a 'classic' and it is not really the fault of the author. It is just a reflection of the rapid rate of change taking place in the world it describes. My only other problem with the book is small, though at times a bit annoying. The book is black and white, without any color illustrations. This in itself isn't a problem but the shades chosen for pie charts in more than one place are not sufficiently different to tell where one edge stops and another starts. Fling describes the charts, they are never floating alone without text that addresses them, so the reader doesn't lose information, just the opportunity to see it displayed in a visual format. I'm not a person with great visual design skills, so if I noticed I'm sure others involved in the production of the book have as well and hopefully later printings corrected this issue.

The first section, as I've described, is a high level overview of the mobile world. This covers what Fling thinks of as all the layers of the mobile ecosystem. This means everything from carriers to hardware manufacturers to operating systems and more. I've spent quite a bit of time over the last year reading up on much of what Fling covers here, but there were still pieces of new information that I found. Fling takes a global view and doesn't lean towards the situation as it is presented in any single geographical area. He is also dealing with all types of phones and platforms. While he obviously spends a lot of time, especially in the second section, dealing with more capable smart phones, he is still dealing throughout the book with less capable devices and systems. This is where Fling's experience really shines. He has navigated what it means to try and develop for less capable phones, the realistic challenges one faces trying to get onto more hardware and more networks. It is at times daunting, but I for one would rather walk into something knowing the reality rather than being uninformed.

Fling hits all the highlights from what is available to suggestions on the whole life cycle of a mobile product including prototyping, testing and adapting to various types of phones and platforms. The second section, dealing with more specifics on putting together a Web App will throw a bone to the developer that wants to see some code. While it is mostly mark-up Fling does spend time dealing with some specifics of implementing a WebKit compatible solution. He states that this will work on a few modern phones, though a few subsections do carry warnings that they are iPhone specific. Fling covers the use of XHTML, XHTML-MP, CSS, JavaScript, and other applicable web technology. This is probably where the management types will start to skim over things. I do think though it still serves the purpose of giving an idea of what is possible and when it is appropriate to choose a pure web application over a native application.

I think that Fling does an excellent job showing that it is important to create mobile applications that are designed purely with mobile users in mind. The last chapter is only a couple pages long and is the only place that Fling devotes purely to prognosticating. The rest of the book is practical and focused purely on what will work right now. In his closing thoughts, Fling essentially invites the reader to be a part of bringing about the future of mobile. I think this is very fitting as he has just given his readers what they need to set out on that path."
Link to Original Source

This sliver does a lot to reveal the similarities and differences. Brakebills is very much like Hogwarts in external ways, and completely different in substance. The school is for adults, not children and the life that Grossman portrays is much more in line with reality than fantasy. This is not a book to pick up for a young child. This story contains profanity, sexual content, graphic violence, as well as alcohol and drug abuse. This is where I ran into my first issue with The Magicians. I'll get to that shortly, but first I'd like to finish laying out what the book involves.

Not all of Brakebills is lifted straight from Hogwarts, though I don't think the reader with much experience in reading fantasy will find anything that could really be called new. What there is, as I have mentioned, is very well done. Grossman builds up to moments of palpable tension. He pulls the reader into the life of Quentin and shows real finesse at times. His characters very much come alive, in their brief moments of joy and in their many moments of pain, frustration and loss. Anyone who has felt the hurt of being outside, dealing with the cruelty of others or a general questioning of meaning will be able to relate well to the protagonist.

Eventually school is over and the students graduate. And here is the turn that I think the promotional material makes obvious but some may not want to know about going into reading the book. The second section of the story begins as Quentin and his fellow Brakebills alumni find out that Fillory is real. They immediately prepare to set out on an expedition to the land they've loved since childhood. That Fillory is better spelled N-a-r-n-i-a is just as obvious as the connection to Rowling's work. Quentin and company enter Fillory using magic buttons that take them to an intermediary world of fountains. Jumping into each fountain takes a person to a different world. They have to take care to jump into the correct pool at the base of the fountain that will take them to Fillory. Fillory is a land of talking beasts and magical creatures.

So what sets The Magicians apart from lesser books that lift heavily from other works? Why is The Magicians a strong story while something like Eragon is a weak rip-off? I think it boils down to two elements. First is Grossman's strong writing. Even if this were just a big piece of fan fiction, it would be well written fan fiction. Secondly, this isn't just an homage to the work of others. While Grossman has lifted the settings and externals, the substance is completely different often to the point of taking a position that is completely antithetical to the original work.

My first problem, which I tie to the very adult content is wrapped up in why I read fantasy. I read fantasy on many levels as a form of escape, much like Grossman's character Quentin did. Much of the fantasy I've read is not only fantasy but it is written for children. At the bottom of it all there is no real risk or fear. I read with anticipation, not of an outcome but rather how that outcome will be worked out by the author. There is often death or treachery but it takes on a fairy tale like quality. It does not feel real or cruel but rather cartoonish. Grossman completely jettisons any of this kind of approach. He tackles the safety of these children's tales and eviscerates it. The violence in The Magicians is not cartoonish, it is often cruel even sadistic. There's not much in the way of escapism here. What Quentin finds is that magic doesn't change the basic underlying facts of life, not even traveling to another world does this. This is combined with the fact that much of Grossman's realism includes behavior and speech that isn't something that I would consider normal or appropriate. It may be for others but this isn't a book I would feel comfortable recommending to friends or family.

Then there is my second issue. I've read that Pullman's His Dark Materials trilogy is intended to be a type of anti-Narnia. Well Grossman doesn't just create an alternative world that is contrary to Narnia. He destroys Narnia from the inside. And this caused issues for me in both sections of the book at times. Not because of ideological difficulties with what Grossman puts forward but because it would frequently push me outside the story as it felt like Grossman would move from telling his own story to commenting on the story of another. It isn't that what he has to say about the other stories isn't interesting and that he doesn't bring up intriguing issues and criticisms of both, but rather that it jarred me out of the narrative as the story became more a work of exposition. Something like the flashbacks to History and Moral Philosophy class that fill so much of Starship Troopers . The author shows his hand, that he is more interested in making a point than telling a story.

The fact that a major component of the book is polemic in nature means much of the discussion around the book will not be about plot or setting but rather about the argument the author sets forth. I don't agree with Grossman's premise or conclusions but I do admire how well he states his case throughout the entire book, not only in those portions that might feel a bit preachy. I've read in an interview Grossman did about The Magicians that he feels that Rowling lets her characters solve their problems, rather than resting on divine intervention like the characters of Lewis's works. This is reflected in how he handles the world of each, though I would argue that this is not the case, especially in light of how Rowling's series ended. I think it does explain why he is so much rougher on Lewis.

Anyone looking for a dark story that questions the assumptions and underlying principles of those that are not so dark should really enjoy this book. Any parent that picks it up for their young one because they hear it compared to Harry Potter is in for a rude surprise. Those looking for a fun little escape from the real world wont find it here, though things are so grim at times they may find the real world a bit of a relief after the weight of Grossman's. The Magicians held my attention and I was impressed with Grossman's ability, unfortunately at the same time I was a bit dissapointed with how he used that ability. With something this subjective your mileage may vary, and since release The Magicians has hit number nine on the New York Times best sellers list.

Viking set up a number of web sites to support the release of The Magicians. This is not so much about the book itself but will be of interest to readers and I think is an interesting development for book lovers in general. There are four sites TheMagiciansBook.com is a normal promotional site with information on the book. ChristopherPlover.com brings to life the fictional author of the Fillory books. Brakebills of course has a site, obfuscated just like the school itself. Finally there is Embers Tomb a wealth of Fillory related information. The Fillory and Plover sites come across as very genuine and will probably snag a reader or two into some level of confusion. The Brakebills site is a bit too over the top to be taken seriously but then again, with real news sites quoting The Onion and the occasional uproar I see over humor sites like Objective Ministries there probably will be some who think it is a real school."

I think the list is pretty solid. The only one I think may not be directly applicable to the case it hand is the FOSS angle. Warren explains that being open means that more can be done with the software and that there is a large set of corresponding code out there freely available. A case could be made that this is also true of more closed languages. The one thing I think that could make this important is if the teacher of the material is interested in not just teaching the technical side of programming but is also interested in communicating the philosophical values of freedom. In light of the amount of closed source software and ignorance in regards to FOSS options I've seen in the public school system where I live, I think this may be more important than some think.

The rest of the reasons though I think make Python an incredibly solid choice, and above all else is the simplicity. My daughter has been able to have fun typing code into IDLE without having to get hung up with a complicated environment. The syntax is clean and simple, there is no compiling, it's very easy to just jump in and start making things happen. I think this is important, the younger the student. I was concerned that nine might be just a touch too young for this undertaking. The book itself does not make any recommendations concerning age. The more I've thought about it, the more I agree with that choice. Children vary so greatly and any number chosen would be rather arbitrary. My nine your old has done well so far, but she is already quite a book worm and leans towards more academic pursuits. An older child may struggle and there may be some that are even younger that would be fine with the material in Hello World! So rather than focus on age I think a parent needs to come at this from a perspective of ability, proclivity and experience.

In the ability area, a child is going to know how to read, work with a mouse, and type things via the keyboard. Of course the mouse is optional strictly speaking but most will probably want to use it. Some math skill would be good as well as the ability to understand the use of variables. The book tackles the necessary material in a kid friendly way but it is not dumbed down. In fact the learning potential here is huge, as one may imagine. The book is formatted with lots of visuals and fly-outs that give information on how computers operate and how programming languages deal with information processing. My daughter and I have already had interesting discussions on subjects like integers and floats. An example that draws a sine wave lead to a great teachable moment about amplitude and wave length. Then there is the constant need for approaching problem solving in a structured manner using logic. I think that taking on programming brings a wide number of benefits.

One of the features, is a little caricature of Carter that is placed throughout the book with observations that the real Carter made as he learned with his dad. These are things that a real kid noticed, and so they are likely to stand out to a child working through this book. For instance in the chapter on "Print Formatting and Strings" Carter says, "I thought the % sign was used for the modulus operator!" The book explains that Python uses context to choose how the % sign is used. There are other little cartoon characters that appear throughout the book drawing attention to important points that need to be remembered. Learning is reinforced through quizzes at the end of the chapters. The chapters are not too long but I've found that my daughter and I have to break them into sections because of her typing speed. I've been tempted at times to move things along by typing for her but I know that she will not get the same benefit from the exercise if we do it that way. I will also let errors slide by at times to allow her the opportunity to look at error messages and find the problems.

As I mentioned the book is billed as being for kids and "other beginners." I'm going to say that the primary focus is rightly on kids, and probably kids who are in grade school or maybe junior high. This is not to say that the examples and information wouldn't be great for anyone brand new to programming. There are even some nuggets for someone who has written some code but is new to Python. I am going to guess though that the average high school student will not be as taken with the cartoons and puns. I'd have loved to have written my own lunar lander game at that age though, so maybe I'm selling this short, or maybe it would be something a teen would be happy to work on away from the eyes of others, so as not to appear childish. (I may take heat for this but even as a teenage geek I was immensely worried about the perceptions of my peer group.) I think an adult that was serious about learning to program, even if they had no prior experience, would do better with heavier material. All that said, I think for children they've really hit the sweet spot and as much as marketers would like it to be so, no book can be everything to everyone.

Things start simple with print statements and loops that took me back to good old days of watching messages scroll endlessly by on display computers at Sears when I was a kid. The move towards games starts even then with text and quickly moves on to leveraging Pygame for games that utilize graphics. I think this is important as it keeps things entertaining while teaching important concepts at the same time. I have to say it is quite a bit fun to sit with my child discussing nested loops and decision trees. By the end of the book examples will have included a simple virtual pet, a downhill skiing game and a lunar lander simulation.

I've discussed a child's ability a bit but I think the last two things I mentioned must be taken into account as well. They are proclivity and experience. I've let my daughter drive the time we spend working on this. Just like the parents who project their sports dreams on their kids, I think there is a possibility to do the same with my love for all things digital. It may even be easier to do so as I view the ability to do some amount of programming to be an important life skill. The thing is I don't want to push her too hard and have her back away from it completely. This fits in with the experience part. We take it as it goes, and if things stop being fun, we will back off. I don't do this with her core disciplines from school like reading and math, but for something that is extra right now I'm not going to push. It would transition from being a joy to being work. That brings up a last and unexpected benefit from Hello World! I'm rediscovering a lot of the fun and excitement that drew me into this industry in the first place."