Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Submission Summary: 0 pending, 108 declined, 67 accepted (175 total, 38.29% accepted)

×
Games

Submission + - SPAM: iWarrior: an African iPhone Game

stoolpigeon writes: "White African has a review up for iWarrior, a new game for the iPhone from Leti Games. The review mentions that this may be the first game fully developed by a team in Africa. The review also deals with some of the unique issues faced by developers and gamers in Africa. The reviewer finds some issues with the game but views it as a strong start for an emerging market."
Link to Original Source
Book Reviews

Submission + - SPAM: Android Application Development

stoolpigeon writes: "Google's mobile OS Android has received plenty of press. As with a lot of Google products, there was much anticipation before any devices were even available. Now a number of phones are available, with many more coming out world-wide in the near future. Part of the lure of Android is the openness of the platform and the freely available tools for development. The SDK and accompanying Eclipse plug-in give the would be creator of the next great Android application everything they need to make their idea reality. The bar to entry in the official Google Android Marketplace is very low and it doesn't seem to be much of a stretch to predict that the number of developers working on Android is only going to grow. As with any hot technology the number of books will grow as well and O'Reilly's Android Application Development has jumped into the fray, promising to help budding Android developers what they need to get started.

The book begins with a brief introduction to Android followed by detailed instructions on procuring and installing the Android SDK. Space is given to Windows, Linux and Mac. The install is relatively simple on all three platforms, extra information is provided for Ubuntu users but no others distributions. Extra care is taken to help Windows users with items they may not use regularly, such as environmental variables. This is all pretty basic and gives the book very much of a 'for beginners' feel. Before I had the book I had already installed the SDK and Eclipse plug-in on Windows, Ubuntu and Fedora without any issues beyond getting a current version of Eclipse for the Ubuntu machine. The version I already had from the Ubuntu repositories was not able to run the plug-in. It's a short chapter and if someone really struggles with it, they probably should shift their focus from learning to code to learning how to use their platform of choice. This does set the tone though, that this is a book for those who are very new to development.

Chapter two steps the reader through the ever present "Hello World" and gives an overview of the structure of Android applications. Chapter three introduces the example application that will be used for the rest of the book. There is a lot of repetition here on just what directories and files make up the guts of an Android program. I was quickly worried ( the first four chapters are only fifty-six pages in ) that maybe four authors had been too many. The repetition made it feel as if separate work had been combined without enough editing to remove what was redundant. Fortunately this got better, though there was still a strange proclivity to list files while referring to earlier chapters that explained their purpose. This would be helpful to anyone jumping right into the middle of the book, but the index also serves the same purpose and saves space for more valuable content, as opposed to explaining the purpose of AndroidManifest.xml repeatedly.

Once I moved into the fifth chapter, Debugging Android Applications and the following chapters, things got better. The pace picked up and the repetition dropped off for the most part. The book did not become incredibly difficult, trying to be everything to everyone, but did maintain an introductory style. At the same time the example application makes use of many Android features that are likely to be used by developers. How to set up and use tools was covered step by step. This is very nice but did cause some issues for the authors due to the rapid pace of development on Android. A visit to the book's errata page will show that many readers struggled with changes to the SKD tool set that came out very shortly after the book. The authors say that future editions will fix these issues, but this creates a dilemma for that reader needing introductory level materials. They are more dependent upon the book than a more advanced user and so these issues can be very trying. Based on the responses to the errata posts it became trying for the authors as well. This isn't a knock on the book itself but rather a limitation of the delivery method.

Once the reader is digging down into the example application the team approach to writing the book does become an asset. The authors bring a number of skills to the table that closely resemble the players that would be necessary to a team developing a real-world application. The reader is now being pulled into an example that benefits from the knowledge of each and does a good job of exploring the range of options an Android developer has available. This includes core functionality, UI options and how to best take advantage of the platform while at the same time taking performance and user expectations into account. I felt like I was getting something beyond the excellent documentation provided by Google. This is where I felt the book stood strongest.

Working with a single, large example application was a move that probably helped move things along on writing the book and I think it's an interesting approach. The problem is of course, that means that this example must be right. Right for the task and technically correct. Small issues in the code are inevitable but now their impact is book wide. The changes to the platform just made it just that much more difficult to sort out. On the whole I still found this to be a better approach primarily due to the fact that it gives the features highlighted a better sense of context. Stand-alone examples are often good at highlighting technical features but completely ignore the issues necessary to using the feature in a larger piece of code.

