Slashdot Mirror

An anonymous reader writes "In late May, Data.gov will launch, in what US CIO Vivek Kundra calls an attempt to ensure that all government data 'that is not restricted for national security reasons can be made public' through data feeds. This appears to be a tremendous expansion on (and an official form of) third-party products like the Sunlight Labs API. Of course, it is still a far cry from 'open sourcing' the actual decision-making processes of government. Wired has launched a wiki for calling attention to datasets that should be shared as part of the Data.gov plan, and an article on O'Reilly discusses the importance of making this information easily accessible."

An anonymous reader writes "In late May, Data.gov will launch, in what US CIO Vivek Kundra calls an attempt to ensure that all government data 'that is not restricted for national security reasons can be made public' through data feeds. This appears to be a tremendous expansion on (and an official form of) third-party products like the Sunlight Labs API. Of course, it is still a far cry from 'open sourcing' the actual decision-making processes of government. Wired has launched a wiki for calling attention to datasets that should be shared as part of the Data.gov plan, and an article on O'Reilly discusses the importance of making this information easily accessible."

thefickler writes "Microsoft is opposing an industry plan, the Open Cloud Manifesto, to promote cloud computing interoperability. Officially, Microsoft says the plan is unnecessarily secretive and that cloud computing is still in an early stage of development, but there are allegations that Microsoft feels threatened by the plan because it could boost Linux-based systems. The goal of the group behind the manifesto, the Cloud Computing Interoperability Forum (CCIF), is to minimize the barriers between different technologies used in cloud computing. And this is where the problem seems to lie, with the group stating that 'whenever possible the CCIF will emphasize the use of open, patent-free and/or vendor-neutral technical solutions.' Some speculate that Microsoft is actually worried that this will allow open source systems, such as Linux, to flourish, at the expense of Microsoft technology." Amazon is also declining to support the plan, saying, "the best way to illustrate openness and customer flexibility is by what you actually provide and deliver for them." Reader smack.addict contributes a link to an O'Reilly piece asking what openness really means for cloud computing.

