Slashdot Mirror

jamie writes "Facebook's security team opens up, shedding light on a revolution that could become a parable for Internet activism. Quoting: 'After more than ten days of intensive investigation and study, Facebook's security team realized something very, very bad was going on. The country's Internet service providers were running a malicious piece of code that was recording users' login information when they went to sites like Facebook. By January 5, it was clear that an entire country's worth of passwords were in the process of being stolen right in the midst of the greatest political upheaval in two decades. Sullivan and his team decided they needed a country-level solution — and fast. Though Sullivan said Facebook has encountered a wide variety of security problems and been involved in various political situations, they'd never seen anything like what was happening in Tunisia.'"

brothke writes "When someone calls 911 in a panic to report an emergency, within seconds the dispatcher knows where the call is coming from, and help is often only moments away. When it comes to computer security incidents, often companies are not as resilient in their ability to quickly respond. Take for instance the TJX Cos. data breach, where insecure wireless networks were compromised for months, revealing millions of personal records, before they were pinpointed and finally secured. Once made aware of the issue, it took TJX an additional few months until the situation was completely in control and secured. In Computer Incident Response and Product Security, author Damir Rajnovic provides the reader with an excellent and practical guide to the fundamentals of building and running a security incident response team. The book is focused on getting the reader up to speed as quick as possible and is packed with valuable real-world and firsthand guidance." Read on for the rest of Ben's review. Computer Incident Response and Product Security author Damir Rajnovic pages 256 publisher Cisco Press rating 8/10 reviewer Ben Rothke ISBN 1587052644 summary Provides a good overview of the topic of computer incident response and product security Be it a IRT (Incident Response Team), CIRT (Computer Incident Response Team), CERT (Computer Emergency Response Team), or CSIRT (Computer Security Incident Response Team); whatever the term used, companies desperately need a process and team to formally respond to computer security incidents. The simple equation is that to the degree the incident is quickly identified, handled and ameliorated; is to the extent that the damage is contained and limited.

At just over 200 pages, the books 13 chapters provides an excellent foundation on which to start a CIRT. The book is divided into two parts. Chapters 1-6 form part 1, Computer Security Incidents, with part 2 being on Product Security.

Chapter 1 provides a basic introduction to the topic on why an organization should care about computer security incident response. This brief chapter touches upon the various business impacts, in addition to the legal and other reasons necessary for establishing a CIRT.

Chapter 2 lays down the 6 steps in which to establish an IRT, which are: defining the constituency, ensuring upper-management support, obtaining funding, hierarchy, team structure and policies and procedures. Each of these steps is crucial, and a mistake too many organizations make is to leave one or more out. Only later when an incident occurs, which often takes an inordinate amount of time to fix, do these companies realize that their IRT was incomplete and inadequate in the first place.

The chapter includes an interesting look at the various types of IRT teams that can be created; namely central, distributed or virtual. The book notes that if you don't have sufficiently strong support from senior organizational executives to form a real IRT (which should be a huge red flag right there), a virtual team is a good option. Virtual teams can be easier to set up as they are less formal with fewer bureaucratic hurdles. While there are benefits to a virtual IRT, companies that are truly serious about computer security will ensure that they have a formal and dedicated IRT in place.

In chapter 3, Operating an IRT, the author details the items needed to successfully operate an IRT. One of the soft skills the author discusses is effective interpersonal skills. The author writes that one situation that can arise when handling an active incident is that the person reporting the incident may say offensive things or become abusive to the IRT analyst. This behavior is generally the consequence of the attack, indicating its urgency. When dealing with such a person, it is imperative that IRT analyst not get caught up in the user's behavior. Rather they must focus on determining the appropriate method to fix the problem.

While part 1 is around the computer security incident itself, part 2 deals with product security. Most organizations create their IRT around computer security incidents. In chapter 8, the author writes about the need to create a product security team (PST) to deal with security issues related to vendor products.

Every software and hardware product has security flaws, be it Cisco, Juniper, Check Point and others. By understanding this and having a PST to deal with vendor security issues, a company will be adequately protected. In truth, only large companies will have the budget to support an independent PST in addition to an IRT.

In many ways, the PST is simply a specialized section of the IRT, with specific expertise around a specific product set. Many firms already have some sort of PST in place to deal with Patch Tuesday, which is the second Tuesday of each month when Microsoft releases security patches.

Overall, Computer Incident Response and Product Security provides a good overview of the topic. At 215 pages, the book should be seen as an introduction to the topic, not a comprehensive reference. The reason is that a topic such as security incident response requires much broader coverage given the extent of the requirements encompassed. In some ways though, its conciseness is its advantage, as a 750 page tome, while adequate for the subject, may overwhelm many, if not most readers. Also, the author has the ability to adequately discuss topics in a manner while brief, does cover the topic issues.

At $49-, the book is moderately priced, given the value of the content. For those on a limited budget, the Handbook for Computer Security Incident Response Teams from CERT provides a good overview of the topic. While the handbook was last revised in 2003, much of the core concepts around incident response are immutable.

As this title is from Cisco Press and the author an employee of the Cisco Product Security Incident Response Team (PSIRT), the book has a definite Cisco slant. While Cisco products are often referenced, this though is not a book from Cisco marketing. More importantly, as part of the Cisco PSIRT, the author has first-hand knowledge of one of the world's premier IRT.

For those serious about computer security and incident response, Computer Incident Response and Product Security should be one of the required books for every member of the team.

Ben Rothke is an information security professional and the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Computer Incident Response and Product Security from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

brothke writes "When someone calls 911 in a panic to report an emergency, within seconds the dispatcher knows where the call is coming from, and help is often only moments away. When it comes to computer security incidents, often companies are not as resilient in their ability to quickly respond. Take for instance the TJX Cos. data breach, where insecure wireless networks were compromised for months, revealing millions of personal records, before they were pinpointed and finally secured. Once made aware of the issue, it took TJX an additional few months until the situation was completely in control and secured. In Computer Incident Response and Product Security, author Damir Rajnovic provides the reader with an excellent and practical guide to the fundamentals of building and running a security incident response team. The book is focused on getting the reader up to speed as quick as possible and is packed with valuable real-world and firsthand guidance." Read on for the rest of Ben's review. Computer Incident Response and Product Security author Damir Rajnovic pages 256 publisher Cisco Press rating 8/10 reviewer Ben Rothke ISBN 1587052644 summary Provides a good overview of the topic of computer incident response and product security Be it a IRT (Incident Response Team), CIRT (Computer Incident Response Team), CERT (Computer Emergency Response Team), or CSIRT (Computer Security Incident Response Team); whatever the term used, companies desperately need a process and team to formally respond to computer security incidents. The simple equation is that to the degree the incident is quickly identified, handled and ameliorated; is to the extent that the damage is contained and limited.

At just over 200 pages, the books 13 chapters provides an excellent foundation on which to start a CIRT. The book is divided into two parts. Chapters 1-6 form part 1, Computer Security Incidents, with part 2 being on Product Security.

Chapter 1 provides a basic introduction to the topic on why an organization should care about computer security incident response. This brief chapter touches upon the various business impacts, in addition to the legal and other reasons necessary for establishing a CIRT.

Chapter 2 lays down the 6 steps in which to establish an IRT, which are: defining the constituency, ensuring upper-management support, obtaining funding, hierarchy, team structure and policies and procedures. Each of these steps is crucial, and a mistake too many organizations make is to leave one or more out. Only later when an incident occurs, which often takes an inordinate amount of time to fix, do these companies realize that their IRT was incomplete and inadequate in the first place.

The chapter includes an interesting look at the various types of IRT teams that can be created; namely central, distributed or virtual. The book notes that if you don't have sufficiently strong support from senior organizational executives to form a real IRT (which should be a huge red flag right there), a virtual team is a good option. Virtual teams can be easier to set up as they are less formal with fewer bureaucratic hurdles. While there are benefits to a virtual IRT, companies that are truly serious about computer security will ensure that they have a formal and dedicated IRT in place.

In chapter 3, Operating an IRT, the author details the items needed to successfully operate an IRT. One of the soft skills the author discusses is effective interpersonal skills. The author writes that one situation that can arise when handling an active incident is that the person reporting the incident may say offensive things or become abusive to the IRT analyst. This behavior is generally the consequence of the attack, indicating its urgency. When dealing with such a person, it is imperative that IRT analyst not get caught up in the user's behavior. Rather they must focus on determining the appropriate method to fix the problem.

While part 1 is around the computer security incident itself, part 2 deals with product security. Most organizations create their IRT around computer security incidents. In chapter 8, the author writes about the need to create a product security team (PST) to deal with security issues related to vendor products.

Every software and hardware product has security flaws, be it Cisco, Juniper, Check Point and others. By understanding this and having a PST to deal with vendor security issues, a company will be adequately protected. In truth, only large companies will have the budget to support an independent PST in addition to an IRT.

In many ways, the PST is simply a specialized section of the IRT, with specific expertise around a specific product set. Many firms already have some sort of PST in place to deal with Patch Tuesday, which is the second Tuesday of each month when Microsoft releases security patches.

Overall, Computer Incident Response and Product Security provides a good overview of the topic. At 215 pages, the book should be seen as an introduction to the topic, not a comprehensive reference. The reason is that a topic such as security incident response requires much broader coverage given the extent of the requirements encompassed. In some ways though, its conciseness is its advantage, as a 750 page tome, while adequate for the subject, may overwhelm many, if not most readers. Also, the author has the ability to adequately discuss topics in a manner while brief, does cover the topic issues.