I'm a fan of O'Reilly books. Interestingly enough this doesn't mean that I'll gloss over issues with what they produce. The result is actually the inverse, in that I go into all their titles with a high level of expectation with regards to quality on every level. This may mean that though I strive to be neutral when I look at a book, I'm probably a little tougher on O'Reilly titles. This made my rough start with Android Application Development a bit jarring. The repetition and what felt like sloppy editing are not what I expect. I was quickly given a sense that this book may have been rushed to publication a little sooner than it should have been. As I moved deeper into the book, things improved and while I think there were still editorial issues, things did seem to smooth out to some degree.

There is an interesting tension that exists purely do to the nature of print books. I don't like to bring up print versus electronic in reviews as I don't think it is on topic, but here it is unavoidable. The book is aimed at people that need a little more hand holding and help getting going. It does a good job of providing step by step instructions, the problem is that some of those steps have changed. I don't think anything in the code itself needs to be different, but the tools have changed enough that getting the code to run in a development environment against the new SDK is different. That means that portion of the book is no longer of as much value without going to other sources to find the new steps.

That said, warts and all I found this to be a helpful way to get my feet wet with Android. I really look forward to future versions as I think just a little more time and work will move this from my 'good' list to my 'great' list. Making things a little tighter and cleaning up the few typos and errors would certainly make this an 8 instead of an 7, which is really substantial in my mind. I'm no super developer and I need stuff like this, that can take things a little more slowly and make it all clear. I think this guide is great for those of us in that category as long as the reader is o.k. with hopping to external sources for the information they'll need to get the newer tool set working.

Title: Android Application Development
Author: Rick Rogers, John Lombardo, Zigurd Mednieks, Blake Meike
Publisher: O'Reilly Media Inc.
Pages: 332
ISBN: 978-0-596-52147-9
Rating: 7/10
Tagline: Programming with the Google SDK.
Reviewer: JR Peck"
Books

Submission + - SPAM: Learning Ext JS

stoolpigeon writes: "Rich Internet Applications (RIA) have often been associated with some type of sandbox or virtual machine environment to make desktop features available via the web. Many applications though, have left behind the restrictions and demands of those technologies, implementing RIAs as pure web interfaces. One key technology in this area is JavaScript. It's been well documented that working with JavaScript can be problematic across various browsers. In response a number of JavaScript libraries have been created to alleviate the issues in dealing with different browsers, allowing developers to focus on application logic rather than platform concerns. One such library, focused on providing tools for building RIAs is Ext JS. For the aspiring developer looking to use Ext JS, Packt provides a guide to the library in the form of Learning Ext JS

The book is written for people with experience in doing web development. The authors state that a working knowledge of HTML and CSS are important, but experience with JavaScript is not essential. I think that a reader that has not used JavaScript may want to supplement this guide with something that covers the basics of JS. Experienced developers that haven't worked specifically with web programming should have no trouble keeping up. Anyone completely new to the idea of programming, scripting, markup, etc. really will need to take some time to get familiar with those concepts before they dive into this book. The authors do not spend time teaching programming, they are focused purely on realistic applications of Ext JS.

The authors begin by stating that, "Ext is not just another JavaScript library..." and it is understandable that they would feel this way. I am unsure why one wouldn't think so other than a personal preference for the product. That said Ext JS can be used alongside other JS libraries and does provide a lot of features 'out of the box' that make it an attractive choice. The emphasis on RIA widgets and building strong applications is nice as Ext JS is not working to be all things to all developers.

The book is heavy on code and examples but not so much so that it falls into the cook-book style of writing. Learning Ext JS is more of an extended tutorial with ample explanation to help the reader not only understand the code but why certain choices are made. Frederick, Ramsay and Blades have done a good job of working through the examples in a concise manner. While the book is the result of group work, it does not have the feeling of being written by a community. I did not run into an abundance of repetition and topics flowed well. Learning Ext JS also covers installation and integration of the library as well as a very quick survey of tools for development. While short these sections would be extremely important to anyone coming into web development with little experience.

It's a quick read, and doesn't delve extremely deeply into more advanced topics. Rather, a reader new to Ext JS will get a launch that should make the library usable in a practical way and also give them the framework to push deeper. The book was written and published just as Ext JS moved between versions. The new version is backwards compatible with the material in this book and a number of the changes in version three would not have fallen within the scope of this book, so it is still a good place to get started with Ext JS. Those who want to dig deeper will need to look elsewhere.

The brevity of the book wont work for those folks who want to really dig down deep into Ext JS. I on the other hand, wasn't looking for a massive tome to lug around and grind through. I was happy to have a very accessible tool that would get me started quickly and that is what I got. On the other hand I do like to be able to find what I need quickly and nothing is more important to me when learning than a solid index. Unfortunately the only really large ding I have for the book is that the index is weak. It would be a lot worse if the book were larger, so the brevity helps here a bit, but it's still unfortunate. This does make the ebook version a little more attractive. Packt will bundle them at a cost that makes the addition of the electronic copy very attractive. That said, the easy flow does it make it easy to read this book front to back while working the examples. Learning Ext JS just wont be my first choice when I need to quickly check a reference.