An IBM-Sun merger is a tantalyzing possibility; snydeq writes "Fatal Exception's Neil McAllister suggests that an IBM/Sun merger could crown Big Blue king of enterprise software development. 'Acquiring Sun would make IBM the clear leader in Java, as it would become the caretaker of the open source reference implementation of the JRE,' which, along with GlassFish, would become entry-level gateways to IBM's WebSphere stack. Moreover, MySQL would give IBM's database division a significant entry-level hook, and NetBeans/Eclipse would unify IBM's front against Visual Studio. 'All in all, this move would solidify IBM's role as "the developer company,"' McAllister writes. 'In other words, if this merger goes through and you're an enterprise developer and you're not an IBM customer now, get ready — because you soon will be. Better bring your wallet.'" And blackbearnh writes with a short interview with Brian Aker (who came to Sun as MySQL's director of architecture, and is now the lead for MySQL fork Drizzle) about what life would be like under Big Blue's control.

An IBM-Sun merger is a tantalyzing possibility; snydeq writes "Fatal Exception's Neil McAllister suggests that an IBM/Sun merger could crown Big Blue king of enterprise software development. 'Acquiring Sun would make IBM the clear leader in Java, as it would become the caretaker of the open source reference implementation of the JRE,' which, along with GlassFish, would become entry-level gateways to IBM's WebSphere stack. Moreover, MySQL would give IBM's database division a significant entry-level hook, and NetBeans/Eclipse would unify IBM's front against Visual Studio. 'All in all, this move would solidify IBM's role as "the developer company,"' McAllister writes. 'In other words, if this merger goes through and you're an enterprise developer and you're not an IBM customer now, get ready — because you soon will be. Better bring your wallet.'" And blackbearnh writes with a short interview with Brian Aker (who came to Sun as MySQL's director of architecture, and is now the lead for MySQL fork Drizzle) about what life would be like under Big Blue's control.

Hugh Pickens writes "Jonathan Berger, a professor of music at Stanford, tests his incoming students each year by having them listen to a variety of recordings which use different formats from MP3 to ones of much higher quality, and he reports that each year the preference for music in MP3 format rises. Berger says that young people seemed to prefer 'sizzle sounds' that MP3s bring to music because it is a sound they are familiar with. 'The music examples included both orchestral, jazz and rock music. When I first did this I was expecting to hear preferences for uncompressed audio and expecting to see MP3 (at 128, 160 and 192 bit rates) well below other methods (including a proprietary wavelet-based approach and AAC),' writes Berger. 'To my surprise, in the rock examples the MP3 at 128 was preferred. I repeated the experiment over 6 years and found the preference for MP3 — particularly in music with high energy (cymbal crashes, brass hits, etc) rising over time.' Dale Dougherty writes that the context of the music changes our perception of the sound, particularly when it's so obviously and immediately shared by others. 'All that sizzle is a cultural artifact and a tie that binds us. It's mostly invisible to us but it is something future generations looking back might find curious because these preferences won't be obvious to them.'"

BigTimOBrien writes "In this interview with O'Reilly Broadcast, Carl Malamud discusses his grassroots effort to build support for his appointment as Public Printer of the United States, running the Government Printing Office — an agency that opened its doors the day Abraham Lincoln was inaugurated. Malamud has published his plans and platform on yeswescan.org: 'For over 20 years, Carl Malamud has been publishing government information on the Internet. In 2008, Public.Resource.Org published over 32.4 million pages of primary legal materials, as well as thousands of hours of video and thousands of photographs. In the 1990s, Malamud fought to place the databases of the United States on the Internet. In the 1980s, Malamud fought to make the standards that govern our global Internet open standards available to all. Malamud would continue to work to preserve and extend our public domain, and would place special attention to our relationship with our customers, especially the United States Congress.'"

BigTimOBrien writes "In this interview with O'Reilly Broadcast, Carl Malamud discusses his grassroots effort to build support for his appointment as Public Printer of the United States, running the Government Printing Office — an agency that opened its doors the day Abraham Lincoln was inaugurated. Malamud has published his plans and platform on yeswescan.org: 'For over 20 years, Carl Malamud has been publishing government information on the Internet. In 2008, Public.Resource.Org published over 32.4 million pages of primary legal materials, as well as thousands of hours of video and thousands of photographs. In the 1990s, Malamud fought to place the databases of the United States on the Internet. In the 1980s, Malamud fought to make the standards that govern our global Internet open standards available to all. Malamud would continue to work to preserve and extend our public domain, and would place special attention to our relationship with our customers, especially the United States Congress.'"

theodp writes "Pressed on Amazon's 1-Click patent, then-USPTO Chief Q. Todd Dickinson got testy: "I make this challenge all the time. If you're aware of prior art out there that invalidates a patent that is existing, file a re-examination. We'll be happy to take a look at it." Really? It's been 3+ years since unemployed actor Peter Calveley submitted prior art that triggered a USPTO reexamination of the 1-Click patent. Still no 'final answer' from the USPTO. To put things in perspective, 1-Click inventor Jeff Bezos once proposed a three-year lifespan for patents (later retracted), let alone patent reexams. In the meantime, other patent examiners have repeatedly smacked down 1-Click — the latest (non-final) rejection was issued on Feb. 10th with Sandra Bullock's help."

blackbearnh writes "Scientific data can be both hard to get and expensive, even if your tax dollars paid for it. And if you do pay the big bucks to a publisher for access to a scientific paper, there's no assurance that you'll be able to read it, unless you've spent your life learning to decipher them. That's the argument that John Wilbanks makes in a recent interview on O'Reilly Radar, describing the problems that have led to the creation of the Science Commons project, which he heads. According to Wilbanks, scientific data should be easy to access, in common formats that make it easy to exchange, and free for use in research. He also wants to see standard licensing models for scientific patents, rather than the individually negotiated ones now that make research based on an existing patent so financially risky." Read on for the rest of blackbearnh's thoughts. "Wilbanks also points of that as the volume of data grows from new projects like the LHC and the new high-resolution cameras that may generate petabytes a day, we'll need to get better at determining what data to keep and what to throw away. We have to figure out how to deal with preservation and federation because our libraries have been able to hold books for hundreds and hundreds and hundreds of years. But persistence on the web is trivial. Right? The assumption is well, if it's meaningful, it'll be in the Google cache or the internet archives. But from a memory perspective, what do we need to keep in science? What matters? Is it the raw data? Is it the processed data? Is it the software used to process the data? Is it the normalized data? Is it the software used to normalize the data? Is it the interpretation of the normalized data? Is it the software we use to interpret the normalization of the data? Is it the operating systems on which all of those ran? What about genome data?'"

blackbearnh writes "Scientific data can be both hard to get and expensive, even if your tax dollars paid for it. And if you do pay the big bucks to a publisher for access to a scientific paper, there's no assurance that you'll be able to read it, unless you've spent your life learning to decipher them. That's the argument that John Wilbanks makes in a recent interview on O'Reilly Radar, describing the problems that have led to the creation of the Science Commons project, which he heads. According to Wilbanks, scientific data should be easy to access, in common formats that make it easy to exchange, and free for use in research. He also wants to see standard licensing models for scientific patents, rather than the individually negotiated ones now that make research based on an existing patent so financially risky." Read on for the rest of blackbearnh's thoughts. "Wilbanks also points of that as the volume of data grows from new projects like the LHC and the new high-resolution cameras that may generate petabytes a day, we'll need to get better at determining what data to keep and what to throw away. We have to figure out how to deal with preservation and federation because our libraries have been able to hold books for hundreds and hundreds and hundreds of years. But persistence on the web is trivial. Right? The assumption is well, if it's meaningful, it'll be in the Google cache or the internet archives. But from a memory perspective, what do we need to keep in science? What matters? Is it the raw data? Is it the processed data? Is it the software used to process the data? Is it the normalized data? Is it the software used to normalize the data? Is it the interpretation of the normalized data? Is it the software we use to interpret the normalization of the data? Is it the operating systems on which all of those ran? What about genome data?'"

frdmfghtr writes "According to a boxee blog entry, Hulu will no longer be supported. From the post: 'two weeks ago Hulu called and told us their content partners were asking them to remove Hulu from boxee. we tried (many times) to plead the case for keeping Hulu on boxee, but on Friday of this week, in good faith, we will be removing it. you can see their blog post about the issues they are facing.' Reading the hulu blog post, the only 'issue' I see facing Hulu is that content providers have (once again) shot themselves in the foot, switching off a media conduit they should have been promoting." Update: 02/19 14:31 GMT by T : Jamie points out this interesting (speculative) piece at O'Reilly Radar about the thought process that may have driven the decision.

blackbearnh writes "If you've gotten tired of hacking firewalls or cloud computing, maybe it's time to try your hand with DNA. That's what Reshma Shetty is doing with her Doctorate in Biological Engineering from MIT. Apart from her crowning achievement of getting bacteria to smell like mint and bananas, she's also active in the developing field of synthetic biology and has recently helped found a company called Gingko BioWorks which is developing enabling technologies to allow for rapid prototyping of biological systems. She talked to O'Reilly Radar recently about the benefits and potential dangers of easy biological design, why students should be hacking wetware, and what's involved in setting up your own lab to slice genes."

blackbearnh writes "If you've gotten tired of hacking firewalls or cloud computing, maybe it's time to try your hand with DNA. That's what Reshma Shetty is doing with her Doctorate in Biological Engineering from MIT. Apart from her crowning achievement of getting bacteria to smell like mint and bananas, she's also active in the developing field of synthetic biology and has recently helped found a company called Gingko BioWorks which is developing enabling technologies to allow for rapid prototyping of biological systems. She talked to O'Reilly Radar recently about the benefits and potential dangers of easy biological design, why students should be hacking wetware, and what's involved in setting up your own lab to slice genes."

stoolpigeon writes in with news that ought to kindle Amazon's attention: "O'Reilly announced recently that they are now hosting Bookworm, an online ePub reader. ePub is composed of three open standards (OPS, OPF, and OCF) that allow users a great amount of flexibility without any lock-in. Bookworm lets users upload ePub files, read them online from a PC or mobile device, and also export them to mobile devices that support ePub. Bookworm can also export directly to Stanza. Once a user has uploaded their ePub books to Bookworm, they can track progress through them even across multiple devices."

stoolpigeon writes in with news that ought to kindle Amazon's attention: "O'Reilly announced recently that they are now hosting Bookworm, an online ePub reader. ePub is composed of three open standards (OPS, OPF, and OCF) that allow users a great amount of flexibility without any lock-in. Bookworm lets users upload ePub files, read them online from a PC or mobile device, and also export them to mobile devices that support ePub. Bookworm can also export directly to Stanza. Once a user has uploaded their ePub books to Bookworm, they can track progress through them even across multiple devices."

blackbearnh writes "While China is attempting to pull its industry up out of mere manufacturing mode, for now the country is the production workhorse of the consumer electronics industry. Almost anything you pick up at a Best Buy first breathed life across the Pacific Ocean. But what is it like to shepherd a product through the design and production process? Andrew 'bunnie' Huang has done just that with the Chumby, a new Internet appliance. In an interview with O'Reilly Radar, he talks about the logistical and moral issues involved with manufacturing in China, as well as his take on the consumer's right to hack the hardware they purchase."

blackbearnh writes "While China is attempting to pull its industry up out of mere manufacturing mode, for now the country is the production workhorse of the consumer electronics industry. Almost anything you pick up at a Best Buy first breathed life across the Pacific Ocean. But what is it like to shepherd a product through the design and production process? Andrew 'bunnie' Huang has done just that with the Chumby, a new Internet appliance. In an interview with O'Reilly Radar, he talks about the logistical and moral issues involved with manufacturing in China, as well as his take on the consumer's right to hack the hardware they purchase."

An anonymous reader writes "According to the Santa Rosa Press Democrat, geeky tech publisher O'Reilly Media has slashed 14% of its workforce, or 31 people. Founder and tech pundit Tim O'Reilly comments on the layoffs by exhorting people to 'get more with less.' According to the article, 'Just this week... both tech giant Google and book retailer Barnes & Noble announced their first layoffs ever. Other publishing houses, including HarperCollins, Houghton Mifflin Harcourt, Random House, and Simon & Schuster have frozen salaries or cut jobs, or both.'"

chromatic writes to tell us that O'Reilly has an interview with Guido van Rossum on the evolutionary process that gave us Python 3.0 and what is in store for the future. "I'd like to reiterate that at this point, it's a very personal choice to decide whether to use 3.0 or 2.6. You don't run the risk of being left behind by taking a conservative stance at this point. 2.6 will be just as well supported by the same group of core Python developers as 3.0. At the same time, we're also not sort of deemphasizing the importance and quality of 3.0. So if you are not held back by external requirements like dependencies on packages or third party software that hasn't been ported to 3.0 yet or working in an environment where everyone else is using another version. If you're learning Python for the first time, 3.0 is a great way to learn the language. There's a couple of things that trip over beginners have been removed."

Michael J. Ross writes "After installing and learning the basics of the content management system Drupal, many Web developers do not know how to best proceed from there. They may realize that much of the programming potential of Drupal — and thus the earning potential of Drupal developers — is derived from the use of community-contributed modules that greatly extend Drupal's power. But there are thousands of such modules, with no objective direction as to which ones are best suited for particular tasks, and what bugs and other flaws could trip up the developer. These programmers need a thorough guide as to which modules are the most promising for the development of the most common types of Web sites. A new book, Using Drupal, aims to fill this need." Keep reading for the rest of Michael's review. Using Drupal author Angela Byron, Addison Berry, Nathan Haug, Jeff Eaton, James Walker, and Jeff Robbins pages 490 publisher O'Reilly Media rating 9/10 reviewer Michael J. Ross ISBN 978-0596515805 summary Key contributed Drupal modules put to use creating sample sites. Published by O'Reilly Media on 16 December 2008, under the ISBN 978-0596515805, the book is authored by Angela Byron, Addison Berry, Nathan Haug, Jeff Eaton, James Walker, and Jeff Robbins — all of whom are affiliated with Lullabot and are actively involved in the Drupal community and knowledgeable about Drupal's core and plug-in modules. Despite the old adage about having too many cooks in the kitchen, a technical book of this nature should benefit from having half a dozen authors, since each one will have his or her fortes, and the whole will be greater than the sum of the parts, as a result of this complementary expertise.

This title appears to be O'Reilly's first — and, as of this writing, only — Drupal book. This is in no way astonishing, given that O'Reilly has never been known for pushing books too quickly through development and production, simply to gain "first mover advantage." Rather, they generally work to create higher-quality efforts that will better stand the test of time — unlike the "shovel" books that some other publishers tend to push out the door, with less coherence and more errata. As a consequence, in the technical libraries of veteran programmers, one tends to see a disproportionately high number of book covers sporting pictures of animals.

On the publisher's Web page for Using Drupal, visitors can read the book's description, table of contents, colophon, errata (of which there are currently several), a link for purchasing the book in electronic form (in formats such as PDF, EPUB, and Kindle-compatible Mobipocket), and a link for viewing the book immediately online, in the Safari Books Online system. There is a simple forum for the book, which currently contains seven posts, three of which already have replies from one of the book's authors and from an O'Reilly community manager. There is a browse system that allows the visitor to read portions of each section of each chapter, and thus preview the book before purchasing it. It even includes the illustrations within each previewed section, but for some reason does not include the figure numbers within the captions.

The authors have created their own site dedicated to the book, where visitors will find brief author biographies largely similar to those found at the very end of the book, with links to the authors' profile pages on Drupal.org. Lastly, there is a download page for the source code, which comprises a copy of Drupal 6, all of the contributed modules and themes needed to complete the hands-on exercises, and the supplementary resource files for those exercises, such as logos and product images. There is a change log for the download file, and yet no mention on the page — or even in the book itself, as far as I can tell — as to which version in the 6.x release series was used for the book and in the download package.

Oddly, neither the publisher's site nor the authors' site appears to mention the free downloadable chapter (Chapter 9, "Event Management"), although it is offered in an article posted in the blog section of Do It with Drupal.

After a foreword by Dries Buytaert — Drupal's founder and project lead — the book continues for 490 pages in total, organized into eleven chapters and three appendices. Nine of the chapters each begin with a description of a case study that will be used for illustrative purposes, followed by some implementation notes, which includes discussion of the candidate modules that could be used for this particular case study, and the trade-offs among them. The contributed modules that are chosen for the implementation and their capabilities are summarized, and then further explained with hands-on exercises — in which the particular modules are utilized and configured. Each of these nine chapters takes the reader through the development of a complete Web site, and is wrapped up with discussion of additional modules applicable to the kind of Web site being created. In Chapters 2 through 10, the case studies are: a simple Drupal site that supports client editing, a job posting board, a product reviews site, a wiki, a site for managing publishing workflow, a photo gallery, multilingual sites, an entertainment events management site, and an online store. Chapter 1 provides an overview of Drupal — covering modules, users, nodes, organizational schemes, and content types — preceded by a brief history of content management systems. Chapter 11 explores site theming, with details on the files and other elements that make up a theme, and how to customize them. The book's three appendices cover installing and upgrading Drupal, choosing the right modules for a job, and a list of the modules and themes used in the book.

The book's material is current with Drupal version 6, but should be of some value to any developer opting, for whatever reason, to stick with version 5. Speaking of versions, the authors should have mentioned which version of Drupal they chose, including the minor release number. The Drupal code in the aforesaid download package indicates that the chosen version is 6.4.

This book is unique, in that most if not all other Drupal books on the market are either introductory in nature — which at best devote only a single chapter to discussing third-party modules contributed by developers — or more advanced, specializing in a particular subject area, such as Drupal site security or e-commerce. Using Drupal, just as the title indicates, examines the detailed usage of best-of-breed modules to accomplish specific goals that one often encounters as a Web developer.

One of the most valuable aspects of software development books written by veteran programmers, is their discussions of various solutions to a particular problem — regardless of its size or complexity — and the reasons why they chose one approach instead of any of the others. Using Drupal is no exception. The authors examine the advantages and disadvantages of various third-party modules, even those that were not chosen for implementing the sample Web sites.

In any computer programming book, screenshots and other figures can be most helpful to the reader, because they reinforce the narrative descriptions of the cumulative results of all the steps up to that point. The screenshots are even valuable to someone following along on his own computer, because they provide immediate confirmation that he has not missed a critical step in the process. Using Drupal offers a generous amount of such screenshots, as well as information tables that help in visually breaking up the text. The only weakness with some of the screenshots is the lack of contrast between the text and the background, resulting in a dark gray shown on a light gray background — not always clearly readable.

The book is substantial in length and content, and naturally it cannot adequately cover dozens of sorts of Web sites. But clearly the book would have been more complete if it contained a chapter explaining how to allow content to be viewable by a limited set of authenticated users. An ideal case study for this would be the implementation of an e-zine site, for which prospective subscribers could view the homepage and other marketing material, but only subscribers could read the actual e-zine's contents. Even better would be to make this sample site fee-based, and show how to accept payments through PayPal (or some other payment systems for which there are Drupal modules) and possibly validate new subscribers automatically and instantly, using PayPal's IPN feature.

The flaws of this book are few and minor. There are unreported errata, most of them grammatical — e.g., "as [the] ability" (page 10) and "modules [that] were" (page 89) — which are to be expected in the first edition of any technical book. Speaking of errata, on the publisher's Web site, the errata should be sorted — or sortable — by page number, so it is much faster for people to see if a discovered erratum has already been reported. In addition, the URLs within the book that do not contain any filename (e.g., "http://www.example.com"; page 8) are in most if not all cases missing the trailing "/" (the root directory). Yet my primary complaint pertains to its production, and not its writing: For countless lines within the text, the spaces separating the words are too narrow, making it difficult to distinguish the words from one another when reading rapidly. As a consequence, each one of these lines almost appears to be a single word. (Skilled programmers know the great value of using whitespace in their code for enhancing readability; the same is certainly true for the printed word.) This readability problem is exacerbated by two factors: The ink color does not appear to be pure black, but instead a dark gray, which possibly has the advantage of producing less glare, but provides less contrast. Secondly, the serif font selected (whose name does not seem to be identified in the book — a common practice ages ago) has quite thin curves, which arguably does make the font face more stylish, but diminishes readability.

In terms of the target audience, the authors do not assume that the reader knows PHP (although some is shown in the chapter on theming), but they do assume that the reader is comfortable installing a PHP-based content management system and all of its required technologies, and familiar enough with Drupal to be able to navigate through the administrative area, download and add modules, and perform other basic admin tasks. Programmers just getting started with Drupal will benefit the most from this book, while experienced Drupal programmers will most likely learn some hitherto unknown best practices, and perhaps even some valuable modules or techniques that the individual has never seen before.

Using Drupal is a detailed and information-packed guide to the most promising contributed modules, and how they can be best employed for creating common types of Web sites. Drupal developers should find this a valuable part of their technical library, especially when they begin creating one of those types of Web sites for the first time.

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

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

blackbearnh writes "If you've watched the Discovery Channel series 'Storm Chasers,' you'll be familiar with Dr. Joshua Wurman and his Doppler on Wheels radar, which he uses to study tornadoes up close and personal every spring. O'Reilly Media spent some time last week speaking to Dr. Wurman about what it takes, technologically, to operate a weather radar in 100-mile-per-hour winds in the middle of a lightning storm. They also talked about the value of this kind of research to both tornado and hurricane research, and how having a film crew around during missions affects the science."

blackbearnh writes "If you've watched the Discovery Channel series 'Storm Chasers,' you'll be familiar with Dr. Joshua Wurman and his Doppler on Wheels radar, which he uses to study tornadoes up close and personal every spring. O'Reilly Media spent some time last week speaking to Dr. Wurman about what it takes, technologically, to operate a weather radar in 100-mile-per-hour winds in the middle of a lightning storm. They also talked about the value of this kind of research to both tornado and hurricane research, and how having a film crew around during missions affects the science."

George Reese writes "It seems a lot of people are mistaking the very valuable benefit that cloud computing enables — dynamically scaling your infrastructure — with the potentially dangerous ability to scale your infrastructure automatically in real-time based on actual demand. An O'Reilly blog entry discusses why auto-scaling is not as cool a feature as you might think."

blackbearnh writes "Last week, the net was all abuzz with speculation that SCO was finally gone and done for. With the final judgment in SCO v. Novell in, and SCO millions of dollars in the hole to Novell, it seemed like the fat lady had finally sung. But like most things in the legal system, it isn't nearly that simple. O'Reilly Media sought out Groklaw's Pamela Jones, and got a rundown of what's still alive, and why a final end to the madness may be many years away. 'Summing up, it looks bleak for SCO at the moment, but let's enter the alternate realm of SCO's best-case scenario in its dreams: in that realm, SCO wins on appeal, which one of SCO's lawyers indicated might take a year and a half or five years, and the case is sent back to Utah for trial by jury, which is what SCO wanted (as opposed to trial by judge, which is what it got), then everything listed above (except for the IPO class action) comes alive again, presumably, depending on what the appellate court decides. Then SCO is in position once again to go after Linux end users, as well as IBM, et al.'"

blackbearnh writes "Last week, the net was all abuzz with speculation that SCO was finally gone and done for. With the final judgment in SCO v. Novell in, and SCO millions of dollars in the hole to Novell, it seemed like the fat lady had finally sung. But like most things in the legal system, it isn't nearly that simple. O'Reilly Media sought out Groklaw's Pamela Jones, and got a rundown of what's still alive, and why a final end to the madness may be many years away. 'Summing up, it looks bleak for SCO at the moment, but let's enter the alternate realm of SCO's best-case scenario in its dreams: in that realm, SCO wins on appeal, which one of SCO's lawyers indicated might take a year and a half or five years, and the case is sent back to Utah for trial by jury, which is what SCO wanted (as opposed to trial by judge, which is what it got), then everything listed above (except for the IPO class action) comes alive again, presumably, depending on what the appellate court decides. Then SCO is in position once again to go after Linux end users, as well as IBM, et al.'"

Joel Aufgang writes "O'Reilly Media's O'Reilly School of Technology in partnership with the University of Illinois has just launched a Java Programming Certificate Series, which looks like it's intended to compete with the Sun Certified Java Programmer (SCJP) certification. According to O'Reilly's press release, this is not an exam-based certification but rather a series of project based instructor-led courses that, if you pass, earns certification backed by the University of Illinois. Also interesting is the use of Eclipse as the preferred learning platform as opposed to Netbeans."

Geek Satire writes "Politics breeds cynicism; politicians seem to pander to contradictory focus groups to get elected, then break their promises to everyone. Mass mailings and faxings overwhelm their staffs, and who knows if you can tell your representatives what you really think? Experienced techie and political consultant Silona Bonewald (creator of the Transparent Federal Budget) believes that simple software solutions can fix these problems and more. O'Reilly News recently discussed with her how social software can improve democracy and leadership."

Geek Satire writes "Voting works only if you believe your vote gets counted accurately. The 2008 US elections have avoided many well-known problems of the 2004 and 2000 elections, but many problems remain. O'Reilly News interviewed Dr. Barbara Simons, advisor to the Federal Election Assistance Commission, to review electronic voting in the 2008 US elections, discussing the physical security of storing and maintaining election machines, the move from electronic back to paper ballots, and why open source voting machines don't necessarily solve problems of bugs, backdoors, and audits."

Michael J. Ross writes "As Internet users' expectations continue to ratchet upwards, it is increasingly essential that every Web site owner maximize the chances that those users will find the site in question, and, once found, that the site will perform well enough that those visitors become customers or members, and recommend the site to others. Key elements of a successful strategy include optimization for search engines, pay-per-click advertising, and visitor conversion, as well as responsive Web pages and fine-tuning of all the above, using various metrics. These topics and others are explored in Website Optimization: Speed, Search Engine & Conversion Rate Secrets by Andrew B. King." Keep reading for the rest of Michael's review. Website Optimization author Andrew B. King pages 394 publisher O'Reilly Media rating 8/10 reviewer Michael J. Ross ISBN 0596515081 summary Techniques for increasing a site's SEO, conversion rates, and speed. The book was published by O'Reilly Media on 15 July 2008, under the ISBNs 0596515081 and 978-0596515089. Website Optimization is organized into two major parts: search engine marketing optimization and Web performance optimization. The book's material, spanning 394 pages, is divided into 10 chapters, covering a range of topics: natural search engine optimization, an SEO case study, pay-per-click optimization, a case study thereof, conversion rate optimization, Web page performance, CSS optimization, AJAX optimization, server- and client-side performance techniques, and Web site metrics. The book begins with a forward by Jim Sterne, a Web marketing and metrics consultant, followed by a preface in which Andy King provides an overview of what is to follow, as well as credits to four other individuals. These credits are confusing, because they do not make clear for what exactly the individuals are being credited! The reader will be left wondering: Are these people the technical editing team? Or did they write some of the material in the book, without byline? Or did they only provide research material to the primary author? In personal correspondence to me, Andy King mentions that this book was "written by a team of experts let [sic] by me." Thus, they are apparently co-authors, but not identified as so in the book.

The first five chapters of the book focus on optimization of search engine marketing (SEM), which comprises search engine optimization (SEO), pay-per-click (PPC) advertising, and conversion rate optimization (CRO). The author(s) begin by demonstrating, through cited statistics, just how critical it is for Web sites to appear within the first few search engine result pages (SERPs), otherwise the sites will probably not be found by the roughly 90 percent of Internet users who do not bother looking at any subsequent pages. This documented selectivity should alone serve as an energizing wake-up call to any Web site owners who — either through ignorance or laziness — make no effort to improve their rankings within the major search engine results. The first chapter delineates the most common SEO mistakes, as well as basic techniques for achieving higher rankings. The two categories could have been combined, simply by inverting the language of the first category; for instance, "develop an adequate number of popular inbound links" could replace "[avoid] a lack of popular inbound links." The bulk of the SEO information will be familiar to most Web marketing veterans, though even they should glean some new pointers. All of the advice is correct, up-to-date, and worthy of implementation on any site — existing or under development. However, the "Step 3" and "Step 4" in Figures 1-6 and 1-7 may be confused by some readers with the identical section headings in the book's text. Note also that the KEI of "84,100" should instead read "84.100" (page 17). Lastly, the first and third sample URIs are missing GET keys (page 29).

The strategies for natural search engine optimization, presented in the first chapter, are illustrated in the second — through a case study of the SEO overhaul of a Philadelphia dental practice's Web site. The original version of the site was lacking keyword-rich headers, body copy, inbound links, etc. (In addition, the dentist's e-mail address was revealed to spam harvesters in plain text. Andy King mentions the use of a contact form to resolve this problem, but does not mention that there are methods of displaying an e-mail address to human visitors, while hiding it from spambots.) This site's search engine results were dramatically boosted through two iterations of SEO fine-tuning, redesign, and release. While this particular dentist's site was greatly improved by the work described in this chapter, the book itself is not improved by inclusion of said chapter, since no additional SEO techniques are offered to the reader, and the first chapter already had enough HTML code snippets to exemplify the concepts discussed. In fact, the case study results should have been boiled down to a few paragraphs and better presented as a sidebar at the end of the first chapter, or moved to the back as an appendix. This latter approach is further supported by the fact that the second chapter illustrates best practices discussed in chapters that the reader has presumably yet to read (5 and 6). The material that composes the actual last sidebar in the first chapter — on metadata and microformats — could have been relegated to an appendix.

Search engine-based ad campaigns are the most important elements in the marketing strategies of countless online vendors, and in Chapter 3, Andy King explains how to increase a site's pay-per-click results, click-through rates (CTRs), and conversion rates. He begins by explaining some key terms and concepts, which should be quite helpful for most readers — especially given how much the online marketing world is laden with terminology and acronyms. The chapter reviews the advertising programs of the three top search engines, and discusses PPC optimization for those programs, with special emphasis given to Google AdWords. Like the first chapter of the book, this one does a competent job of explaining and illustrating the key ideas, and making clear topics that can be quite daunting to anyone new to the field. However, additional clarification of some terms would be helpful, otherwise many readers may be uncertain as to what is meant by terms such as "negative keywords," which unfortunately are left undefined. Even phrases outside the online marketing industry, such as "second-price sealed bidding system," could confuse countless readers. More importantly, some of the material is discussed at a level higher than what would be really usable for most site owners and developers — in contrast to the first chapter, which generally presented more actionable details. In fact, for readers unfamiliar with all the factors involved in running a PPC ad campaign, the early portion of this chapter could prove quite bewildering. Returning to the issue of how best to present case studies, the "Bid Optimization in Action: The E-Grooming Book Example" section shows how illustrative examples can be presented much more concisely. In contrast, Chapter 4, which consumes eight pages, shows how not to illustrate concepts already discussed.

Considerable SEO and PPC efforts could pay off in the form of a huge increase in traffic to one's Web site. But all of that would be in vain if there were no corresponding increase in turning those visitors into customers. Chapter 6 is devoted to conversion rate optimization, and presents some key elements of persuading online prospects, as well as the top 10 factors for maximizing one's conversion rates, from an online marketing and sales perspective. This chapter is rich in material that should inspire site owners to critically reevaluate their sites' contents, as well as their competitors'.

The sixth chapter, on Web page optimization, commences the second part of the book, and explores the most common pitfalls that lead to poor site performance, as well as ten techniques for increasing page display speeds — many of them based upon Steve Souders's book High Performance Web Sites. Andrew King correctly notes that this optimization can result in increased profits, customer satisfaction, and accessibility. However, he also claims that it will decrease costs as well as improve site maintainability and search engine rankings. He should have made it clear that faster page loading per se will not provide those last three benefits, but rather those are potential secondary gains that result from changes to code and other factors with the goal of decreasing page load times for site visitors. Nonetheless, even the most experienced Web developers should find one or more ideas in this chapter for reducing the total bandwidth consumption of the pages they create — particularly for anyone serving video content, which receives substantial coverage in this chapter. Chapter 7, on CSS optimization, follows a pattern similar to its predecessor, by presenting ten methods for improving one's CSS code, as helpful rules. The advice is spot-on, and well illustrated with examples. The suggested methods are preceded by brief discussion of reset rules, including mention of the (differing) reset rules advocated by Eric Meyer and Yahoo. It would be interesting to have learned the author's perspective on the technical differences, and why the author chose one set of rules over another. Incidentally, the paragraph describing the section, immediately below the "Tip #1" header, should have been located above it. Also, on page 195, " | inherit" should have been explained, or, better yet, excised. Lastly, the "|" appears to be missing from the similar instances on the three subsequent pages.

During the past several years, there has been a huge increase in the usage of Asynchronous JavaScript and XML (AJAX) to reduce dynamic Web page reloading, and to make Web sites behave more like desktop applications. Unfortunately, there are pitfalls in this approach, and Andy King discusses them in Chapter 8, in addition to numerous best practices for minimizing these problems within one's own AJAX code. Incidentally, in the tip on page 225, the author states that the sample AJAX application will not run on your desktop; this apparently means that it cannot run on a local Web server. An explanation as to why, would most likely be of interest to the typical reader. Prior to getting into the details of JavaScript optimization, some tips on evaluating and choosing an AJAX library are presented.

Chapter 9 covers additional optimization techniques — aside from the Web page and code techniques covered earlier — on both the server and client side. The former category consists of parallel downloads, frequent caching, HTTP compression, delta encoding, and rewriting URIs. The latter category consists of load delaying, caching of off-site files on the server to be loaded locally, JavaScript packing, and inlining images.

The last chapter delves into Web site metrics for measuring the effectiveness of Web sites and changes made to them. The author explains some of the most popular and telling metrics, the leading Web analytics software (both Web server log analysis and JavaScript page tagging), and how they can be used for improving one's search marketing strategies and results. The chapter concludes with a detailed discussion of Web performance metrics — i.e., measures of page load times, oftentimes broken out by site, request sizes, and content type. The material clearly shows that there are a great many options for testing the optimization techniques presented in all of the earlier chapters.

There are two Web sites that have additional information about the book: O'Reilly's book page offers book descriptions, the table of contents, and confirmed and reported errata (of which there are no significant ones, as of this writing). There is a more substantial author book site, which has chapter summaries, full color figures, worksheets, all the sample code, and links to external reviews.

In general, the book achieves its goals. Aside from the occasional marketing term that will most likely puzzle the majority of readers (more on that in a moment), the writing is clear and the examples cited are applicable. The illustrations created and chosen for this book are more than adequate in quality and number, although some of the graph labels would be confusing if not clarified by the text, e.g., "Mean Fixation Duration" (page 2). Web site statistics and other data are well referenced throughout the manuscript.

On the other hand, the brief chapter summaries add nothing new to the reader's understanding, and could be disposed of without loss to the book's usefulness. Chapter summaries are more appropriate for books whose material is far more lengthy and dense, thus justifying summaries as a way to convey the highlights to the reader. As noted earlier, the case study chapters similarly add very little value, if any, to Website Optimization, and could in future editions be folded into the relevant chapters, as sidebars, or at least made much more concise and moved to the back as appendices. There is a fair bit of repetition, in the form of allusions to techniques that are covered in more detail in earlier or later chapters, and other times in the form of redundancy within chapters. For instance, the sidebar on page 156, concerning CSS and JavaScript placement, consists of a uselessly brief mention of information covered later in more detail. Trimming away all of the repeated material and the chapter summaries, and folding the case studies into the relevant chapters, would make the book leaner and a faster read. Furthermore, some of the phrases are not entirely clear in their meaning, at least to readers who are not SEO marketers. For instance, "flagged sites" (page 12) — flagged for what? Some of the phrasing is confusing, if not downright bizarre, e.g. "information scent" (page 2) and "the scent of a link" (page 122)

Admittedly, a Web site owner could learn much of this information by reading numerous articles freely available online. But most businesspeople value their time much more highly than that, and would probably find a significant amount of repetition among those articles, because they tend to "borrow" a lot from one another. This is especially true in the cases of writers who have never done SEO optimization to a Web site themselves, or run a PPC campaign.

Aside from the aforesaid weaknesses, Website Optimization is an engaging, comprehensive, and valuable resource for anyone who wishes to improve the online marketing results of their own businesses Web sites or those of the clients they support. Online business owners and Web developers unfamiliar with core SEO and site optimization techniques, are urged to read this book.

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

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

Linux Blog recommends an interview up on the O'Reilly site with Greg Kroah-Hartman, long-time Linux kernel hacker and the current Linux kernel maintainer for the USB driver core. He updates the free Linux driver program announced almost two years ago, which has really caught traction now with more than 300 developers volunteering. The interviewer begins by asking about Kroah-Hartman's claim that the Linux kernel now supports more devices than any other operating system ever has. "[One factor is] the ease of writing drivers; Linux drivers are at normally one-third smaller than Windows drivers or other operating system drivers. We have all the examples there, so it's trivial to write a new one if you have new hardware, usually because you can copy the code and go. We maintain them... forever, so the old ones don't disappear and we run on every single processor out there. I mean Linux is 80% of the world's top 500 super computers right now and we're also the number one embedded operating system today. We've got both sides of the market because it's — yeah it's pretty amazing. I don't know why, but we're doing something right."

lamaditx writes "The world of the .NET framework is taken to the next level by the release of .NET 3.5. The intended audience of this book are experienced .NET programmers. There are no sections that tell you details about C#, SQL servers or anything like that. I don't recommend this book if you never worked on a .NET project and don't know how to set up a SQL database. You should be aware that the code is written in C#. You might use one of the software code converters if you prefer Visual Basic instead. I think the code is still readable even if you do not know C#. I appreciate the fact that the authors decided to use one language only because it keeps the book smaller. The authors assume you are using Visual Studio 2008. You don't necessarily need to update to 2008 if you are working with an older edition because you can use the free Express Edition to get started." Keep reading for the rest of Adrian's review. Programming .NET 3.5 author Jesse Liberty & Alex Horovitz pages 476 publisher O'Reilly Media rating 7/10 reviewer Adrian Lambeck ISBN ISBN 978-0-596-52756-3 summary Covers all main .NET technologies found in .NET 3.5 The table of contents is available from O'Reilly — together with a chapter preview — here. The book does not come with any extras but includes the usual free 45 days access to the book on Safari.

This book covers the key technologies in .NET. There are books on each of these technologies: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), XAML, AJAX,C# and Silverlight already, but this book shows you how everything is connected with each other. As the authors note: "Our goal is to show you the 25% that you will use 85% of the time.". From my point of view this is good because I have a .NET 2.0 background and wanted to know what is new in .NET 3.5 and how things are connected.