At $49-, the book is moderately priced, given the value of the content. For those on a limited budget, the Handbook for Computer Security Incident Response Teams from CERT provides a good overview of the topic. While the handbook was last revised in 2003, much of the core concepts around incident response are immutable.

As this title is from Cisco Press and the author an employee of the Cisco Product Security Incident Response Team (PSIRT), the book has a definite Cisco slant. While Cisco products are often referenced, this though is not a book from Cisco marketing. More importantly, as part of the Cisco PSIRT, the author has first-hand knowledge of one of the world's premier IRT.

For those serious about computer security and incident response, Computer Incident Response and Product Security should be one of the required books for every member of the team.

Ben Rothke is an information security professional and the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Computer Incident Response and Product Security from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

PatPending writes "Aerial drones are now used by the Texas Department of Public Safety; the Mesa County Sheriff's Office, Colorado; the Miami-Dade County, Florida, Police Department; and the Department of Homeland Security. But what about privacy concerns? 'Drones raise the prospect of much more pervasive surveillance,' said Jay Stanley, a senior policy analyst with the American Civil Liberties Union's Speech, Privacy and Technology Project. 'We are not against them, absolutely. They can be a valuable tool in certain kinds of operations. But what we don't want to see is their pervasive use to watch over the American people.'"

RedK writes "In a follow up to yesterday's news about Google apparently relicensing confidential Oracle code found in Java under the ASL, it seems that the blogger who initially reported the issue was plain wrong, as the files he indicated were in breach of Oracle's copyright do not actually ship with Android. Google has also deleted many of these files, which were mostly used as unit tests."

tsamsoniw writes "The rumors that a Playboy app would appear in the Apple App Store were greatly exaggerated. Playboy plans to offer an online service through which subscribers can access past and current issues of the nudie mag — and per Playboy, it will be accessible via Safari and support iPad features (whatever that means). But if Playboy does come out with a native app for iPad, all the nudity will be censored. That should be just fine for the legions of people who indeed read the magazine for the articles. This really shouldn't be a surprise, though: If Apple insists on 'protecting' users of its high-priced gear from pixelated naughty bits in a graphic-novel version of classic literature, it certainly won't let users access the full monty. It's a shame, though: If Apple's customers want access to that sort of content, Apple should allow them to get at it via a native app instead of suffering a potentially buggier, less secure browser-based experience."

Michael J. Ross writes "Of all the better-known content management systems, Drupal is oftentimes criticized for having the steepest learning curve. Yet that would only be a valid charge as a result of Drupal's great power and flexibility — particularly in the hands of a knowledgeable Drupal developer. But how can the interested programmer begin gaining those skills, as quickly as possible? One approach is to read and work through the examples of an introductory book, such as Foundation Drupal 7, written by Robert J. Townsend (except for a chapter contributed by Stephanie Pakrul)." Read on for the rest of Michael's review. Foundation Drupal 7 author Robert J. Townsend pages 328 pages publisher friends of ED rating 6/10 reviewer Michael J. Ross ISBN 978-1430228080 summary A guide to getting started building websites using Drupal. The book was published on 15 December 2010, under the ISBN 978-1430228080, by "friends of ED", which is both a division of Apress and arguably a baffling name for a publisher's imprint. The book's material spans 328 pages, grouped into 12 chapters and four appendices. The publisher's page offers a description of the book, and a link for purchasing the e-book version. Visitors can also read a few dozen of the least interesting pages in the book, using a lame modal interface "powered" by Google Preview's book viewer system. As of this writing, the author's own site for the book appears to have no useful content. In fact, even a few weeks after the publication of the book, the site had no word as to how to use the site or even obtain an account, and there is nothing pertaining to that in the book. Now, it appears to be the beginnings of a demo site.

The book's chapters can be loosely grouped into four parts: The first three chapters provide an overview of Drupal, and explain how to set up a local Web server, install Drupal 7 on it, and configure the new site. The material composes an adequate introduction, but there are some false statements readers should watch out for, such as: newly created blocks are added to nodes (page 15); "Drupal will not run on most inexpensive hosting plans" (pages 19 and 20); "server settings and update notifications must be configured" (page 35; actually, they are optional); "the default Garland theme" (pages 40 and 55; no longer true in Drupal 7); a block can be any shape (page 48; as long as it's a rectangle!). But the discussion on multisite setups — while likely intimidating for Drupal newbies — is well worth reading by anyone who has not yet tried running multiple sites from a single Drupal instance. However, the ."demo.d7" suffix (page 28) should have been explained. In the introduction, the author noted that the book is primarily intended for readers who have little or no experience with content management systems in general, and Drupal in particular. The early chapters hew to that approach, going so far as to briefly present the basics of databases — material that experienced programmers can safely skip.

Node fields, content types, taxonomies, users, roles, permissions, and modules (both core and contributed) are key components in building a site with Drupal — and they are explicated in Chapters 4 through 7. The narrative is quite descriptive, and readers new to Drupal may find some of it tough going; but it will be worth their while to read through all of the material, at least once, while exercising their newfound knowledge on a test installation of Drupal 7. Most of the discussion is clear and straightforward, but a few spots will likely perplex readers, e.g., "all search fields are hidden by default when either search view node is enabled" (page 85; what search view nodes?). Also, on pages 69 and 87, the author advises readers to limit a system name to seven characters, but each example given exceeds that number. Such inconsistencies can prompt readers to begin questioning the author's advice and attention to detail. As a resource perhaps unique to this Drupal book, the sixth chapter explores the purpose and basic usage of most of the core modules not enabled by the standard installation. Drupal newcomers invariably wonder what contrib modules they should first be trying out and learning, and the author presents several of them in the seventh chapter, which includes a helpful comparison of using the Webform module versus nodes for collecting data from users.

Nonprogrammer website creators — who must rely entirely upon the GUI of a content management system to build a site — are strongly influenced by the visual appeal of a CMS's built-in themes, and not necessarily its flexibility or other differentiating factors. (One can only speculate as to how many such people have chosen Joomla over Drupal based upon the former's more attractive default themes.) Thus, theming can be especially significant to non-technical Drupal site creators, and is covered in the next two chapters, the first of which was authored by Stephanie Pakrul. To illustrate the ideas discussed, she uses her own Vibe theme, which is a sub-theme of Fusion. Unfortunately, as of this writing, there are no releases of Vibe, so it is not clear how readers are expected to download it as instructed (on page 174). Consequently, readers won't be able to see on their own Drupal installations what she shows in the screenshots. This is just one more example of how this book appears to be unfinished. Some readers may become frustrated with the way that she often gives instructions but fails to identify the page on which to perform them. Also, the Skinr block settings shown in the book look nothing like what I am seeing using the latest versions of Fusion and Skinr, but that may be due to Vibe missing. Skinr's project page currently warns that it is not stable or functional for Drupal 7; this makes it a poor choice for a book aimed at beginners, who can be easily derailed by such problems. Several details are incorrect, e.g., the Firebug technique shown in Figure 8-14 does not use double-clicking, as stated, but simply mouse hover. Chapter 9 provides advice on using Photoshop and Illustrator CS5 for working with layouts, text, colors, and images in designing Drupal themes.

The last three chapters discuss topics related to deploying a site. Chapter 10, "Going Live," presents the details of the author's strategy for using separate sites for development, staging, and production. This involves executing Linux commands on the command-line, and at one point even deleting the public_html directory and creating a symbolic link. It is easy to imagine readers being hesitant about doing so — especially in a client's account — and for such people, using only an FTP application might be more palatable, even if it takes extra time. The next chapter offers some valuable best practices for maintaining a production site, including techniques to be automatically notified when installed modules become out of date. The last chapter, "Translating Business Requirements to Drupal Functionality," may at first glance seem inappropriately placed at the end of the book, because shouldn't the developer analyze the client's business requirements before beginning any work on their future website? But this chapter does belong at the end, because most of its topics will make a lot more sense to the reader after she has learned the basics of a Drupal site. The only confusing aspect of this material is the author's recommendation to add 25 percent to both the amount of estimated time to complete a project and also one's hourly rate, with no explanation for the rate increase. Nonetheless, the chapter presents some worthy advice on how to be a more effective Drupal site builder.

The book's four appendices briefly cover search engine optimization for Drupal sites; Drush (a command-line shell for Drupal); a survey of more than 50 useful contrib modules; and usage of the Views module to address some common query-building needs. Note that the Views carousel module — which is one of two image slideshow modules listed — was deprecated awhile ago.

All of the chapters except the first are capped off with summaries, which add no value to the book and consist mostly of unneeded reminders that begin with "I talked about," "I then talked about," etc. One of the summaries (page 214) states that a particular website was used as an example, but it wasn't even mentioned in the chapter itself. A strength of the book is that there are plenty of screenshots throughout, and most of them are helpful. But their captions typically repeat information stated immediately before the figure, and thus add unnecessary text.

Readers may become disappointed with an overall sense that the book was not crafted and edited properly, perhaps in a desire to rush it to market in order to cash in on the growing interest in Drupal and the release of Drupal 7. Any such urgency could account for the poor decisions in the production of the book. Some of the material appears unfinished, or at least unpolished. For instance, Chapter 1 ends quite abruptly, with no chapter summary, unlike all the others. The first part of a sentence on page 184 is completely missing.

It is not always clear as to which problems are caused by the authors, and which by the publisher. As a minor example, many of the module names are incorrectly presented in all lowercase (especially in Chapters 6, 7, and 11), in some cases rather pointedly (e.g., "cck") and in others a bit confusingly when in mid-sentence (e.g., "views"). Was that the author being sloppy, or an overzealous copyeditor who did not realize that title case is appropriate for the proper names of the modules?