I've discussed the shallow coverage, but this does not mean that the book is not useful. The Ext JS library bundles enough functionality into the stock widgets, that decent applications could be written with nothing more. Creating custom widgets is covered and extending existing code as well, but this is later in the book. The material prior to that covers not only the use of the provided widgets but how to tie them together, theme an app and then handling data. This means the reader pretty much has everything in hand to build a stock application. The focus is on dealing with these issues on the client side. The examples do include a small amount of back end code when necessary for the execution of examples. All the examples are available to download from the Packt site and come packaged with all necessary scripts, images, etc.

I've always worked primarily with desktop applications. I've done some work with web applications, but it seems to me that increasingly the tools that I use the most are web based. With technology like Google Gears making those applications available whether I'm connected or not they have become much more attractive. Tools like Ext JS make it much easier for me to transition over to this new way of developing applications. I've found that Learning Ext JS has been a valuable resource in taking what is a great resource and allowing me to get the most out of it more rapidly than I would have otherwise. Reviewer: JR Peck Title: Learning Ext JS Author: Shea Frederick, Colin Ramsay, Steve 'Cutter' Blades Publisher: Packt Publishing Pages: 309 ISBN: 978-1-847195-14-2 Rating: 8/10 Tagline: Build dynamic, desktop-style user interfaces for your data-driven web applications."
Books

Submission + - SPAM: The Magicians

stoolpigeon writes: "The popularity of web site Will It Blend? is indicative of how people enjoy mashing things together. Of course this kind of sharing and combining has been going on in the arts for quite some time. The new Lev Grossman novel, The Magicians asks 'will it blend?' of two rather popular fantasy series, J.K. Rowling's world of Harry Potter and the tales of Narnia from C.S. Lewis. Grossman's thoughts on both are tossed on top and then the author begins to play a symphony across the full range of buttons from stir to liquefy. What comes out is not children's fantasy but at times a rather bitter mix.

Grossman is an author and critic for Time and has written for a number of high profile magazines. He is a talented writer and handles his story telling with skill. His characters have depth and this story takes on a very gritty sense of reality, something that is not often found in fantasy. I was impressed with his writing, yet at the same time I was torn with how I felt about the book. I found it to be compelling and at the same time difficult. It took me a few weeks to process the whole thing and get an idea of why the book impacted me the way that it did. I'm going to lay that all out now, but I have to say that when reviewing fiction I work very hard to avoid discussing plot. In this case, it will be impossible to some extent. I don't think I'm going to give away anything that the promotional material doesn't make pretty obvious, but anyone who wants to go into this book knowing as little as possible should stop reading now.

The protagonist, Quentin Coldwater is a nerd. He's an academic over-achiever living a life of privilege, set on a path of success. He's also extremely unhappy, feeling disconnected from the rest of the world. He struggles with his inability to connect with others and the meaninglessness of life. He has sought out and found some respite in the fantasy world of Fillory. A magical land created and explored in the books of an American author that lived in England. At the start of The Magicians Quentin in on his way to an interview as part of the admissions process for Princeton. But this does not end up as another normal day for Quentin. Rather than his ultimate destination, Princeton, Quentin ends up at Brakebills. Brakebills is a university in upstate New York where students learn magic.

While Hogwarts was not the first literary school of magic, it is the model Grossman has in mind and he is very up front about that fact. The students take part in a magical game called Welters. At one point a team member of Quentin's, Josh, is absent at the start of a match. Quentin hunts him down and the following interaction takes place between the two of them.

Josh stood up. He saluted smartly. "Send me an owl."

"Come on, they're waiting for us. Fogg is freezing his ass off."

"Good for him. Too much ass on that man anyway."

Quentin got Josh out of the library and heading toward the rear of the House, though he was moving slowly with a worrying tendency to lurch into door frames and occasionally into Quentin.

He did an abrupt about-face.

"Hang on," he said. "Gotta get my quidditch costume. I mean uniform. I mean welters."

"We don't have uniforms."

"I know that, " Josh snapped. "I'm drunk, I'm not delusional. I still need my winter coat."

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."

Robotics

Submission + - SPAM: Where's Waldo? 1