The book is divided in 3 main parts. The first is presentation, which covers XAML, WPF and AJAX. The second describes how to take advantage of the design pattern support in .NET. The last part covers the business layer which includes LINQ, WCF, WF and CardSpace.

The first part starts with XAML. This is the eXtensible A The next main topic is using WPF which is the successor of Windows Forms. The authors explain how to connect data structures to the user interface which I consider to be one of the most important parts of using WPF. You will also find a lot of code and XAML layout descriptions.

The chapter on Silverlight was not very helpful to me. Silverlight is the competitor of Adobe Flash. Giving samples how to layout a Silverlight application is essentially the same as a WPF application thus it dives into more details of XAML. I am missing the real Silverlight message so this part did not meet my expectations.

The third technology you will learn about is AJAX which leads us away from the desktop client to a web client. The explanation how AJAX works is pretty good. The authors show you step by step how to create a todo list web-application with a database backend using ASP.NET and AJAX. Again, this does not cover all AJAX controls or ASP.NET but it shows you how the parts are interconnected and assumes that if you know how to handle one control, then you can also figure out how to handle all the others. Most web applications need some kind of access control. At this point the authors argue that it is faster to implement your own security tables instead of using the ASP.NET forms-based controls.My opinion is that you should never do something that is not correct to teach something else. There are always people who get it wrong in a way you did not anticipate. My recommendation: use the ASP.NET components and do not implement them by yourself.