Some of the problems could only originate from the author. There are countless instances of weird and perplexing instructions, such as "log on and log in" (page 266). On one page alone (127), readers will encounter "Make sure the configure it after saving if applicable" and "Configuration, Languages should be screen text style." There are numerous errata: "postgresql" (page xvii), "blog" (page 15; should read "block"), "minimum the PHP requirements" (21), "Drupal 7-1 to 7-2" (35), "ä" (60), "of [a] single" (68), "of [the] fields" (74), "per-configured" (76), "a decimal [point]" (77), "be round[ed]" (77), "by [a] user" (83), "how which fields" (85), "requires updated or not" (131), "delimeter" (163), "ie" (175), "This [is] where" (196), "comments are will" (198), "aka" (226, 270, and 278), "is usually means" (240), "site to bake" (243), and "described in earlier in the chapter" (248).

The pace of explanation varies tremendously, from one section to the next. For instance, several paragraphs might discuss fundamental Drupal concepts slowly, with full explanations, and then only a page later the reader is entangled in fairly advanced topics, with little or no preparation. Many readers will find appealing the informal conversational style — although in a few instances the wording is unintentionally humorous, such as the phrase "most exciting" transformed into "most excitedly" (page xxi).

Other problems can only be laid at the feet of the publisher, such as incorrectly bolded words, even for individual characters in words (e.g., pages 87, 110, 233). The publisher chose to use the smallest font of any technical book I've ever seen, and consequently people with vision limitations may have difficulty reading the text. Also, many of the screenshots are rather pale; in most cases this is not a problem, but some of the images look fuzzy. In contrast (no pun), the image in Figure 9-4 is an unreadable black rectangle containing a stack of smaller gray rectangles, and the background is effectively indiscernible. Readers will wonder how the production team let that obvious problem slip through the cracks. The image used for Figure 4-15 evidently had its right side chopped off. Several of the pages contain small gray and brown lines, dots, and splotches; but those blemishes may be limited to my copy of the book.

Writing and releasing a book prior to the final release of the software, is always fraught with danger. Some of the Drupal-generated warning and error messages mentioned in the book differ from what would be seen using the final 7.0 version, which was not available to the author during the writing of the book. This is likely also the reason why the list of core modules (Table 1-1) is missing the Options module and includes the now-absent Profile module. But that would not explain why the critical System module is missing from the list. Also, the "Secondary menu" mentioned on page 56, is now gone, although secondary links are still part of Drupal 7. In terms of theming, the default site theme is Seven, and not the venerable Garland; also, the Minnelli theme (page 63) — Garland's fixed-width counterpart — was excluded from the final 7.0 release.

In essence, this book was not well executed, and yet it has a lot of promise. A second edition — perhaps for Drupal 8 — could rectify most if not all of these problems. The author's passion for Drupal is evident and inspiring: He shares hard-won and sincere advice for avoiding disaster in working with clients and working on their websites. Also, he notes in the introduction that 10 percent of all profits from the book will be donated to the Drupal Association. Although it is in much need of polishing — and in some places a full overhaul — Foundation Drupal 7 provides information and guidance that would be helpful to anyone who wants to learn how to use Drupal for creating websites.

Michael J. Ross is a freelance Web developer and writer.

You can purchase Foundation Drupal 7 from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Michael J. Ross writes "Of all the better-known content management systems, Drupal is oftentimes criticized for having the steepest learning curve. Yet that would only be a valid charge as a result of Drupal's great power and flexibility — particularly in the hands of a knowledgeable Drupal developer. But how can the interested programmer begin gaining those skills, as quickly as possible? One approach is to read and work through the examples of an introductory book, such as Foundation Drupal 7, written by Robert J. Townsend (except for a chapter contributed by Stephanie Pakrul)." Read on for the rest of Michael's review. Foundation Drupal 7 author Robert J. Townsend pages 328 pages publisher friends of ED rating 6/10 reviewer Michael J. Ross ISBN 978-1430228080 summary A guide to getting started building websites using Drupal. The book was published on 15 December 2010, under the ISBN 978-1430228080, by "friends of ED", which is both a division of Apress and arguably a baffling name for a publisher's imprint. The book's material spans 328 pages, grouped into 12 chapters and four appendices. The publisher's page offers a description of the book, and a link for purchasing the e-book version. Visitors can also read a few dozen of the least interesting pages in the book, using a lame modal interface "powered" by Google Preview's book viewer system. As of this writing, the author's own site for the book appears to have no useful content. In fact, even a few weeks after the publication of the book, the site had no word as to how to use the site or even obtain an account, and there is nothing pertaining to that in the book. Now, it appears to be the beginnings of a demo site.

The book's chapters can be loosely grouped into four parts: The first three chapters provide an overview of Drupal, and explain how to set up a local Web server, install Drupal 7 on it, and configure the new site. The material composes an adequate introduction, but there are some false statements readers should watch out for, such as: newly created blocks are added to nodes (page 15); "Drupal will not run on most inexpensive hosting plans" (pages 19 and 20); "server settings and update notifications must be configured" (page 35; actually, they are optional); "the default Garland theme" (pages 40 and 55; no longer true in Drupal 7); a block can be any shape (page 48; as long as it's a rectangle!). But the discussion on multisite setups — while likely intimidating for Drupal newbies — is well worth reading by anyone who has not yet tried running multiple sites from a single Drupal instance. However, the ."demo.d7" suffix (page 28) should have been explained. In the introduction, the author noted that the book is primarily intended for readers who have little or no experience with content management systems in general, and Drupal in particular. The early chapters hew to that approach, going so far as to briefly present the basics of databases — material that experienced programmers can safely skip.

Node fields, content types, taxonomies, users, roles, permissions, and modules (both core and contributed) are key components in building a site with Drupal — and they are explicated in Chapters 4 through 7. The narrative is quite descriptive, and readers new to Drupal may find some of it tough going; but it will be worth their while to read through all of the material, at least once, while exercising their newfound knowledge on a test installation of Drupal 7. Most of the discussion is clear and straightforward, but a few spots will likely perplex readers, e.g., "all search fields are hidden by default when either search view node is enabled" (page 85; what search view nodes?). Also, on pages 69 and 87, the author advises readers to limit a system name to seven characters, but each example given exceeds that number. Such inconsistencies can prompt readers to begin questioning the author's advice and attention to detail. As a resource perhaps unique to this Drupal book, the sixth chapter explores the purpose and basic usage of most of the core modules not enabled by the standard installation. Drupal newcomers invariably wonder what contrib modules they should first be trying out and learning, and the author presents several of them in the seventh chapter, which includes a helpful comparison of using the Webform module versus nodes for collecting data from users.

Nonprogrammer website creators — who must rely entirely upon the GUI of a content management system to build a site — are strongly influenced by the visual appeal of a CMS's built-in themes, and not necessarily its flexibility or other differentiating factors. (One can only speculate as to how many such people have chosen Joomla over Drupal based upon the former's more attractive default themes.) Thus, theming can be especially significant to non-technical Drupal site creators, and is covered in the next two chapters, the first of which was authored by Stephanie Pakrul. To illustrate the ideas discussed, she uses her own Vibe theme, which is a sub-theme of Fusion. Unfortunately, as of this writing, there are no releases of Vibe, so it is not clear how readers are expected to download it as instructed (on page 174). Consequently, readers won't be able to see on their own Drupal installations what she shows in the screenshots. This is just one more example of how this book appears to be unfinished. Some readers may become frustrated with the way that she often gives instructions but fails to identify the page on which to perform them. Also, the Skinr block settings shown in the book look nothing like what I am seeing using the latest versions of Fusion and Skinr, but that may be due to Vibe missing. Skinr's project page currently warns that it is not stable or functional for Drupal 7; this makes it a poor choice for a book aimed at beginners, who can be easily derailed by such problems. Several details are incorrect, e.g., the Firebug technique shown in Figure 8-14 does not use double-clicking, as stated, but simply mouse hover. Chapter 9 provides advice on using Photoshop and Illustrator CS5 for working with layouts, text, colors, and images in designing Drupal themes.

The last three chapters discuss topics related to deploying a site. Chapter 10, "Going Live," presents the details of the author's strategy for using separate sites for development, staging, and production. This involves executing Linux commands on the command-line, and at one point even deleting the public_html directory and creating a symbolic link. It is easy to imagine readers being hesitant about doing so — especially in a client's account — and for such people, using only an FTP application might be more palatable, even if it takes extra time. The next chapter offers some valuable best practices for maintaining a production site, including techniques to be automatically notified when installed modules become out of date. The last chapter, "Translating Business Requirements to Drupal Functionality," may at first glance seem inappropriately placed at the end of the book, because shouldn't the developer analyze the client's business requirements before beginning any work on their future website? But this chapter does belong at the end, because most of its topics will make a lot more sense to the reader after she has learned the basics of a Drupal site. The only confusing aspect of this material is the author's recommendation to add 25 percent to both the amount of estimated time to complete a project and also one's hourly rate, with no explanation for the rate increase. Nonetheless, the chapter presents some worthy advice on how to be a more effective Drupal site builder.

The book's four appendices briefly cover search engine optimization for Drupal sites; Drush (a command-line shell for Drupal); a survey of more than 50 useful contrib modules; and usage of the Views module to address some common query-building needs. Note that the Views carousel module — which is one of two image slideshow modules listed — was deprecated awhile ago.

All of the chapters except the first are capped off with summaries, which add no value to the book and consist mostly of unneeded reminders that begin with "I talked about," "I then talked about," etc. One of the summaries (page 214) states that a particular website was used as an example, but it wasn't even mentioned in the chapter itself. A strength of the book is that there are plenty of screenshots throughout, and most of them are helpful. But their captions typically repeat information stated immediately before the figure, and thus add unnecessary text.