stoolpigeon writes: "Scientists on Florida's Gulf Coast are trying to find an underwater robot that has mysteriously vanished. The robot from the Mote Marine Laboratory in Sarasota has been missing since Monday. The robot, which cost about $100,000, also was equipped with a detector to find red tide, a toxic algae bloom. The detector was valued at another $30,000. Scientists aren't sure what happened to the robot, which is nicknamed Waldo."
Link to Original Source
Programming

Submission + - SPAM: Hello World!

stoolpigeon writes: "Hitting middle age has been an interesting time. I catch myself thinking about how well kids have it today and sounding a lot like my father. One difference is while my dad was happy to teach me about sports or cars, we never spent any time knocking out code together. I think he did realize that home computers were important and I will always be grateful for the Commodore Vic-20 be brought home one day. It was a substantial purchase for our household. I spent many days copying lines of basic from magazines and saving the results to cassette tapes. In my home today we have a considerably better situation, computing wise. There are usually a couple laptops running as well as the desktop machine upstairs. My kids take for granted what I found to be amazing and new. Still, that's all pretty normal and I'd like to give them an opportunity to go deeper if they are so inclined, just like we give them opportunities to explore other skills and pursuits. With that in mind I brought a copy of Hello World! home a few weeks ago, and the response from my oldest has been surprisingly enthusiastic.

Warren Sande wanted to teach his son Carter about programming but had difficulty finding what he thought was a suitable book to guide the process. At the encouragement of Warren's wife, he and Carter decided to write their own while Carter learned to code. Warren chose Python as the language they would work in and then the two together outlined the book and created the sample applications. As the book moves into more complex territory the sample applications are the kind kids like best. They are games. As soon as my daughter saw that she would get to make her own computer games she immediately asked me if we could start working through the book together. When it has been a while since we've had a chance to crack it open, she reminds me by asking when we will get back to it. I would say that on her end it has been a complete success. It has been a great time for us as father and daughter and educational for us both.

Language choice can be quite a hot topic amongst us geeks. In the preface Warren defends his choice of Python with a bullet list I'll summarize here.
  • Python was created from the start to be easy to learn.
  • Python is free.
  • Python is open source software.
  • Python is not just a 'toy' language.
  • Python is multi-platform.
  • Warren likes Python and thinks others will like it too.

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."

Social Networks

Submission + - SPAM: The Twitter Book

stoolpigeon writes: "Microblogging service Twitter has undeniably been a hit, with growth rates that were at times in excess of 1400%. The growth was rapid enough that the site became well know for its periodic and at times extensive downtime. Even with these issues, the service continued to grow rapidly, and with celebrities getting into the mix Twitter was quickly on the radar of mainstream media. The ubiquity of twitter and ever increasing coverage of 'tweets' has also brought the inevitable backlash. As with anything that gains high profile popularity there are plenty of Twitter haters out there, though the role that Twitter has played in the recent Iranian elections seems to have brought more legitimacy to Twitter in the eyes of many. With popularity come books and quite a few are already out there about and for twitter, but my favorite so far is The Twitter Book by Tim O'Reilly and Sarah Milstein.

What makes The Twitter Book work so well is that it functions in a manner very similar to the service it describes. The book itself is small, 8x5.9x0.7 inches, and the font is a bit larger than most tech books. This means the most text dense pages probably contain the same content as one third of a page in a traditional O'Reilly book. Most pages aren't text though, there is a liberal use of color, bold text and graphics. When a page is relatively heavy on text, the facing page will be equally focused on graphics with pictures, graphs or large colored bubbles around text.

All this combines to make The Twitter Book contain many of the same elements that create such a passionate response, positive or negative, to Twitter itself. This means if someone absolutely hates twitter, can't think of a single reason it should exist and wishes it would go away; they are probably not going to like this book. On the other hand anyone that loves Twitter and wants to learn all the ins and outs of the service, there is a high likelihood they are really going to take to this guide. It's format is one of those genius moves that seems incredibly obvious in hind sight. When I've shown it to other fans of Twitter, the usual initial response has been, "A twitter book, really?" and they are not all that enthusiastic. But once I start flipping through it and letting them see the way it is formatted, the reception becomes much warmer and quite a few have quickly flipped from skepticism to a desire to take my copy.

O'Reilly and Milstein both have been using the Twitter platform extensively and speak from experience and data that backs up their assertions. The format may make the whole thing look rather simple, but there is a lot going on here and one can very easily find a lot of bad advice out there on how to get the most out of Twitter. The Twitter Book leaves the reader in good hands that have already tread the paths they lead one down.