The second part about the design patterns was surprising to me because I expected the common introduction to standard design pattern. The Model-View-Controller project implements the pattern for ASP.NET and allows developers to incorporate it easily. The advantage is that you get a comprehensive and easy to understand introduction how .NET supports design pattern implementation. I guess this will lead some developers from theory of design patterns to actually implementing them.

I consider the third part to be the real interesting content. It starts with LINQ which bridges object-oriented code to relational databases. You get to know the differences to SQL and also the advantages it provides by explaining new concepts. The examples are easy to understand and successfully make their point.

Windows Communication Foundation (WCF) covers the hot Service-Oriented-Architecture (SOA) topic. The authors explain what it is all about but you will need some knowledge about Web Services and XML to really get it. The introduction is rather short but more details are explained in the corresponding example.

The chapter about Windows Workflow Foundation (WF) starts with a short example how you implement a workflow without WF. After that you get to see how you do the same with WF. This way the necessity for WF become clear and you understand how to take advantage of this technology.

Card Space is the successor of Microsoft passport which was not successful as an authentication service with respect to user acceptance. This is also the key issue that decides on the success of Card Space. Maybe the improved interoperability will help. The chapter provides you with a short authenticate-yourself test and shows you how to offer Card Space authentication in your ASP.NET application.

The book is a good entry to the world of .NET 3.5 because it gives you an idea about every part and what it is good for. Maybe you do not need all of it for your job but at least you know that it exists and how it might be useful. I think it is reasonable that a comprehensive introduction to .NET 3.5 can not satisfy everybody because the range of topics is too broad. One can argue that this kind of information could also be retrieved from the net. I consider the book to be a better resource because it already summarizes the important information such that you do not drown in a flood of information.