Readers may become disappointed with an overall sense that the book was not crafted and edited properly, perhaps in a desire to rush it to market in order to cash in on the growing interest in Drupal and the release of Drupal 7. Any such urgency could account for the poor decisions in the production of the book. Some of the material appears unfinished, or at least unpolished. For instance, Chapter 1 ends quite abruptly, with no chapter summary, unlike all the others. The first part of a sentence on page 184 is completely missing.

It is not always clear as to which problems are caused by the authors, and which by the publisher. As a minor example, many of the module names are incorrectly presented in all lowercase (especially in Chapters 6, 7, and 11), in some cases rather pointedly (e.g., "cck") and in others a bit confusingly when in mid-sentence (e.g., "views"). Was that the author being sloppy, or an overzealous copyeditor who did not realize that title case is appropriate for the proper names of the modules?

Some of the problems could only originate from the author. There are countless instances of weird and perplexing instructions, such as "log on and log in" (page 266). On one page alone (127), readers will encounter "Make sure the configure it after saving if applicable" and "Configuration, Languages should be screen text style." There are numerous errata: "postgresql" (page xvii), "blog" (page 15; should read "block"), "minimum the PHP requirements" (21), "Drupal 7-1 to 7-2" (35), "ä" (60), "of [a] single" (68), "of [the] fields" (74), "per-configured" (76), "a decimal [point]" (77), "be round[ed]" (77), "by [a] user" (83), "how which fields" (85), "requires updated or not" (131), "delimeter" (163), "ie" (175), "This [is] where" (196), "comments are will" (198), "aka" (226, 270, and 278), "is usually means" (240), "site to bake" (243), and "described in earlier in the chapter" (248).

The pace of explanation varies tremendously, from one section to the next. For instance, several paragraphs might discuss fundamental Drupal concepts slowly, with full explanations, and then only a page later the reader is entangled in fairly advanced topics, with little or no preparation. Many readers will find appealing the informal conversational style — although in a few instances the wording is unintentionally humorous, such as the phrase "most exciting" transformed into "most excitedly" (page xxi).

Other problems can only be laid at the feet of the publisher, such as incorrectly bolded words, even for individual characters in words (e.g., pages 87, 110, 233). The publisher chose to use the smallest font of any technical book I've ever seen, and consequently people with vision limitations may have difficulty reading the text. Also, many of the screenshots are rather pale; in most cases this is not a problem, but some of the images look fuzzy. In contrast (no pun), the image in Figure 9-4 is an unreadable black rectangle containing a stack of smaller gray rectangles, and the background is effectively indiscernible. Readers will wonder how the production team let that obvious problem slip through the cracks. The image used for Figure 4-15 evidently had its right side chopped off. Several of the pages contain small gray and brown lines, dots, and splotches; but those blemishes may be limited to my copy of the book.

Writing and releasing a book prior to the final release of the software, is always fraught with danger. Some of the Drupal-generated warning and error messages mentioned in the book differ from what would be seen using the final 7.0 version, which was not available to the author during the writing of the book. This is likely also the reason why the list of core modules (Table 1-1) is missing the Options module and includes the now-absent Profile module. But that would not explain why the critical System module is missing from the list. Also, the "Secondary menu" mentioned on page 56, is now gone, although secondary links are still part of Drupal 7. In terms of theming, the default site theme is Seven, and not the venerable Garland; also, the Minnelli theme (page 63) — Garland's fixed-width counterpart — was excluded from the final 7.0 release.

In essence, this book was not well executed, and yet it has a lot of promise. A second edition — perhaps for Drupal 8 — could rectify most if not all of these problems. The author's passion for Drupal is evident and inspiring: He shares hard-won and sincere advice for avoiding disaster in working with clients and working on their websites. Also, he notes in the introduction that 10 percent of all profits from the book will be donated to the Drupal Association. Although it is in much need of polishing — and in some places a full overhaul — Foundation Drupal 7 provides information and guidance that would be helpful to anyone who wants to learn how to use Drupal for creating websites.

Michael J. Ross is a freelance Web developer and writer.

You can purchase Foundation Drupal 7 from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

stupid_is writes with news that Duke Nukem Forever has now gotten a firm US release date: May 3rd. It will release worldwide three days later. The game was resurrected last fall by Gearbox Software and 2K Games after 3D Realms' 12-year attempt at development came to an end in 2009 when the company closed its doors.

stupid_is writes with news that Duke Nukem Forever has now gotten a firm US release date: May 3rd. It will release worldwide three days later. The game was resurrected last fall by Gearbox Software and 2K Games after 3D Realms' 12-year attempt at development came to an end in 2009 when the company closed its doors.

The Washington Post reports that Verizon has filed a lawsuit against the Federal Communications Commission over the net neutrality rules they adopted last month. Quoting: "Verizon argues that the FCC does not have the legal authority to mandate how Internet service providers treat content on their networks. A legal challenge was widely expected, and the FCC has said it thinks Congress enabled the agency to pursue its rules under several interpretations of telecommunications laws. The FCC's rules are supported by consumer groups and Web giants such as Google and Facebook. Verizon filed its case in the same federal court — the US Court of Appeals for the District of Columbia — that ruled last April that the FCC overstepped its authority in trying to sanction Comcast for blocking Web traffic. 'We are deeply concerned by the FCC's assertion of broad authority for sweeping new regulation of broadband networks and the Internet itself,' said Michael E. Glover, Verizon's senior vice president and deputy general counsel. 'We believe this assertion of authority goes well beyond any authority provided by Congress, and creates uncertainty for the communications industry, innovators, investors and consumers.'"

The Washington Post reports that Verizon has filed a lawsuit against the Federal Communications Commission over the net neutrality rules they adopted last month. Quoting: "Verizon argues that the FCC does not have the legal authority to mandate how Internet service providers treat content on their networks. A legal challenge was widely expected, and the FCC has said it thinks Congress enabled the agency to pursue its rules under several interpretations of telecommunications laws. The FCC's rules are supported by consumer groups and Web giants such as Google and Facebook. Verizon filed its case in the same federal court — the US Court of Appeals for the District of Columbia — that ruled last April that the FCC overstepped its authority in trying to sanction Comcast for blocking Web traffic. 'We are deeply concerned by the FCC's assertion of broad authority for sweeping new regulation of broadband networks and the Internet itself,' said Michael E. Glover, Verizon's senior vice president and deputy general counsel. 'We believe this assertion of authority goes well beyond any authority provided by Congress, and creates uncertainty for the communications industry, innovators, investors and consumers.'"

On Wednesday we discussed news of an impressive-looking mod for StarCraft II that transformed the game into a WoW lookalike, which quickly drew a copyright infringement warning from Activision Blizzard. The company has now released an official statement green-lighting the mod for continued development. "'It was never our intention to stop development on the mod or discourage the community from expressing their creativity through the StarCraft II editor,' Blizzard said in a statement. 'As always, we actively encourage development of custom maps and mods for StarCraft II, as we've done with our strategy games in the past.' Blizzard went on the say that it's looking forward to seeing development of the mod continue, and that it has invited Winzen to the company's campus to meet the game's development team."

An anonymous reader writes "It looks like the Australian Government is not taking criticism of its decision to mandate Microsoft's Office Open XML standard lying down. 'The policy is vendor-neutral which allows its principles and standards to be used across any platform,' they said this week. Yup ... except for the fact that almost no other office suite apart from Microsoft Office supports writing to the standard. And as for Firefox? Turns out 96 percent of Australian Government desktops use Internet Explorer. Looks like bureaucracy is winning here."

SEWilco writes "Despite our older headline, NanoSail-D was not 'Lost in space.' It was stuck in its canister. The solar sail nano-satellite finally ejected on Wednesday. The three-day countdown to sail deployment began then, so we'll have to see what happens next." And clm1970 adds "In another conventional use for an arguably unconventional hobby given the technology of 2011, NASA is requesting the help of Amateur Radio or 'ham operators' to help listen to a beacon signal of the nano-satellite. Many say the hobby is dying, but for every 'death knell,' it seems another application brings it back to life to prove its usefulness."

An anonymous reader writes "Last summer, NASA announced that the Kepler space telescope had identified more than 700 exoplanet 'candidates' from the first few months of observations in 2009. Only 312 of the candidates were initially made public, while 400 others (click the green search button) were sequestered until February 2011. The team is soon expected to announce that a large number of these candidates have been confirmed as exoplanets. A non-profit organization in Boulder, Colorado supports scientific research on the Kepler data through $10 adopt-a-star donations. The price is $100 for confirmed exoplanets, so hurry while these 700+ stars are still 'candidates'!"

eldavojohn writes "If you've been following the team who created World of StarCraft (an amazing mod of StarCraft II to be more like World of Warcraft), their YouTube video of what they've done so far has already resulted in a cease and desist from Activision/Blizzard. Evidently when you are given tools to make custom mods to games you should be careful about making something too good. The author of the mod is hopeful that it's just a trademark problem with the name of his mod, but few reasons for the C&D were given." In other StarCraft news, reader glwtta recommends an article about how a Berkeley team won the world's first StarCraft AI competition with code that can beat even pro-level human players.