Of course this does raise and important question, is a guide to microblogging really necessary? All one does with twitter after all, is post 140 word updates. If kids can text vociferously, who needs how to do the equivalent to a web site? Well, there are two things in play that I think make this worth having. The first, and I think possibly the more important, is that Twitter is a social service. Beyond the simple technical aspects of the various clients, and technologies supported for the sending and receiving of tweets, there are the mores and customs of what has already become an established community. O'Reilly and Milstein aren't just guiding the reader through a simple how to, they are giving an introduction to a massive community that can save the reader from making more than a few mistakes that could really make getting going with microblogging a rough start.

The second reason is that while basic twitter functionality is drop dead easy, some of the more powerful or useful features are not built into twitter itself. They are methods and tools that have come up from the user base itself. Some of them require a little thinking outside the box as it were and are not immediately obvious. Others do seem incredibly simple once they've been implemented but their simplicity belies their usefulness. The book gives solid information on third party clients and tools. Tips on use are backed up with statistics on existing use within twitter.

As this is The Twitter Book, I have been talking about Twitter quite a bit. I'm sure the name is going to help the book sell but much of the information is just as valuable in the context of microblogging in general as opposed to just Twitter. The only real exception may be the clients and tools mentioned previously. Some of them have been slow to support other platforms. I think this book is just as useful still, to anyone microblogging with another service such as idenit.ca. Identi.ca is built on the free and open Laconica software. I personally base all my microblogging from identi.ca and forward things over to twitter. I still interact on twitter because at this point is where the majority of the players are at. But the social guidelines and strategies laid out in The Twitter Book carry over directly to identi.ca.

I don't really have any issues with the book. The scope is purposefully narrow and within the defined limits the authors have covered everything very well. I'd have loved to see something on identi.ca or Laconica but that would have widened the scope quite a bit and I think we can all relate to hating scope creep in a project. SlideShare has a nice preview of the book. Of course this format is not suited to every purpose. Any in depth study of just what makes twitter so popular and the impact it is or is not having on society will need to take place in a manner more suited to such topics. This is simply a case of using the right tool for the job. But dismissing this format as useless would be a mistake it is uniquely appropriate to the job at hand. I think this book is a lot like a screw driver. When used in the manner intended, no tool is better at the job. The only way to break a screw driver is to use it in an unintended way. In that case it isn't the tool's fault. Looking for a meaty discourse on the pros and cons of twitter? Do not look here. But if getting the most out of the service is the goal this may just be the best tool available."
Programming

Submission + - SPAM: CJKV Information Processing 2nd ed.

stoolpigeon writes: "The end of last year I made a move from an IT shop focused on supporting the U.S. side of our business to a department that provides support to our operations outside the U.S. This was the first time I've worked in an international context and found myself running into long time assumptions that were no longer true on a regular basis. My first project was implementing a third party, web based HR system for medium sized offices. I found myself constantly missing important issues because I had such a narrow approach to the problem space. Sure I've built applications and databases that supported Unicode, but I've never actually implemented anything with them but the same types of systems I'd built in the past with ASCII. But a large portion of the worlds population is in Asia, and ASCII is certainly not going to cut it there. Fortunately a new edition of Ken Lunde's classic CJKV Information Processing has become available and it has really opened my eyes.

CJKV Information Processing has a long history that actually goes back into the 1980s. It began as a simple text document JAPAN.INF, available via FTP on a number of servers. This document was excerpted and refined and published as Lunde's first book in 1993, Understanding Japanese Information Processing. Shortly after JAPAN.INF became CJK.INF and the foundation for the first edition of CJKV Information Processing was born. The first edition was published in 1999, and it is safe to say that a number of important things have changed over the last 10 years. Lunde states four major developments that prompted this second edition in the preface. They are the emergence of Unicode, OpenType and the Portable Document Format (PDF) as preferred tools and lastly the maturity of the web in general to use Unicode and deal with a wider range of languages and their character sets.

Lunde sets out not to create an exhaustive reference on the languages themselves, but rather an exhaustive guide to the considerations that come into play when processing CJKV information. As Lunde states, "..this book focuses heavily on how CJKV text is handled on computer systems in a very platform-independent way..." Taking into account the complexity of the topic, the breadth of the work and the degree to which it is independent of any specific technology, outside a heavy bias for Unicode, is extremely impressive. A glance over the table of contents show just how true this is. Chapter 9, Information Processing Techniques has sections touching on C/C++, Java, Perl, Python, Ruby, Tcl and others. These are brief, with most examples in Java but that they are all directly addressed shows a great awareness of the options out there. The sections that deal with operating system issues have the same breadth. Chapter 10, OSes, Text Editors, and Word Processors doesn't just hit the top Mac and Windows items. It looks at FreeBSD, Linux, Mac OS X, MS Vista, MS-DOS, Plan 9, OpenSolaris, Unix and more. There are also sections for what Lunde calls hybrid environments such as Boot Camp, CrossOver Mac, Gnome, KDE, VMware Fusion, Wine and the X Window System. Interestingly the Word Processor system covers AbiWord and KWord but not OpenOffice.org The point stands that anyone looking to support CJKV, this book will probably cover your platform and give you at the very least a starting point with your chosen tool set.