There is also some criticism as I pointed out earlier. Maybe I am just a little picky about the details but if you print code download references into a book, they must be available. Most examples can be downloaded but the Alex Horovitz site was not reachable when I tried to access it. Another personal remark is that I do not like to see quotes from Wikipedia. Other people might think different about that so you just need to decide on your own.

I rate this book a 7. The authors scratch the surface of every topic and choose an appropriate style to explain it. You can tell that they thought about how to explain each topic on it's own and give you not just the "how" but also the "why".

Adrian Lambeck is a graduate student in "Media and Information Technologies" and worked with .NET for a few years.

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

lamaditx writes "The world of the .NET framework is taken to the next level by the release of .NET 3.5. The intended audience of this book are experienced .NET programmers. There are no sections that tell you details about C#, SQL servers or anything like that. I don't recommend this book if you never worked on a .NET project and don't know how to set up a SQL database. You should be aware that the code is written in C#. You might use one of the software code converters if you prefer Visual Basic instead. I think the code is still readable even if you do not know C#. I appreciate the fact that the authors decided to use one language only because it keeps the book smaller. The authors assume you are using Visual Studio 2008. You don't necessarily need to update to 2008 if you are working with an older edition because you can use the free Express Edition to get started." Keep reading for the rest of Adrian's review. Programming .NET 3.5 author Jesse Liberty & Alex Horovitz pages 476 publisher O'Reilly Media rating 7/10 reviewer Adrian Lambeck ISBN ISBN 978-0-596-52756-3 summary Covers all main .NET technologies found in .NET 3.5 The table of contents is available from O'Reilly — together with a chapter preview — here. The book does not come with any extras but includes the usual free 45 days access to the book on Safari.