jddp writes "MacDonald is a programmer's programmer, and Pro Silverlight 4 in VB is a model of what a programmer's guide should be. He explains a mass of technical information in considerable detail without losing the big-picture. His clear and concise exposition of concepts and functionality is never confusing or needlessly repetitive. The book's organization is logical, yet the chapters can be read in isolation, as the need or interest arises." Keep reading for the rest of jddp's review. Pro Silverlight 4 in VB author Matthew MacDonald pages 896 publisher Apress rating 9/10 reviewer jddp ISBN 1430235489 summary An invaluable reference for professional developers wanting to discover the new features of Silverlight One thing this book doesn't provide is an overview of the subject for a novice trying to get the big-picture. After the briefest of introductions (10 pages), the author leaps right into building applications. Nor does it provide every technical detail you will need to complete your application. (That's why we have the web). However, if you want a book that can take you from having a rough map of the territory to being a self-sufficient Silverlight developer, I highly recommend this one.

Starting from the fundamentals of Silverlight such as XAML, Layout and Elements, McDonald rarely puts a step wrong as he winds through the technical details, progressing to specific functional areas such as such as Animation, Data Binding and Web services. Each chapter provides a brief overview of the functionality addressed before stepping through the programming details. His code examples are concise, but also convey the significance and use of the features very clearly. The examples do not sprawl across pages and pages, as in weaker tutorials, but they do build upon one another when necessary. Working code implementing the examples from the text is available at MacDonald's personal site for anyone to download — but apparently only in C# (as far as I could see. The VB version may be coming later, just as the VB book lagged the C# version). Due to the intelligent choice, structuring and clear implementation of his examples, I have found them a useful jumping-off point for "real-life" applications on several occasions. The author has gone beyond the scope of the book in at least one case, implemented an "advanced" capability (support for large file up/downloads via a Web Service) that I was specifically interested in.

As mentioned, the book does not contain an extensive technology overview and this is reflected by the absence of many of the buzzwords associated with Silverlight from the index. You will find no mention of RIA services. MVVM is only touched upon in the context of the new SL 4 support for the Command pattern. (Even so, his brief explanation is a great example of MacDonald's lucid and economical expository style. You could trawl the web for a long time without finding such a straightforward explanation.) However, while MacDonald does not attempt to convey any over-arching architectural vision, he is perfectly capable of clarifying some abstract design concepts. In Chapter 4 of the book he is already tackling the intimidating-sounding topics of Dependency Properties, Attached Properties and Routed Events. By the time you've read a few pages you're wondering what all the fuss was about. After less than six pages, MacDonald is working through a meaningful application of attached properties (a custom layout panel). Most of the chapter is devoted a detailed explanation and illustration of Mouse and Keyboard event handling, and to the new Commanding support in SL 4.

A final caveat: This is not a book for someone wanting to catch up on what's new in Silverlight 4. The information is there, but it is dispersed among the relevant sections of the old book, and there is no helpful index. Contrary to the impression given by the back-cover, the very occasional "What's New" boxes don't help much in homing in on new features. In fact, the organization of the material and most of the content is unchanged from the SL 3 edition, so I wouldn't buy this if you already have that book.

While reading this book, I sometimes wished for a wider view: discussions of the merits of different architectures; comparisons to design patterns used in other technologies, and so forth. This book will not be much help in defining the architecture for your next mega-app. This is a book to seize on when you need to get a handle on programming specific Silverlight features fast. You won't learn about every possible shortcut or dead-end on the trail, but you will never have to wonder where the heck you are.

While this book it isn't all things to all developers, it is hard to overstate its consistent intelligence and clarity, or its sheer usefulness (to programmers). Programmers just aren't supposed to be so articulate – are they?

You can purchase Pro Silverlight 4 in VB from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

jddp writes "MacDonald is a programmer's programmer, and Pro Silverlight 4 in VB is a model of what a programmer's guide should be. He explains a mass of technical information in considerable detail without losing the big-picture. His clear and concise exposition of concepts and functionality is never confusing or needlessly repetitive. The book's organization is logical, yet the chapters can be read in isolation, as the need or interest arises." Keep reading for the rest of jddp's review. Pro Silverlight 4 in VB author Matthew MacDonald pages 896 publisher Apress rating 9/10 reviewer jddp ISBN 1430235489 summary An invaluable reference for professional developers wanting to discover the new features of Silverlight One thing this book doesn't provide is an overview of the subject for a novice trying to get the big-picture. After the briefest of introductions (10 pages), the author leaps right into building applications. Nor does it provide every technical detail you will need to complete your application. (That's why we have the web). However, if you want a book that can take you from having a rough map of the territory to being a self-sufficient Silverlight developer, I highly recommend this one.

Starting from the fundamentals of Silverlight such as XAML, Layout and Elements, McDonald rarely puts a step wrong as he winds through the technical details, progressing to specific functional areas such as such as Animation, Data Binding and Web services. Each chapter provides a brief overview of the functionality addressed before stepping through the programming details. His code examples are concise, but also convey the significance and use of the features very clearly. The examples do not sprawl across pages and pages, as in weaker tutorials, but they do build upon one another when necessary. Working code implementing the examples from the text is available at MacDonald's personal site for anyone to download — but apparently only in C# (as far as I could see. The VB version may be coming later, just as the VB book lagged the C# version). Due to the intelligent choice, structuring and clear implementation of his examples, I have found them a useful jumping-off point for "real-life" applications on several occasions. The author has gone beyond the scope of the book in at least one case, implemented an "advanced" capability (support for large file up/downloads via a Web Service) that I was specifically interested in.

As mentioned, the book does not contain an extensive technology overview and this is reflected by the absence of many of the buzzwords associated with Silverlight from the index. You will find no mention of RIA services. MVVM is only touched upon in the context of the new SL 4 support for the Command pattern. (Even so, his brief explanation is a great example of MacDonald's lucid and economical expository style. You could trawl the web for a long time without finding such a straightforward explanation.) However, while MacDonald does not attempt to convey any over-arching architectural vision, he is perfectly capable of clarifying some abstract design concepts. In Chapter 4 of the book he is already tackling the intimidating-sounding topics of Dependency Properties, Attached Properties and Routed Events. By the time you've read a few pages you're wondering what all the fuss was about. After less than six pages, MacDonald is working through a meaningful application of attached properties (a custom layout panel). Most of the chapter is devoted a detailed explanation and illustration of Mouse and Keyboard event handling, and to the new Commanding support in SL 4.

A final caveat: This is not a book for someone wanting to catch up on what's new in Silverlight 4. The information is there, but it is dispersed among the relevant sections of the old book, and there is no helpful index. Contrary to the impression given by the back-cover, the very occasional "What's New" boxes don't help much in homing in on new features. In fact, the organization of the material and most of the content is unchanged from the SL 3 edition, so I wouldn't buy this if you already have that book.

While reading this book, I sometimes wished for a wider view: discussions of the merits of different architectures; comparisons to design patterns used in other technologies, and so forth. This book will not be much help in defining the architecture for your next mega-app. This is a book to seize on when you need to get a handle on programming specific Silverlight features fast. You won't learn about every possible shortcut or dead-end on the trail, but you will never have to wonder where the heck you are.

While this book it isn't all things to all developers, it is hard to overstate its consistent intelligence and clarity, or its sheer usefulness (to programmers). Programmers just aren't supposed to be so articulate – are they?

You can purchase Pro Silverlight 4 in VB from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

jamie writes "Our reaction to the music that we love stimulates the flow of dopamine into certain sections of the brain, concludes a new study out of McGill University. The findings 'help to explain why music is of such high value across all human societies,' the scientists note."

TechieAlizay points out a post at Geekword.net about a man who hacked Microsoft's Kinect to play Max Payne. "This hack was possible due to FAAST (a toolkit for Kinect), OpenNi/Nite and GlovePIE. Here's how the hacker describes the different control gestures: 'As you can see, the leaning left and right stuff is all there – and moving your body forward and back moves you back and forward. The reload and interact gestures are becoming pretty standard for me now, and pain killers are popped with an upward motion of the left hand. What makes this special though is the leg movements that activate bullet time. The result is bullet time diving for real! When this game hit just after the Matrix film came out, it caused a big stir – with Kinect augmentation it gets even better. The one thing that needs fixing is weapon select; this will be handled by the +/- buttons on the mote in future, I think.'" Another video shows Kinect controlling Left 4 Dead 2. In addition to future PC support, Microsoft is reportedly working on an official SDK. Yet another recent hack of note allows a human to control a humanoid robot with an impressive level of accuracy. Just be careful if you play the Kinect boxing game; somebody might call the police.

jamie writes "Horace Dediu crunches some numbers and comes to a startling conclusion: 'If you look at the red line above and its slope, it would indicate that, given time, the App store will overtake the entire physical media gaming industry. The time when that happens will depend a lot on the growth or decline of the physical game media business, but another four years seems a safe bet.' This follows on the heels of some earlier analysis of apps per iOS device and what that steady upward growth means."

eldavojohn writes "The last time we discussed the Las Vegas Review-Journal and their litigating attorneys at Righthaven LLC, they were suing all the websites that had violated their news copyrights. Well, they've now added seven individual message board posters that they've managed to identify, bringing the number of DMCA-related lawsuits they have launched since March to 203. In one case, LVRJ is upset that a Google Groups user named Jim_Higgins posted a column that cited the columnist but failed to cite the original LVRJ article. But Google Groups is protected from these suits, as the article explains: 'Both the madjacksports and Google sites are somewhat protected from copyright lawsuits because they have posted "DMCA" notices as required by the Digital Millennium Copyright Act. These notices, which must be registered with the US Copyright Office, inform copyright holders who to contact if they would like infringing material removed.' The first decision of this cluster of lawsuits was against Righthaven, yet the onslaught continues. Righthaven has publicly dismissed fair use as well."

eldavojohn writes "The last time we discussed the Las Vegas Review-Journal and their litigating attorneys at Righthaven LLC, they were suing all the websites that had violated their news copyrights. Well, they've now added seven individual message board posters that they've managed to identify, bringing the number of DMCA-related lawsuits they have launched since March to 203. In one case, LVRJ is upset that a Google Groups user named Jim_Higgins posted a column that cited the columnist but failed to cite the original LVRJ article. But Google Groups is protected from these suits, as the article explains: 'Both the madjacksports and Google sites are somewhat protected from copyright lawsuits because they have posted "DMCA" notices as required by the Digital Millennium Copyright Act. These notices, which must be registered with the US Copyright Office, inform copyright holders who to contact if they would like infringing material removed.' The first decision of this cluster of lawsuits was against Righthaven, yet the onslaught continues. Righthaven has publicly dismissed fair use as well."

Charbax writes "Not only is power consumption halved to less than two Watts and price of the motherboard reduced, the performance of the next generation OLPC Laptop is actually better for running full Fedora Linux compared to x86. Here's a video interviewing OLPC's CTO, Edward J. McNierney, where he explains how and why OLPC's world class engineers are making this change of CPU architecture. If OLPC XO-1 threatened Intel enough to start the netbook market and has reached two million poor kids in third-world countries thus far, XO-1.75 may help start the ARM-powered Linux laptop market. Do you think Fedora/Sugar will do, or should OLPC attract Chrome OS and Android solutions for education to get faster help from the big boys of Silicon Valley in bringing Linux software successfully to the next billion PC/laptop users?"

An anonymous reader writes "With all the talk about WebM and H.264, how the move might be a step backwards for openness, and Google's intention to add 'plugins' for IE9 and Safari to support WebM, this article attempts to clear misconceptions about the VP8 and H.264 codecs and how browsers render video. Firefox, Opera and Google rely on their own media frameworks to decode video, whereas IE9 and Safari will hand over video processing to the operating system (Windows Media Player or QuickTime), the need for the web to establish a baseline codec for encoding videos, and how the Flash player is proprietary, but implementation and usage remain royalty free."

An anonymous reader writes "With all the talk about WebM and H.264, how the move might be a step backwards for openness, and Google's intention to add 'plugins' for IE9 and Safari to support WebM, this article attempts to clear misconceptions about the VP8 and H.264 codecs and how browsers render video. Firefox, Opera and Google rely on their own media frameworks to decode video, whereas IE9 and Safari will hand over video processing to the operating system (Windows Media Player or QuickTime), the need for the web to establish a baseline codec for encoding videos, and how the Flash player is proprietary, but implementation and usage remain royalty free."

An anonymous reader writes "With all the talk about WebM and H.264, how the move might be a step backwards for openness, and Google's intention to add 'plugins' for IE9 and Safari to support WebM, this article attempts to clear misconceptions about the VP8 and H.264 codecs and how browsers render video. Firefox, Opera and Google rely on their own media frameworks to decode video, whereas IE9 and Safari will hand over video processing to the operating system (Windows Media Player or QuickTime), the need for the web to establish a baseline codec for encoding videos, and how the Flash player is proprietary, but implementation and usage remain royalty free."

eldavojohn writes "A new study published today in Pediatrics Journal conducted in Singapore on three thousand children in grades third, fourth, seventh and eighth claims that one in ten are video game addicts and almost all of those suffer mental health problems. This comes conveniently after the suspect in the Tucson shooting has widely been reported as an online gamer. Among the accusations from the study are that playing video games leads to lower school performance and fewer social skills while exacerbating existing depression, anxiety and social phobias. Gamasutra reports that the Entertainment Software Alliance is already criticizing this study, saying, 'Its definition of "pathological gaming" is neither scientifically nor medically accepted and the type of measure used has been criticized by other scholars. Other outcomes are also measured using dubious instruments when well-validated tools are readily available. In addition, because the effect sizes of the outcomes are mainly trivial, it leaves open the possibility the author is simply interpreting things as negatively as possible.' It seems that the doctors are still disagreeing on whether or not gaming causes problems."

eldavojohn writes "A new study published today in Pediatrics Journal conducted in Singapore on three thousand children in grades third, fourth, seventh and eighth claims that one in ten are video game addicts and almost all of those suffer mental health problems. This comes conveniently after the suspect in the Tucson shooting has widely been reported as an online gamer. Among the accusations from the study are that playing video games leads to lower school performance and fewer social skills while exacerbating existing depression, anxiety and social phobias. Gamasutra reports that the Entertainment Software Alliance is already criticizing this study, saying, 'Its definition of "pathological gaming" is neither scientifically nor medically accepted and the type of measure used has been criticized by other scholars. Other outcomes are also measured using dubious instruments when well-validated tools are readily available. In addition, because the effect sizes of the outcomes are mainly trivial, it leaves open the possibility the author is simply interpreting things as negatively as possible.' It seems that the doctors are still disagreeing on whether or not gaming causes problems."

angry tapir writes "Government-funded researchers in Taiwan have developed a vending machine that recommends purchases based on people's faces. We've previously discussed a Japanese vending machine that recommended drinks based using facial recognition. The Taiwanese machine can look for clues like whether a person has glasses, a beard or a mustache and based on that it guesses their use of make-up or frequency of shaving. It then might recommend a facial mask, razor, or health products that people in a certain category are statistically likely to buy."

Reader jsrodrigues points out Businessweek's article on the predicted coming wave of office robots. These include offerings from Willow Garage, Anybots, and Smart Robots, all designed to automate certain bits of office-building meatspace gruntwork, like ferrying mail and making coffee, but more intelligently and smoothly than previous generations of such tools. Smart Robots has posted a scenario describing the benefits of office life with robots; a test run of robots from that company is set for early 2012 at "a major office building in Manhattan."

Em Adespoton writes "It was a computer security story that made headlines around the world, involving the private emails of a woman who could have become Vice President of the United States. And now, it's ended with a young man sent to a federal prison, hundreds of miles from his family home. David C Kernell, the hacker who broke into Sarah Palin's personal Yahoo email account, is reported to have been sent to jail despite a judge's recommendation that he should not be put behind bars."

mudimba writes "Microsoft has made grand announcements about how great their implementation of the HTML5 canvas specification is. However, while I was porting a large HTML5 application to work with IE9 beta I found that there are some key features missing. Workarounds are provided where possible. (Disclaimer: I am the author of the submitted article.)"

Sam writes "A former Ubisoft exec believes that Sony will not be able to combat piracy on the PlayStation 3, which was recently hacked. Martin Walfisz, former CEO of Ubisoft subsidiary Ubisoft Massive, was a key player in developing Ubisoft's new DRM technologies. Since playing pirated games doesn't require a modchip, his argument is that Sony won't be able to easily detect hacked consoles. Sony's only possible solution is to revise the PS3 hardware itself, which would be a very costly process. Changing the hardware could possibly work for new console sales, though there would be the problem of backwards compatibility with the already-released games. Furthermore, current users would still be able to run pirated copies on current hardware." An anonymous reader adds commentary from PS3 hacker Mathieu Hervais about Sony's legal posturing.

An anonymous reader writes "It may not seem like it, but 2010 has tied 2005 as the warmest year since people have been keeping records, according to data from NASA's Goddard Institute for Space Studies in New York. The two years differed by less than 0.018 degrees Fahrenheit. That difference is so small that it puts them in a statistical tie. In the new analysis, the next warmest years are 1998, 2002, 2003, 2006 and 2007, which are statistically tied for third warmest year. The GISS records begin in 1880." Adds jamie: "This was the 34th consecutive year with global temperatures above the 20th century average — 0.62 +/- 0.07 C above, to be precise. It was the wettest year on record too, according to the Global Historical Climatology Network."

An anonymous reader writes "We last heard about LVX's LED ceiling light optical communication system in December, and now news has broken that the company recently implemented the technology at several city offices in St. Cloud, Minnesota. The LVX/ceiling light system is capable of transmitting data at about three megabits per second, which is about as fast as a residential DSL line. It works by placing light-emitting diodes (LEDs) in a standard-sized light fixture. This then transmits coded binary messages to the special modems attached to computers, which also respond via light waves."

An anonymous reader writes "Over at Ars Technica, Peter (not so) Bright gives a long-winded four pages of FUD about how Chrome dropping support for H.264 is a slight against openness. 'The promise of HTML5's video tag was a simple one: to allow web pages to contain embedded video without the need for plugins. With the decision to remove support for the widespread H.264 codec from future versions of Chrome, Google has undermined this widely-anticipated feature. The company is claiming that it wants to support "open codecs" instead, and so from now on will support only two formats: its own WebM codec, and Theora. ... The reason Google has given for this change is that WebM (which pairs VP8 video with Vorbis audio) and Theora are "open codecs" and H.264 apparently isn't. ... H.264 is unambiguously open.'"

Alex writes "In the first update to Windows Phone 7, Microsoft is planning to block ChevronWP7, which allowed users to unlock any retail Windows Phone 7 device for application side-loading without having to pay $99 per year for a WP7 marketplace account. The update, which is slated for release this month, will also introduce copy and paste functionality, among other improvements. ChevronWP7 was discontinued less than a week after its release about two months ago. ChevronWP7's three developers, Long Zheng, Rafael Rivera, and Chris Walsh were approached by Brandon Watson, Director of Developer Experience for Windows Phone 7, and decided to kill their app."

J. Ayen Green writes "When the request came for me to review Drupal 6: Panels Cookbook by Bhavin (Vin) Patel, I was excited. I've been a software developer forever, a Web developer for as long as there's been a Web, and a Drupal developer since D6 was imminent. I have two Drupal books myself, and am working on one about D7 Views, but with all that, one glaring hole in my self-education has been Panels; it would be my first chance to use it." Keep reading for the rest of J. Ayen Green's review. Drupal 6: Panels Cookbook author Bhavin (Vin) Patel pages 220 publisher Packt Publishing rating 9/10 reviewer J. Ayen Gree ISBN 1849511187 summary contains step-by-step instructions for Drupal users to make optimum use of the Panels module Panels is the big cousin of the Views module, and big brother to the Panels Everywhere module. All were written by Earl Miles, aka merlinofchaos, a deserving macha in the Drupal community and, in my opinion, a topnotch coder: all the more reason to look forward to the book.

I need to mention the parameters within which I formed this review. I first considered the book format, because it greatly influences my expectations. A Packt 'cookbook' does not have the format or aims of a standard computer reference or 'Bible' text. It is meant to give the reader a broad but shallow exposure to a topic by using a plethora of step-by-step examples. Basically, if you come away from a cookbook feeling excited by the technology and wanting to dive deeper into learning it, the author has done a good job.

Patel starts off the book with the obligatory chapter on installation and setup, though this one contains a bit more since it is a broader Getting Started chapter. Panels is a contributed module, and installing it will be a familiar process to Drupalers. He covers installing Chaos Tools (Ctools) as well, since it is a required module. There are instructions for those upgrading from a prior release of Panels, too. Having installed and set up the module, Patel then leads you through creating a basic Panels page and node, the building blocks of a Panels layout.

It was early on that I discovered a couple things that made using the book more challenging than it needs to be. Patel uses a non-American dialect of English. While it's quite understandable, at times the usage and sentence structure require one to stop, blink, and reread the passage. Some might find this to be annoying. I looked at it as reading dialogue written by Dickens or Twain, and was fine with it. The other thing is that the instructions at times seem to skip a step, going from point A to point C without a mention of the requisite point B. Again, this causes the occasional confusion for a few moments, but nothing one cannot get past.

Chapter 2 covers a number of topics related to navigating and making use of the Panels interface and related topics. One might be biting at the bit to start creating meaty layouts by now, but Panels is a fairly complex framework to use, so having these 'recipes' available is important. Keep in mind that a 'cookbook' is designed so that most recipes are independent of each other, so they can usually be skipped over, if desired.

This chapter also touches on the topic of context, the context of 'context' here being the circumstances in which a layout exists. For example, with the standard capabilities of Drupal, a block is a fairly independent piece of content. If you want the content of a block to be intelligently related to the main content on the page, it's a difficult nut to crack aside. It can be achieved to some extent with the crafty use of Views, more so by writing a custom module, but becomes pleasantly easy using Panels. This is a big and important topic, and though this is a cookbook and not meant to be deep, I think this subject could have done with a chapter of its own.

Theming is the topic of Chapter 3. Even though Panels handles much of the work, there will likely be the desire to (re)theme its output to varying degrees, and this chapter guides the reader through examples of manipulating it with CSS, adding it to a theme region, and other useful topics.

In Chapter 4 we jump into examples of what is expected from Panels, doing things like replacing the front page, overriding the node edit form, using Panels with feeds and even using mini panels, basically panels within blocks. In Chapters 5 through 9 we move on to using Panels with other common Drupal add-on functionality: organic groups, the custom content kit (CCK), the advanced profile kit, composite layouts and Views.

Chapter 10 builds on much of what was covered and what Panels excels in by creating an example of a travel industry web site. The travel tie-in really doesn't matter, though, as one can easily extrapolate the example to whatever subject matter the intended site will contain.

I enjoyed working my way through the book. I found Patel's recipes to be creative and useful, and they gave me a sufficient understanding of Panels and its capabilities to begin considering possibilities for its use on existing and upcoming sites.

You can purchase Drupal 6: Panels Cookbook from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

J. Ayen Green writes "When the request came for me to review Drupal 6: Panels Cookbook by Bhavin (Vin) Patel, I was excited. I've been a software developer forever, a Web developer for as long as there's been a Web, and a Drupal developer since D6 was imminent. I have two Drupal books myself, and am working on one about D7 Views, but with all that, one glaring hole in my self-education has been Panels; it would be my first chance to use it." Keep reading for the rest of J. Ayen Green's review. Drupal 6: Panels Cookbook author Bhavin (Vin) Patel pages 220 publisher Packt Publishing rating 9/10 reviewer J. Ayen Gree ISBN 1849511187 summary contains step-by-step instructions for Drupal users to make optimum use of the Panels module Panels is the big cousin of the Views module, and big brother to the Panels Everywhere module. All were written by Earl Miles, aka merlinofchaos, a deserving macha in the Drupal community and, in my opinion, a topnotch coder: all the more reason to look forward to the book.

I need to mention the parameters within which I formed this review. I first considered the book format, because it greatly influences my expectations. A Packt 'cookbook' does not have the format or aims of a standard computer reference or 'Bible' text. It is meant to give the reader a broad but shallow exposure to a topic by using a plethora of step-by-step examples. Basically, if you come away from a cookbook feeling excited by the technology and wanting to dive deeper into learning it, the author has done a good job.

Patel starts off the book with the obligatory chapter on installation and setup, though this one contains a bit more since it is a broader Getting Started chapter. Panels is a contributed module, and installing it will be a familiar process to Drupalers. He covers installing Chaos Tools (Ctools) as well, since it is a required module. There are instructions for those upgrading from a prior release of Panels, too. Having installed and set up the module, Patel then leads you through creating a basic Panels page and node, the building blocks of a Panels layout.

It was early on that I discovered a couple things that made using the book more challenging than it needs to be. Patel uses a non-American dialect of English. While it's quite understandable, at times the usage and sentence structure require one to stop, blink, and reread the passage. Some might find this to be annoying. I looked at it as reading dialogue written by Dickens or Twain, and was fine with it. The other thing is that the instructions at times seem to skip a step, going from point A to point C without a mention of the requisite point B. Again, this causes the occasional confusion for a few moments, but nothing one cannot get past.

Chapter 2 covers a number of topics related to navigating and making use of the Panels interface and related topics. One might be biting at the bit to start creating meaty layouts by now, but Panels is a fairly complex framework to use, so having these 'recipes' available is important. Keep in mind that a 'cookbook' is designed so that most recipes are independent of each other, so they can usually be skipped over, if desired.

This chapter also touches on the topic of context, the context of 'context' here being the circumstances in which a layout exists. For example, with the standard capabilities of Drupal, a block is a fairly independent piece of content. If you want the content of a block to be intelligently related to the main content on the page, it's a difficult nut to crack aside. It can be achieved to some extent with the crafty use of Views, more so by writing a custom module, but becomes pleasantly easy using Panels. This is a big and important topic, and though this is a cookbook and not meant to be deep, I think this subject could have done with a chapter of its own.

Theming is the topic of Chapter 3. Even though Panels handles much of the work, there will likely be the desire to (re)theme its output to varying degrees, and this chapter guides the reader through examples of manipulating it with CSS, adding it to a theme region, and other useful topics.

In Chapter 4 we jump into examples of what is expected from Panels, doing things like replacing the front page, overriding the node edit form, using Panels with feeds and even using mini panels, basically panels within blocks. In Chapters 5 through 9 we move on to using Panels with other common Drupal add-on functionality: organic groups, the custom content kit (CCK), the advanced profile kit, composite layouts and Views.

Chapter 10 builds on much of what was covered and what Panels excels in by creating an example of a travel industry web site. The travel tie-in really doesn't matter, though, as one can easily extrapolate the example to whatever subject matter the intended site will contain.

I enjoyed working my way through the book. I found Patel's recipes to be creative and useful, and they gave me a sufficient understanding of Panels and its capabilities to begin considering possibilities for its use on existing and upcoming sites.

You can purchase Drupal 6: Panels Cookbook from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

An anonymous reader follows up to yesterday's Google announcement that they would drop H.264 support from Chrome. "Thomas Ford, Senior Communications Manager, Opera, told Muktware, 'Actually, Opera has never supported H.264. We have always chosen to support open formats like Ogg Theora and WebM. In fact, Opera was the first company to propose the tag, and when we did, we did it with Ogg. Simply put, we welcome Google's decision to rely on open codecs for HTML5 video.'"

Kayot writes "George Hotz, or, as he is known on the internet, GeoHot, has been served court papers. Shorty after Team fail0verflow discovered faults in the PS3's TPMs, Geohot and others figured out how to extract the long sought after holy grail encryption keys. Apparently Sony is not pleased and is very keen on defending their poorly defended system with the US legal system. The basis is that GeoHot released programs that allow the signing of homebrew which can be used to make PSN-like games out of normal PS3 games. However GeoHot has never supported any form of piracy and in fact has taken a constant stance against it."

Kayot writes "George Hotz, or, as he is known on the internet, GeoHot, has been served court papers. Shorty after Team fail0verflow discovered faults in the PS3's TPMs, Geohot and others figured out how to extract the long sought after holy grail encryption keys. Apparently Sony is not pleased and is very keen on defending their poorly defended system with the US legal system. The basis is that GeoHot released programs that allow the signing of homebrew which can be used to make PSN-like games out of normal PS3 games. However GeoHot has never supported any form of piracy and in fact has taken a constant stance against it."

donniebaseball23 writes "Earlier today, Verizon and Apple finally confirmed what everyone knew was coming: iPhone will soon launch on the Verizon network. The hugely popular iPhone has been a hit with gamers and game developers on the App Store, and by bringing the phone to the largest carrier in the US, the installed base suddenly could get much larger. The folks at social gaming network OpenFeint believe the Verizon iPhone impact could be immediately felt this year. 'The iPhone coming to Verizon is a highly anticipated event by the mobile gaming community,' said Peter Relan, chairman of OpenFeint. 'Adding 13 million more potential gamers on the iPhone is going to be a watershed moment for mobile gaming. I wouldn't be surprised if the US mobile gaming industry doubles in revenue this year because of this deal.'"

jfruhlinger writes "Tunisians logging into Facebook encountered extra JavaScript, probably a sign of their repressive government's attempt to spy on them. The question is: does the US government do the same thing, just more subtly? We're not talking about agents friending you on Facebook to get more information about you; we're talking monitoring your supposedly private information behind the scenes."

Ken writes "Microsoft CEO Steve Ballmer has said that the company will support Kinect for PCs sometime in the future. The motion controller is currently only officially supported for the Xbox 360, although it has been hacked and tweaked to work on pretty much any platform that can be plugged into via a USB port. 'We're trying to move beyond gaming to include the world of socialization, movies, TV, music, and we're trying to make the whole experience accessible to everybody in the family not just the traditional gamer.' When Ballmer was asked, 'Will you plug-in the Kinect to the PC, will you go for that in the near future?' he replied, 'We'll support that in a formal way in the right time and when we've got an announcement to make we'll make it.' Note that this is completely separate from the Kinect-like controller from PrimeSense and Asus." Other readers have tipped related articles about Kinect being used to enable 3D teleconferencing and help drive a small helicopter drone.

snydeq writes "Longtime Microsoft executive Bob Muglia, president of the company's server and tools business, will step down from his position later this year, according to a Steve Ballmer memo issued Monday to company employees. Muglia has been with Microsoft for 23 years, leading development efforts in Microsoft Office, Windows NT and online services businesses. More recently, Muglia shepherded Microsoft's entry into cloud computing, guiding the rollout of the company's Azure platform. Muglia's departure follows that of Ray Ozzie, whose exit was made all the more notable by a memo warning Microsoft to start thinking beyond the PC."

snydeq writes "Longtime Microsoft executive Bob Muglia, president of the company's server and tools business, will step down from his position later this year, according to a Steve Ballmer memo issued Monday to company employees. Muglia has been with Microsoft for 23 years, leading development efforts in Microsoft Office, Windows NT and online services businesses. More recently, Muglia shepherded Microsoft's entry into cloud computing, guiding the rollout of the company's Azure platform. Muglia's departure follows that of Ray Ozzie, whose exit was made all the more notable by a memo warning Microsoft to start thinking beyond the PC."

FrederickSeiler writes "When David Harriman, this book's author, was studying physics at Berkeley, he noticed an interesting contrast: 'In my physics lab course, I learned how to determine the atomic structure of crystals by means of x-ray diffraction and how to identify subatomic particles by analyzing bubble-chamber photographs. In my philosophy of science course, on the other hand, I was taught by a world-renowned professor (Paul Feyerabend) that there is no such thing as scientific method and that physicists have no better claim to knowledge than voodoo priests. I knew little about epistemology [the philosophy of knowledge] at the time, but I could not help noticing that it was the physicists, not the voodoo priests, who had made possible the life-promoting technology we enjoy today.' Harriman noticed the enormous gulf between science as it is successfully practiced and science as is it described by post-Kantian philosophers such as Feyerabend, who are totally unable to explain the spectacular achievements of modern science." Read on for the rest of Frederick's review. The Logical Leap: Induction In Physics author David Harriman pages 272 publisher NAL Trade rating 9/10 reviewer Frederick Seiler ISBN 0451230051 summary Explains how scientists discover the laws of nature Logical Leap: Induction in Physics attempts to bridge this gap between philosophy and science by providing a philosophical explanation of how scientists actually discover things. A physicist and physics teacher by trade, he worked with philosopher Leonard Peikoff to understand the process of induction in physics, and this book is a result of their collaboration.

Induction is one of the two types of logical argument; the other type is deduction. First described by Aristotle, deduction covers arguments like the following: (1) All men are mortal. (2) Socrates is a man. (3) Therefore, Socrates is mortal. Deductive arguments start with generalizations ("All men are mortal.") and apply them to specific instances ("Socrates"). Deductive logic is well understood, but it relies on the truth of the generalizations in order to yield true conclusions.

So how do we make the correct generalizations? This is the subject of the other branch of logic induction and it is obviously much more difficult than deduction. How can we ever be justified in reasoning from a limited number of observations to a sweeping statement that refers to an unlimited number of objects? In answering this question Harriman presents an original theory of induction, and he shows how it is supported by key developments in the history of physics.

The first chapter presents the philosophical foundations of the theory, which builds directly on the theory of concepts developed by Ayn Rand. Unfortunately for the general reader, Harriman assumes familiarity with Rand's theory of knowledge, including her views of concepts as open-ended, knowledge as hierarchical, certainty as contextual, perceptions as self-evident, and arbitrary ideas as invalid. Those unfamiliar with these ideas may find this section to be confusing. But the good news is that those readers can then proceed to the following chapters, which flesh out the theory and show how it applies to key developments in the history of physics (and the related fields of astronomy and chemistry). These chapters do a wonderful job at bringing together the physics and the philosophy, clarifying both in the process.

Harriman argues that as concepts form a hierarchy, generalizations form a hierarchy as well; more abstract generalizations rest on simpler, more direct ones, relying ultimately on a rock-solid base of "first-level" generalizations which are directly, perceptually obvious, such as the toddler's grasp of the fact that "pushed balls roll." First-level generalizations are formed from our direct experiences, in which the open-ended nature of concepts leads to generalizations. Higher-level generalizations are formed based on lower-level ones, using Mill's Methods of Agreement and Difference to identify causal connections, while taking into account the entirety of one's context of knowledge.

Ayn Rand held that because of the hierarchical nature of our knowledge, it is possible to take any valid idea (no matter how advanced), and identify its hierarchical roots, i.e. the more primitive, lower-level ideas on which it rests, tracing these ideas all the way back to directly observable phenomena. Rand used the word "reduction" to refer to this process. In a particularly interesting discussion, Harriman shows how the process of reduction can be applied to the idea that "light travels in straight lines," identifying such earlier ideas as the concept "shadow" and finally the first-level generalization "walls resist hammering hands."

Harriman's discussion of the experimental method starts with a description of Galileo's experiments with pendulums. Galileo initially noticed that the period of a pendulum's swing seems to be the same for different swing amplitudes, so he decided to accurately measure this time period to see if it is really true. Concluding that the period is indeed constant, he then did further experiments. He selectively varied the weight and material of the pendulum's bob, and the length of the pendulum. This led him to the discovery that a pendulum's length is proportional to the square of its period. Harriman notes the experiments that Galileo did not perform: 'He saw no need to vary every known property of the pendulum and look for a possible effect on the period. For example, he did not systematically vary the color, temperature, or smell of the pendulum bob; he did not investigate whether it made a difference if the pendulum arm is made of cotton twine or silk thread. Based on everyday observation, he had a vast pre-scientific context of knowledge that was sufficient to eliminate such factors as irrelevant. To call such knowledge "pre-scientific" is not to cast doubt on its objectivity; such lower-level generalizations are acquired by the implicit use of the same methods that the scientist uses deliberately and systematically, and they are equally valid.' One powerful tool for avoiding nonproductive speculations in science is Ayn Rand's concept of the arbitrary, and Harriman brilliantly clarifies this idea in the section on Newton's optical experiments. An arbitrary idea is one for which there is no evidence; it is an idea put forth based solely on whim or faith. Rand held that an arbitrary idea cannot be valid even as a possibility; in order to say "it is possible," one needs to have evidence (which can consist of either direct observations or reasoning based on observations).

Newton began his research on colors with a wide range of observations, which led him to his famous and brilliant experiments with prisms. Harriman presents the chain of reasoning and experimentation which led Newton to conclude that white light consists of a mixture of all of the colors, which are separated by refraction.

Isaac Newton said that he "framed no hypotheses," and here he was referring to his rejection of the arbitrary. When Descartes claimed without any evidence that light consists of rotating particles with the speed of rotation determining the color; and when Robert Hooke claimed without any evidence that white light consists of a symmetrical wave pulse, which results in colors when the wave becomes distorted; these ideas were totally arbitrary, and they deserved to be thrown out without further consideration: "Newton understood that to accept an arbitrary idea even as a mere possibility that merits consideration undercuts all of one's knowledge. It is impossible to establish any truth if one regards as valid the procedure of manufacturing contrary 'possibilities' out of thin air." This rejection of the arbitrary may be expressed in a positive form: Scientists should be focused on reality, and only on reality.

After discussing the rise of experimentation in physics, Harriman turns to the Copernican revolution, the astronomical discoveries of Galileo and Kepler, and the grand synthesis of Newton's laws of motion and of universal gravitation. But this reviewer found the most historically interesting chapter to be the one about the atomic theory of matter; this chapter is a cautionary tale about the lack of objective standards for evaluating theories. This story then leads to Harriman proposing a set of specific criteria of proof for scientific theories.

The final, concluding chapter addresses several broader issues, including why mathematics is fundamental to the science of physics, how the science of philosophy is different than physics, and finally, how modern physics has gone down the wrong path due to the lack of a proper theory of induction.

So, with the publication of Logical Leap, has the age-old "problem of induction" now been solved? On this issue, the reader must judge for himself. What is clear to this reviewer is that Harriman has presented an insightful, thought-provoking and powerful new theory about how scientists discover the laws of nature.

You can purchase The Logical Leap: Induction In Physics from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.