That said, an extremely specific implementation is not what Lunde is out to offer up. This is the very opposite of a 'cook book' approach. This also makes the book extremely useful to anyone dealing with internationalization, globalization or localization issues regardless of character set or language. Lunde teaches the underlying principles of how writing systems and scripts work. He then moves to how computer systems deal with these various writing systems and scripts. The focus is always on CJKV but the principles will hold true in any setting. This continues to be the case as Lunde talks about character sets, encoding, code conversion and a host of other issues that surround handling characters. Typography is included, as well as input and output methods. In each case Lunde covers the basics as well as pointing out areas of concern and where exceptions may cause issues. The author is nothing if not thorough in this regard. His knowledge of the problem space is at times down right staggering. Lunde also touches on dictionaries as well as publishing in print and on the web.

The first three chapters set the table for the rest of the book with an overview of the issues that will be addressed, information on the history and usage of the writing systems and scripts covered and the character set standards that exist. This was a fascinating glimpse, once again into CJKV languages and how other languages are dealt with as well. I think there is even a lot here that would be extremely informative to a person who wants to learn more about CJKV, even if they are not a developer that will be working with one of the languages. That's only the first quarter of the book, so I don't know that it would be worth it from just that perspective, but it is definitely a nice benefit of Lunde's approach.

The style is very readable, but I wouldn't just hand this to someone who didn't have some familiarity with text processing issues on computer systems. While there is no requirement to know or understand one of the CJKV languages, understanding how computer systems process data and information is important. I did not know anything about CJKV languages prior to reading the book and have learned quite a bit. What I learned was not limited to the CJKV arena. The experience I had was very similar to when I studied ancient Greek in school. Learning Greek I learned much more about English grammar than I had ever picked up prior. Reading CJKV Information Processing I learned quite a bit more about the issues involved in things like character encoding and typography for every language, not just these four. But in dealing with CJKV specifically I've found that Lunde's work is indispensable. It is not just my go to reference, it's essentially my only reference. If any other works do come my way, this is the standard against which they will be judged.

There are thirteen indexes including a nice glossary. Nine of them are character sets, which were printed out in the longer first edition. In this second edition, there is a note on each, with a url pointing to a PDF with the information. It seemed odd, but each URL gets it's own page. This means there are nine pages with nothing but the title of the index and a url. Fortunately they are all in the same directory, which can be reached directly from the books page at the O'Reilly site. It seems it would have made sense to just list them all on a single page, but maybe it was necessary for some reason. It's a minute flaw in what is a great book.
"
Operating Systems

Submission + - SPAM: A Practical Guide to Ubuntu Linux 2nd ed. 1

stoolpigeon writes: "One thing I love about Linux is the rapid development and frequent updates that allow me to run the latest versions of all my favorite software packages. My favorite distributions make it simple to always have the latest and greatest. In fact the distros themselves roll out new version regularly and I am always excited to see what new packages and features will be included. For book publishers this must be a little less exciting. Anything tied to a specific product that is under active development is going to quickly be behind the times. Mark Sobell's A Practical Guide to Ubuntu Linux managed to avoid the worst of this by providing a lot of information that is useful for any Linux user running any distro. But still things move forward and almost exactly a year later we have A Practical Guide to Ubuntu Linux 2nd ed.. I was very pleased with the first edition and I think they've managed to really improve what was already a solid resource.

Let's kick things off with a rough diff on the two editions. There have been improvements made in content and some added tools to rapidly get at what one needs. With the size of the book and the amount covered, these rapid access improvements are significant. The inside of the cover on the second edition has a utility index, so that a reader searching for help with any specific utility can find it quickly. This is followed up with two tables of contents, one a brief summary and the second much more detailed and taking up twenty-two pages. The new edition is about sixty pages longer than the first, but is slightly thinner and shorter. It is still a beefy book, but this is a nice direction to move.

After the tables of contents there is a list of JumpStarts. These are new to the second edition. They are short guides to getting started with key clients and servers. They come at the beginning of sections that will deal with the topic in more detail, but up front the focus is just on getting things up and running. The JumpStarts cover APT, CUPS, OpenSSH, FTP, exim4, NFS, Samba, DNS, firestarter and Apache. These are nice, as often just getting things going is the biggest hurdle and fine tuning is rather easy once that is past.