This book covers the key technologies in .NET. There are books on each of these technologies: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), XAML, AJAX,C# and Silverlight already, but this book shows you how everything is connected with each other. As the authors note: "Our goal is to show you the 25% that you will use 85% of the time.". From my point of view this is good because I have a .NET 2.0 background and wanted to know what is new in .NET 3.5 and how things are connected.

The book is divided in 3 main parts. The first is presentation, which covers XAML, WPF and AJAX. The second describes how to take advantage of the design pattern support in .NET. The last part covers the business layer which includes LINQ, WCF, WF and CardSpace.

The first part starts with XAML. This is the eXtensible A The next main topic is using WPF which is the successor of Windows Forms. The authors explain how to connect data structures to the user interface which I consider to be one of the most important parts of using WPF. You will also find a lot of code and XAML layout descriptions.

The chapter on Silverlight was not very helpful to me. Silverlight is the competitor of Adobe Flash. Giving samples how to layout a Silverlight application is essentially the same as a WPF application thus it dives into more details of XAML. I am missing the real Silverlight message so this part did not meet my expectations.

The third technology you will learn about is AJAX which leads us away from the desktop client to a web client. The explanation how AJAX works is pretty good. The authors show you step by step how to create a todo list web-application with a database backend using ASP.NET and AJAX. Again, this does not cover all AJAX controls or ASP.NET but it shows you how the parts are interconnected and assumes that if you know how to handle one control, then you can also figure out how to handle all the others. Most web applications need some kind of access control. At this point the authors argue that it is faster to implement your own security tables instead of using the ASP.NET forms-based controls.My opinion is that you should never do something that is not correct to teach something else. There are always people who get it wrong in a way you did not anticipate. My recommendation: use the ASP.NET components and do not implement them by yourself.