Like the first edition a DVD is included. As I mentioned Linux is a quick moving target and the dvd contains Ubuntu 8.1. It can be used as a live dvd or to do an install. Last time I checked the Canonical store, this was still the most recent version available on DVD. Ubuntu and Kubuntu 9.04 are available online and on CD. I did an install from the book's dvd and the upgrade to 9.04 was completely painless. I don't really see the DVD as a necessary addition but it could be a nice plus for anyone that wants to get Ubuntu up and running but can't get the bandwidth to download it.

The section Programming the Bourne Again Shell has been removed from the Digging Into Ubuntu Linux section and placed in its own section, Programming Tools which also includes a new chapter on Perl. The chapters on Linux utilitie and the Linux file system have also been extended. Coverage of ufw was added to the firewall chapter. The appendices remain the same but three new indices have been added to cover JumpStarts, the file tree and utilities. The main index is huge, offering excellent access to everything in the book. This book shows excellent forethought from start to finish aimed at making it a natural choice to grab from the shelf whenever an Ubuntu user has a question.

This did leave me wondering though, why no database server is included in the coverage. It seemed odd to cover Apache but not the rest of the LAMP stack. Installing MySQL and PHP are simple with Ubuntus package manager, but knowing the basics of caring for them is just as important as it is with Apache, which is also easy to install. I realize that the book is already large, but I'd have liked to see this included. That said, configuring services is covered and indexed in mulitple places. This means if one did install MySQL, PostgreSQL or some other database and were looking for how to go about starting, stopping, etc. the information is there.

As before, this is still a nice guide to Linux in general. While it is most applicable to Ubuntu, much of the information is accurate regardless of the distro in question. The style is understandable and there are many examples with code or illustrations as appropriate. This entire book is a real boon to any neophyte that does not have a solid handle on getting their own answers. That group is the one that I think will benefit the most from A Practical Guide to Ubuntu Linux. Random access is easy, but reading cover to cover would also give one a nice foundational understanding of getting the most out of their machine and even enough guidance to get their feet wet in the sysadmin world. Anyone thrown into owning an Ubuntu server may find this to be a handy lifeline. More experienced users, even if they are moving from another distro may find that there is just too much material that they don't need and already know. This really is a basic Linux guide first and an Ubuntu book second.

I thought the first edition was a solid value and the second edition offers welcome improvements with no real missteps. That they managed to put more in, not take a lot out and get it into a smaller package is quite a plus. I don't think anyone will be throwing this in a bag and carrying it with them any time soon, but it's a great office shelf resource for a quick refresher or getting launched. This is the kind of guide that can make the difference between frustrated failure and passion for anyone just starting out with Linux."
Google

Submission + - SPAM: Scripting Arrives for Android

stoolpigeon writes: "Google has announced availability of the Android Scripting Environment(ASE). The ASE brings scripting languages to Android by allowing you to edit and execute scripts and interactive interpreters directly on the Android device. Scripts can be run interactively in a terminal, started as a long running service, or started via Locale. Python, Lua and BeanShell are currently supported, with plans to add Ruby and JavaScript support, as well."
Link to Original Source
Robotics

Submission + - SPAM: Wired for War 1

stoolpigeon writes: "The US Army's Future Combat Systems program calls for one third of their fighting strength to be robots by 2015. The American pilots seeing the most combat in Iraq and Afghanistan right now, do so from flight consoles in the United States, and they are controlling Predator unmanned vehicles. Every branch of the U.S. military has aggressive robotics programs in place. This is not anything unusual. Other nations are also developing and purchasing robotic systems designed to be used in combat. Advances in communications, software and hardware make it inevitable that robotics will have a profound effect on conflict in the future. The development of these systems has been rapid and while technology hurtles forward, culture and understanding seem to lag behind. Similar to the way our legal codes are playing catch up with new technologies, combat enabled robots raise questions and issues that did not even exist a short time ago. Wired for War by Dr. P. W. Singer is an excellent opportunity for anyone interested to dive into just what is going on all over the world with regards to robotics and their use by the military.

Singer is Senior Fellow and Director of the 21st Century Defense Initiative at the Brookings Institution. His focus and study on changes in modern warfare have made him one of the world's top experts on the nature of modern day combat as well as what developments are likely to come. Singer is an academic, but Wired for War is not a strictly academic approach to the issue of robots in war. He has made an intentional effort to make the book approachable, delivering a large amount of information wrapped in the context of popular culture and current events. The average geek is going to feel right at home in the sea of references made throughout the book as they often turn on sci-fi. This is not to say that the book dwells in a possible future of far-flung vaporware. Wired for War is divided into two large sections. The first is "The Change We are Creating" and deals with the definition, history and current technology of robotics. Some of this is talking about robotics in general but primarily with a view to military applications. Singer makes it clear that he believes that robotics is going to have a huge impact on many more areas of society and culture, but war is the focus of this work.

The last chapter of the first section, "The Refuseniks: The Roboticists Who Just Say No" is an interesting look at those who are not comfortable with the direction they see technology being deployed. It makes for a very natural segue into the second section, "What Change is Creating for Us". It also serves as an excellent illustration of just what Singer does in this book. There is not a lot of highly technical detail or information. The discussion of various technologies in play deals primarily with capabilities available as opposed to how those capabilities are achieved. This is in keeping with Singer's stated desire to keep the book open to a wide audience. It also serves to reinforce what I believe is the real purpose of the book, though it is more subtly stated. That purpose is to educate the members of democracies on what is going on in the militaries of their nations, so that they can be more informed in how they participate in the political process. This is as much a sociology book as it is a technology book and as much as it gives insight into how the military uses technology it also gives insight into military trends and subcultures. Primarily the examples given and information shared deal with the U.S. military. The Chinese military gets some time as well but it is quite small in comparison.

This would probably be my only disappointment with the book. (Well there are two but the second is very specific and small. John Scalzi is called Joe Scalzi on page 369 and in the index.) It is understandable that most of the information is U.S. centric. Singer has been involved with America's Department of Defense and the American military is one of the few that is spending the amounts of money they spend on such a wide array of robotic systems. Singer does discuss how others are getting into the game, and even how less likely players, like insurgents can make use of robotic tech, but there is never the same depth of analysis and information for any other nation as the U.S. It's not that large an issue, the book is still excellent but I would love to see a work of the same depth and breadth that dealt solely with abilities and programs that are not American.

As I mentioned the second section deals much more with how all of this change is apt to change us. Singer deals with questions about not only what robots do to war but what they do to warriors, military leaders, governments and civilians. There is a lot here to chew on and to be honest I found the book to be more than a little frightening at times. Singer doesn't just point out new machines and revel in the engineering challenges that have been overcome. He digs in to see what the ramifications are for all of us and some of it could be very bad. At the same time Singer is not against technology and can see the good side of many developments. I think that what he fears most is that many will remain ignorant of just what is taking place and by the time they are all playing catch up it will be too late. I try to stay current on unmanned systems and military changes but there were quite a few revelations to me in the pages of Wired for War. Singer does not shy away from tough questions and I think his previous experience studying warfare, especially in the third world, comes to bear.

This isn't just a book for gun nuts that love to see stuff explode. This is a book for anyone who wants to be up to date on the technological changes that have come and are coming to warfare. As I mentioned, Singer emphasizes the importance of being informed about these things for the members of any democratically governed society. The people of such a nation are culpable in the actions of their leaders and how force is is deployed against others. How can they rightly use the power they have if they are ignorant of the capabilities and the very nature of the systems their military uses? And even more importantly what happens if they do not question the changes in perspective that robots in warfare bring not only to those who deploy such systems but to those who are the targets of automated violence and finally those who look on from the sidelines?

The book covers a lot of ground but does so in an eminently readable way. Part of this is that the notes do not occur at the bottom of the page but at the back of the book. In the back they are numbered but those numbers are not placed in the text. This can make it very difficult to find just how the information fits together. I can see the up side of not interrupting the flow but at the same time it could be frustrating working my way through to be sure I had found the matching note. This also reflects the book having part of one foot in the academic world while the rest of it stands closer to popular literature. The index is decent. This book will in all likelihood be quoted quite a bit and stand as the standard on military robotics for a while. There is a center section of black and white photographs featuring current robotic systems, military and civilian.

Singer addresses the debate over the rate of change in technology and the views of some that we are approaching the singularity where all bets will be off. Whether or not change is gaining momentum at an exponential rate, it is taking place quickly and at some point the technology that Singer covers will be old news. That said, the majority of the attention is given to questions and issues revolving around ethics and morality that will not go away any time soon. This book is going to be a fascinating read for many while educating and expanding their horizons at the same time. I recommend it without reservation."
Businesses

Submission + - SPAM: EFF Launches TOS Tracker

stoolpigeon writes: ""Terms of Service" policies on websites define how Internet businesses interact with you and use your personal information. But most web users don't read these policies — or understand that the terms are constantly changing. To track these ever-evolving documents, the Electronic Frontier Foundation (EFF) is launching "TOSBack": a "terms of service" tracker for Facebook, Google, eBay, and other major websites."
Link to Original Source

Slashdot Top Deals

Happiness is twin floppies.

Working...