The second part about the design patterns was surprising to me because I expected the common introduction to standard design pattern. The Model-View-Controller project implements the pattern for ASP.NET and allows developers to incorporate it easily. The advantage is that you get a comprehensive and easy to understand introduction how .NET supports design pattern implementation. I guess this will lead some developers from theory of design patterns to actually implementing them.

I consider the third part to be the real interesting content. It starts with LINQ which bridges object-oriented code to relational databases. You get to know the differences to SQL and also the advantages it provides by explaining new concepts. The examples are easy to understand and successfully make their point.

Windows Communication Foundation (WCF) covers the hot Service-Oriented-Architecture (SOA) topic. The authors explain what it is all about but you will need some knowledge about Web Services and XML to really get it. The introduction is rather short but more details are explained in the corresponding example.

The chapter about Windows Workflow Foundation (WF) starts with a short example how you implement a workflow without WF. After that you get to see how you do the same with WF. This way the necessity for WF become clear and you understand how to take advantage of this technology.

Card Space is the successor of Microsoft passport which was not successful as an authentication service with respect to user acceptance. This is also the key issue that decides on the success of Card Space. Maybe the improved interoperability will help. The chapter provides you with a short authenticate-yourself test and shows you how to offer Card Space authentication in your ASP.NET application.

The book is a good entry to the world of .NET 3.5 because it gives you an idea about every part and what it is good for. Maybe you do not need all of it for your job but at least you know that it exists and how it might be useful. I think it is reasonable that a comprehensive introduction to .NET 3.5 can not satisfy everybody because the range of topics is too broad. One can argue that this kind of information could also be retrieved from the net. I consider the book to be a better resource because it already summarizes the important information such that you do not drown in a flood of information.

There is also some criticism as I pointed out earlier. Maybe I am just a little picky about the details but if you print code download references into a book, they must be available. Most examples can be downloaded but the Alex Horovitz site was not reachable when I tried to access it. Another personal remark is that I do not like to see quotes from Wikipedia. Other people might think different about that so you just need to decide on your own.

I rate this book a 7. The authors scratch the surface of every topic and choose an appropriate style to explain it. You can tell that they thought about how to explain each topic on it's own and give you not just the "how" but also the "why".

Adrian Lambeck is a graduate student in "Media and Information Technologies" and worked with .NET for a few years.

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

blackbearnh wrote in with a story that's not really about the iPhone, but if your office speakerphones beep like mine does, read on: "If you own an iPhone, you may have noticed that it has a distinct and very annoying effect on clock radios, computer speakers, car radios, and just about anything else with a speaker. The folks at O'Reilly Media aren't immune, so they set out to discover just what is it about iPhones that makes them such bad RF citizens. The iPhones aren't the only bad apples in the cell phone basket and there's not much you can do about the problem. We're really in an interesting time in that there has never been so many high-powered personal transmitters just wandering loose in the world."

blackbearnh wrote in with a story that's not really about the iPhone, but if your office speakerphones beep like mine does, read on: "If you own an iPhone, you may have noticed that it has a distinct and very annoying effect on clock radios, computer speakers, car radios, and just about anything else with a speaker. The folks at O'Reilly Media aren't immune, so they set out to discover just what is it about iPhones that makes them such bad RF citizens. The iPhones aren't the only bad apples in the cell phone basket and there's not much you can do about the problem. We're really in an interesting time in that there has never been so many high-powered personal transmitters just wandering loose in the world."

BigTimOBrien writes "Jason Fried, founder of 37signals, talks about the day-to-day operations of 37signals. How does the company work, and what are the guiding principles behind the design of Basecamp and Campfire? He talks about the importance of avoiding interruptions and the relative unimportance of both physical space and mandatory meetings."

BigTimOBrien writes "Jason Fried, founder of 37signals, talks about the day-to-day operations of 37signals. How does the company work, and what are the guiding principles behind the design of Basecamp and Campfire? He talks about the importance of avoiding interruptions and the relative unimportance of both physical space and mandatory meetings."

chromatic writes "Kernel hackers Arjan van de Ven and Auke Kok showed off Linux booting in five seconds at last month's Linux Plumbers Conference. Arjan and other hackers have already improved the Linux user experience by reducing power consumption and latency. O'Reilly News interviewed him about his work on improving the Linux experience with PowerTOP, LatencyTOP, and Five-Second Boot."

Ed Pegg writes "For those that want to get their fingers stained red and blue with actual political data, resources beyond 538 and pollster can be accessed. In a blog item for Wolfram Research, Jeff Hamrick gives step by step details for how to import raw data from Mason-Dixon, Rasmussen, and Quinnipiac. Then he uses Mathematica to analyze the political data." Related: Slashdot developer Pudge presented at OSCON in July his own approach to gathering Washington-state polling data for analysis [PDF].

blackbearnh writes "The Linux Standard Base is the grand attempt to create a binary-level interface that application developers can use to create software which will run on any distribution of Linux. Theodore Tso, who helps maintain the LSB, talked recently with O'Reilly News about what the LSB does behind the scenes, how it benefits ISVs and end users, and what the greatest challenges left on the plate are. 'One of the most vexing problems has been on the desktop where the Open Source community has been developing new desktop libraries faster than we can standardize them. And also ISVs want to use those latest desktop libraries even though they may not be stable yet and in some ways that's sort of us being a victim of our own success. The LSB desktop has been getting better and better and despite all the jokes that for every year since I don't know probably five years ago, every year has been promoted as the year of the Linux desktop. The fact of the matter is the Linux desktop has been making gains very, very quickly but sometimes as a result of that some of the bleeding edge interfaces for the Linux desktop haven't been as stable as say the C library. And so it's been challenging for ISVs because they want to actually ship products that will work across a wide range of Linux distributions and this is one of the places where the Linux upstream sources haven't stabilized themselves.'"

blackbearnh writes "The Linux Standard Base is the grand attempt to create a binary-level interface that application developers can use to create software which will run on any distribution of Linux. Theodore Tso, who helps maintain the LSB, talked recently with O'Reilly News about what the LSB does behind the scenes, how it benefits ISVs and end users, and what the greatest challenges left on the plate are. 'One of the most vexing problems has been on the desktop where the Open Source community has been developing new desktop libraries faster than we can standardize them. And also ISVs want to use those latest desktop libraries even though they may not be stable yet and in some ways that's sort of us being a victim of our own success. The LSB desktop has been getting better and better and despite all the jokes that for every year since I don't know probably five years ago, every year has been promoted as the year of the Linux desktop. The fact of the matter is the Linux desktop has been making gains very, very quickly but sometimes as a result of that some of the bleeding edge interfaces for the Linux desktop haven't been as stable as say the C library. And so it's been challenging for ISVs because they want to actually ship products that will work across a wide range of Linux distributions and this is one of the places where the Linux upstream sources haven't stabilized themselves.'"

DaveyJJ sends news of yet another rejection of an iPhone app by Apple, with perhaps a chilling twist for potential developers of productivity or utility apps. John Gruber of Daring Fireball writes: "Let's be clear: forbidding 'duplication of functionality' is forbidding competition. The point of competition is to do the same thing, but better." Paul Kafasis (co-founder of Rogue Amoeba Software) makes the point that this action by Apple will scare talented developers away from the iPhone platform. And Dave Weiner argues that the iPhone isn't a "platform" at all: "The idea that it's a platform should mean no individual or company has the power to turn you off."

blackbearnh writes "It may make you feel very, very old, but the Macintosh will be turning 25 in January. As we approach this momentous anniversary, O'Reilly News had a talk with Andy Hertzfeld, one of the original Macintosh designers, about the long and storied history of the Mac. Hertzfeld, who tells the story of the Mac in his book A Revolution in the Valley, shares his thoughts about how the Mac has aged over time, how life might have been different if Steve Jobs had stayed on at Apple, and the differences between working for Apple, and for Google (his current employer.)" Read on below for a bit of what Hertzfeld had to say.

"They're very similar in certain ways — essentially both Apple and Google want to rewrite the rulebook; they don't want to do things in conventional ways. They want to come up with a better way — for everything; that's not even just the technology but the work processes, the work environment, everything has to be unique and better, so they're very similar in that way. One of the ways that they're different has to do with essentially trust of employees. Apple is very secretive within the company; people working on Macs don't know anything about the new iPods, et cetera. Google is extremely open within the company; once you're a Google employee you have access to just about every piece of information there is."

blackbearnh writes "It may make you feel very, very old, but the Macintosh will be turning 25 in January. As we approach this momentous anniversary, O'Reilly News had a talk with Andy Hertzfeld, one of the original Macintosh designers, about the long and storied history of the Mac. Hertzfeld, who tells the story of the Mac in his book A Revolution in the Valley, shares his thoughts about how the Mac has aged over time, how life might have been different if Steve Jobs had stayed on at Apple, and the differences between working for Apple, and for Google (his current employer.)" Read on below for a bit of what Hertzfeld had to say.

"They're very similar in certain ways — essentially both Apple and Google want to rewrite the rulebook; they don't want to do things in conventional ways. They want to come up with a better way — for everything; that's not even just the technology but the work processes, the work environment, everything has to be unique and better, so they're very similar in that way. One of the ways that they're different has to do with essentially trust of employees. Apple is very secretive within the company; people working on Macs don't know anything about the new iPods, et cetera. Google is extremely open within the company; once you're a Google employee you have access to just about every piece of information there is."

blackbearnh writes "It may make you feel very, very old, but the Macintosh will be turning 25 in January. As we approach this momentous anniversary, O'Reilly News had a talk with Andy Hertzfeld, one of the original Macintosh designers, about the long and storied history of the Mac. Hertzfeld, who tells the story of the Mac in his book A Revolution in the Valley, shares his thoughts about how the Mac has aged over time, how life might have been different if Steve Jobs had stayed on at Apple, and the differences between working for Apple, and for Google (his current employer.)" Read on below for a bit of what Hertzfeld had to say.

"They're very similar in certain ways — essentially both Apple and Google want to rewrite the rulebook; they don't want to do things in conventional ways. They want to come up with a better way — for everything; that's not even just the technology but the work processes, the work environment, everything has to be unique and better, so they're very similar in that way. One of the ways that they're different has to do with essentially trust of employees. Apple is very secretive within the company; people working on Macs don't know anything about the new iPods, et cetera. Google is extremely open within the company; once you're a Google employee you have access to just about every piece of information there is."

Schneed Tweedly writes "William Patry is one of the leading scholars in the world on copyright law. For a long time he maintained a blog, "Patry on Copyright," that discussed new cases as they came out. A few days ago, though, he shut down his blog because 'the Current State of Copyright Law is too depressing.' O'Reilly has a long post up on their news site discussing Patry's retirement from blogging and giving a history of copyright that explains how we got where we are."

securitas writes "Almost a decade after the Internet bubble collapsed, the New York Times reports on the revival of the Silicon Alley technology social scene — with a twist. It's now about substance. Gone are the "glitzy club ... minor celebrities, go-go dancers, an open bar and pricey giveaways" in favor of unconferences, Ignite, Pecha Kucha, ideas and 'a night life that involves actually talking to creative people doing exciting things.' Most major cities have a geek social scene like the NYC Soldering Championship [video link] featured in the article." Not surprisingly (for anyone who reads O'Reilly's Make magazine), Bre Pettis is one of the event organizers mentioned.

OSCON isn't just a gathering for talks on topics like Creating Location-aware Web 2.0 Applications on an Open Source Geospatial Platform and fightin' words from the stage; it's also an excuse for some interesting social gatherings, like this year's Community Choice awards (organized and sponsored by the corporate overlords at SourceForge, as you might recall, and with Slashdot's own special category), at which, among other festive activities, attendees were offered the chance to get open-source-related tattoos. There are shots of some of these up on the SourceForge Community pages, and — with some overlap — even more in this set at Flickr. (My pasty bicep^h^h^h^h^h shoulder is the one now adorned with a circled head of a happy Tux ala IBM; I was expecting it to hurt more than it actually did.) Anyone with techie tattoos, please disclose below.

mjasay writes "At OSCON this year, MySQL's Brian Aker made this bold statement: 'Microsoft is irrelevant ... We're more worried about Apple.' The Free Software Foundation appears to have caught the hint, and has turned its attention to all-things-Apple with a 'denial of service' attack on the Apple Genius Bars. The idea is to completely book all Genius Bars and then ask the 'geniuses,' over and over again, a few questions about Apple's proprietary ways (while, apparently, real customers with support issues are left to flounder). Lost in this anti-Apple fervor, however, is the Free Software Foundation's complete and conscious failure to protect the web. Richard Stallman has long felt that software that doesn't sit on his desktop doesn't affect his freedom, but isn't the opposite true? Why is the FSF focused on Apple when the bigger concern should be Google, Yahoo!, Amazon, and other web players, a point made by Tim O'Reilly recently at OSCON?" Defective by Design is just one of many FSF projects, remember; it hardly seems fair to say that the FSF has been ignoring the implications of software as a service.

mjasay writes "At OSCON this year, MySQL's Brian Aker made this bold statement: 'Microsoft is irrelevant ... We're more worried about Apple.' The Free Software Foundation appears to have caught the hint, and has turned its attention to all-things-Apple with a 'denial of service' attack on the Apple Genius Bars. The idea is to completely book all Genius Bars and then ask the 'geniuses,' over and over again, a few questions about Apple's proprietary ways (while, apparently, real customers with support issues are left to flounder). Lost in this anti-Apple fervor, however, is the Free Software Foundation's complete and conscious failure to protect the web. Richard Stallman has long felt that software that doesn't sit on his desktop doesn't affect his freedom, but isn't the opposite true? Why is the FSF focused on Apple when the bigger concern should be Google, Yahoo!, Amazon, and other web players, a point made by Tim O'Reilly recently at OSCON?" Defective by Design is just one of many FSF projects, remember; it hardly seems fair to say that the FSF has been ignoring the implications of software as a service.