Slashdot Mirror

r3lody writes "An extremely large amount of the information we get on a daily basis comes from what we see. Imagery is therefore very important to those who want to communicate with us. When computers had advanced enough to be able to process images in a digital fashion, the market opened up for programs that could manipulate them in many ways. While many professionals would opt for the paid programs, there is a free alternative: GIMP (Gnu Image Manipulation Program). The only stumbling block is learning how to use it properly. That is where Beginning GIMP: From Novice to Professional, Second Edition by Akkana Peck comes in." Read below for the rest of Ray's review. Beginning GIMP: From Novice to Professional, Second Edition author Akkana Peck pages 584 publisher Apress rating 8/10 reviewer Ray Lodato ISBN 1430210702 summary An easy-to-read, fairly complete introduction to image processing with GIMP I first attempted to use GIMP to fix a photograph or two of mine, but was quickly bogged down in the many options available in the program. That is why I was happy to get my hands on a copy of Beginning GIMP. The book is based mainly on GIMP 2.4, but the author included a preview of GIMP 2.6 in Appendix D. When I downloaded the latest verson of GIMP from gimp.org, I received GIMP 2.6.0. So I used the PortableApps version of GIMP (2.4.6) on Windows XP while reviewing the book and found only minor variations from the text.

One thing that strikes you as you open the book is the extensive use of color. Most texts are black-and-white throughout, but here you are presented with a pleasantly colorful tome. To follow the examples as best as I could, I downloaded the images available on the gimpbook.com web site. Although the images are supposed to be for the 2nd edition, several of those shown in the text for demonstrations purposes are not included. It appears that the images for the tools new to GIMP 2.4 are missing from the web site. This is surprising, since the 1st edition of the book covered version 2.4, so you would expect the images to be there.

The book begins by giving the reader a brief tour of the three main windows of GIMP: the Toolbox window, the Layer/Channels/Path/Undo window, and the Image window. Some basic navigation is presented, along with tear-off menus and how to modify tool placement. It concludes with a simple project layering a small image onto a larger one was given. Unfortunately, the files supplied from the web site did not include the PNG file used in the text, so it's difficult to reproduce the picture as shown. I later found the missing image in a GIMP-format file called wilber.xcf.gz. Unfortunately, xcf files are not discussed until the next chapter.

After the simple introduction, the author, Akkana Peck, gets into the most common adjustments a beginning user might need: re-sizing, cropping, rotating, brightening and darkening, and fixing red-eye. Each manipulation is presented with careful step-by-step instructions. I was able to match the pictures shown in the book, providing me with a level of comfort that I was learning the right way to fix photos.

One of the most common and useful methods of altering photographs uses the concept of layers. Layers act like cinematic cels, being mostly transparent with some opaque portions to lay on top of other layers. Chapter 3 gives a clear description of how to use layers to make changes. Two sample projects use layers to add text and another image to an existing photo, and to create an animated GIF using a series of layers for each frame of the animation. While I found minor differences between the text and the version of GIMP I used, I had no real problem understanding how the concept is applied.

You will probably need to do some freehand drawing from time to time, and chapter 4 covers the tools you'll need. While these tools are familiar to anyone who has used a basic painting program like Microsoft Paint, there are enough differences in how they are applied to warrant their own chapter. After creating some basic shapes (rectangle and circles), outlining and filling them, the author explores various fills and patterns. The chapter ends with a tutorial of creating a tree in a planter box, using just the drawing tools.

Every tool you use in GIMP works on the current selection. Knowing how to select just the parts of the image you want affected is important to getting the results you want. The author devotes an entire chapter to the numerous ways to select areas, add to or subtract from the selections, and fine-tuning them to only touch the parts you want touched. Basic rectangle, ellipse, and free-hand selections are followed by more sophisticated methods including the intelligent scissors and SIOX (Simple Interactive Object Extraction). The book also shows how to save selections as channels, so you can return to them in future editing sessions.

Sometimes, however, all you really need to do is a little touch-up on a photograph. Is someone's face in shadow or too much sun? Did you wish to get rid of some little irritating extra in a photo? Maybe you just wanted to draw attention to one subject and blur out the rest. Chapter 6 provides the information on how to make these basic adjustments. Darkroom techniques called dodging and burning provide minor adjustments to brightness, while cloning and healing can completely eradicate unwanted portions of the image. To draw attention to portions of the picture, you can enhance it using the blur and sharpen tools.

In addition to simple adjustments, GIMP offers a plethora of various tools to modify or create images. Under the Filters menu, you will find a large selection of tools. When I first looked, I felt that there were so many, who would need all of them? In the Filters and Effects chapter, Akkana Peck goes through them all, showing how they can be used to enhance your image. Because there are so many, she does not provide examples of each effect, but each one is described and you are encouraged to play. Remember, Undo is your friend here!

Chapter 8 delves into a very important aspect of your photos and drawings — the colors. First, the concepts of the RGB (Red-Green-Blue) and CMY (Cyan-Magenta-Yellow) colorspaces are described, followed by the HSV (Hue-Saturation-Value) space. A lot of time is used reviewing how these different colorspaces are used, and how they can be manipulated. The tools for breaking the image into its component layers, and demonstrations on how manipulating them can enhance your photo follow. The chapter concludes with some discussion on color profiles.

Now that you've learned quite a few niceties of GIMP, you need to learn more advanced techniques. The next two chapters go into more detail about drawing and compositing. The chapter on Advanced Drawing covers three main topics: mask and layer modes, realism using perspective and shading, and making new brushes, patterns and gradients. The Layer Mode section is the most interesting, showing how blending layers using various modes other than simple overlays can produce interesting effects. There are a number of examples, all easily followed and replicated. Once you've got a basic understanding of the advanced drawing techniques, it's time to put them to use on photographs. The chapter on Advanced Compositing shows how to use layer modes to play with images to improve their looks. You can brighten images, improve contrast, create eerie landscapes, fix noisy photos, and create panoramas, all using various layer modes. Many examples are shown, so you can get a good feel for the technique.

GIMP plug-ins provide automated tasks for the user. In fact, a number of GIMP's tools are provided by plug-ins. A variety of languages is supported. Plug-in scripts can be written in Scheme (the default — always installed), Python, and Perl (if available on your computer). If you need greater speed, you can write a plug-in in C. Chapter 11 uses the sphere plug-in as an example. Xtns — Misc — Sphere creates a sphere on a solid background. Akkana explains how to modify the script to provide a transparent background. A full discussion of the programming of the original script follows. Each step is carefully explained so only a minimal amount of programming background is needed to understand the concepts. Finally, examples in Python, Perl and C round out the chapter. Also included are explanations of how to find plug-ins and help on callable routines.

Unfortunately, there is so much to GIMP that one medium-sized book cannot contain it all. There is a potpourri of topics in the final chapter, including printing, scanning, setting preferences and the configuration files. The chapter ends with information on where to go for more help, source code, and images.

The appendices offer information on how to get and install GIMP, how to install it on older systems, and how to build it from source. Naturally, GIMP is always evolving, and Appendix D offers a list of enhancements in GIMP 2.6 that were not incorporated into the main text.

Over the course of reading the book, I had very little trouble reproducing the examples as demonstrated. I must admit that, despite the book's subtitle: From Novice to Professional, I am now at best an intermediate user. The depth of the capabilities available within GIMP is much deeper than the author could provide in the text. At almost 600 pages, this book is just about the right size, and provides the right amount of instruction for most people. The Additional Topics chapter provides information and links for further study and training, for those so inclined. If you are a beginner to image manipulation, and want to get fairly proficient with GIMP, then definitely get Beginning GIMP. It's not leaving my desk any time soon.

You can purchase Beginning GIMP: From Novice to Professional, Second Edition from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

r3lody writes "An extremely large amount of the information we get on a daily basis comes from what we see. Imagery is therefore very important to those who want to communicate with us. When computers had advanced enough to be able to process images in a digital fashion, the market opened up for programs that could manipulate them in many ways. While many professionals would opt for the paid programs, there is a free alternative: GIMP (Gnu Image Manipulation Program). The only stumbling block is learning how to use it properly. That is where Beginning GIMP: From Novice to Professional, Second Edition by Akkana Peck comes in." Read below for the rest of Ray's review. Beginning GIMP: From Novice to Professional, Second Edition author Akkana Peck pages 584 publisher Apress rating 8/10 reviewer Ray Lodato ISBN 1430210702 summary An easy-to-read, fairly complete introduction to image processing with GIMP I first attempted to use GIMP to fix a photograph or two of mine, but was quickly bogged down in the many options available in the program. That is why I was happy to get my hands on a copy of Beginning GIMP. The book is based mainly on GIMP 2.4, but the author included a preview of GIMP 2.6 in Appendix D. When I downloaded the latest verson of GIMP from gimp.org, I received GIMP 2.6.0. So I used the PortableApps version of GIMP (2.4.6) on Windows XP while reviewing the book and found only minor variations from the text.

One thing that strikes you as you open the book is the extensive use of color. Most texts are black-and-white throughout, but here you are presented with a pleasantly colorful tome. To follow the examples as best as I could, I downloaded the images available on the gimpbook.com web site. Although the images are supposed to be for the 2nd edition, several of those shown in the text for demonstrations purposes are not included. It appears that the images for the tools new to GIMP 2.4 are missing from the web site. This is surprising, since the 1st edition of the book covered version 2.4, so you would expect the images to be there.

The book begins by giving the reader a brief tour of the three main windows of GIMP: the Toolbox window, the Layer/Channels/Path/Undo window, and the Image window. Some basic navigation is presented, along with tear-off menus and how to modify tool placement. It concludes with a simple project layering a small image onto a larger one was given. Unfortunately, the files supplied from the web site did not include the PNG file used in the text, so it's difficult to reproduce the picture as shown. I later found the missing image in a GIMP-format file called wilber.xcf.gz. Unfortunately, xcf files are not discussed until the next chapter.

After the simple introduction, the author, Akkana Peck, gets into the most common adjustments a beginning user might need: re-sizing, cropping, rotating, brightening and darkening, and fixing red-eye. Each manipulation is presented with careful step-by-step instructions. I was able to match the pictures shown in the book, providing me with a level of comfort that I was learning the right way to fix photos.

One of the most common and useful methods of altering photographs uses the concept of layers. Layers act like cinematic cels, being mostly transparent with some opaque portions to lay on top of other layers. Chapter 3 gives a clear description of how to use layers to make changes. Two sample projects use layers to add text and another image to an existing photo, and to create an animated GIF using a series of layers for each frame of the animation. While I found minor differences between the text and the version of GIMP I used, I had no real problem understanding how the concept is applied.

You will probably need to do some freehand drawing from time to time, and chapter 4 covers the tools you'll need. While these tools are familiar to anyone who has used a basic painting program like Microsoft Paint, there are enough differences in how they are applied to warrant their own chapter. After creating some basic shapes (rectangle and circles), outlining and filling them, the author explores various fills and patterns. The chapter ends with a tutorial of creating a tree in a planter box, using just the drawing tools.

Every tool you use in GIMP works on the current selection. Knowing how to select just the parts of the image you want affected is important to getting the results you want. The author devotes an entire chapter to the numerous ways to select areas, add to or subtract from the selections, and fine-tuning them to only touch the parts you want touched. Basic rectangle, ellipse, and free-hand selections are followed by more sophisticated methods including the intelligent scissors and SIOX (Simple Interactive Object Extraction). The book also shows how to save selections as channels, so you can return to them in future editing sessions.

Sometimes, however, all you really need to do is a little touch-up on a photograph. Is someone's face in shadow or too much sun? Did you wish to get rid of some little irritating extra in a photo? Maybe you just wanted to draw attention to one subject and blur out the rest. Chapter 6 provides the information on how to make these basic adjustments. Darkroom techniques called dodging and burning provide minor adjustments to brightness, while cloning and healing can completely eradicate unwanted portions of the image. To draw attention to portions of the picture, you can enhance it using the blur and sharpen tools.

In addition to simple adjustments, GIMP offers a plethora of various tools to modify or create images. Under the Filters menu, you will find a large selection of tools. When I first looked, I felt that there were so many, who would need all of them? In the Filters and Effects chapter, Akkana Peck goes through them all, showing how they can be used to enhance your image. Because there are so many, she does not provide examples of each effect, but each one is described and you are encouraged to play. Remember, Undo is your friend here!

Chapter 8 delves into a very important aspect of your photos and drawings — the colors. First, the concepts of the RGB (Red-Green-Blue) and CMY (Cyan-Magenta-Yellow) colorspaces are described, followed by the HSV (Hue-Saturation-Value) space. A lot of time is used reviewing how these different colorspaces are used, and how they can be manipulated. The tools for breaking the image into its component layers, and demonstrations on how manipulating them can enhance your photo follow. The chapter concludes with some discussion on color profiles.

Now that you've learned quite a few niceties of GIMP, you need to learn more advanced techniques. The next two chapters go into more detail about drawing and compositing. The chapter on Advanced Drawing covers three main topics: mask and layer modes, realism using perspective and shading, and making new brushes, patterns and gradients. The Layer Mode section is the most interesting, showing how blending layers using various modes other than simple overlays can produce interesting effects. There are a number of examples, all easily followed and replicated. Once you've got a basic understanding of the advanced drawing techniques, it's time to put them to use on photographs. The chapter on Advanced Compositing shows how to use layer modes to play with images to improve their looks. You can brighten images, improve contrast, create eerie landscapes, fix noisy photos, and create panoramas, all using various layer modes. Many examples are shown, so you can get a good feel for the technique.

GIMP plug-ins provide automated tasks for the user. In fact, a number of GIMP's tools are provided by plug-ins. A variety of languages is supported. Plug-in scripts can be written in Scheme (the default — always installed), Python, and Perl (if available on your computer). If you need greater speed, you can write a plug-in in C. Chapter 11 uses the sphere plug-in as an example. Xtns — Misc — Sphere creates a sphere on a solid background. Akkana explains how to modify the script to provide a transparent background. A full discussion of the programming of the original script follows. Each step is carefully explained so only a minimal amount of programming background is needed to understand the concepts. Finally, examples in Python, Perl and C round out the chapter. Also included are explanations of how to find plug-ins and help on callable routines.

Unfortunately, there is so much to GIMP that one medium-sized book cannot contain it all. There is a potpourri of topics in the final chapter, including printing, scanning, setting preferences and the configuration files. The chapter ends with information on where to go for more help, source code, and images.

The appendices offer information on how to get and install GIMP, how to install it on older systems, and how to build it from source. Naturally, GIMP is always evolving, and Appendix D offers a list of enhancements in GIMP 2.6 that were not incorporated into the main text.

Over the course of reading the book, I had very little trouble reproducing the examples as demonstrated. I must admit that, despite the book's subtitle: From Novice to Professional, I am now at best an intermediate user. The depth of the capabilities available within GIMP is much deeper than the author could provide in the text. At almost 600 pages, this book is just about the right size, and provides the right amount of instruction for most people. The Additional Topics chapter provides information and links for further study and training, for those so inclined. If you are a beginner to image manipulation, and want to get fairly proficient with GIMP, then definitely get Beginning GIMP. It's not leaving my desk any time soon.

You can purchase Beginning GIMP: From Novice to Professional, Second Edition from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

The NYTimes is running a tip-of-the-iceberg story about how the age of Google is resulting in more mistrials as the traditional rules of evidence, honed over many centuries, collide with the always-on Internet. Especially when jurors carry the always-on Internet in their pockets. (We discussed one such case recently.) "The use of BlackBerrys and iPhones by jurors gathering and sending out information about cases is wreaking havoc on trials around the country, upending deliberations and infuriating judges. ... Jurors are not supposed to seek information outside of the courtroom. They are required to reach a verdict based on only the facts the judge has decided are admissible, and they are not supposed to see evidence that has been excluded as prejudicial. But now, using their cellphones, they can look up the name of a defendant on the Web or examine an intersection using Google Maps, violating the legal system's complex rules of evidence."

I Don't Believe in Imaginary Property writes "Discovery Communications, the parent company of the Discovery Channel, is alleging that Amazon's Kindle e-book reader infringes upon their patent for DRM-encumbered e-books (Discovery's complaint, PDF). The patent in question was filed back in 1999 and issued in 2007 — coincidentally one day after Kindle 1.0 went on the market — and has claims for DRM implemented with a great many particular symmetric key ciphers and key exchange algorithms, (the patent has 171 claims). Unlike most software patents, this one goes into quite a lot of detail about how the encryption is to be performed. But it will still be interesting to see if it can pass the 'machine or transformation' test now that In Re Bilski is being accepted as precedent. After all, it seems like all of these encryption and e-book distribution schemes could be run on a general-purpose PC, so is the 'invention' actually tied to a 'particular machine or apparatus' just because an e-book 'viewer' (not to mention 'home system', 'library', and 'kiosk') happens to be specified in the patent's claims? Or can the encryption of an e-book be claimed as some kind of 'transformation' when the law in that area is especially murky — when no one knows how In Re Bilski may affect the precedent of In Re Schrader?"

Not long ago, we discussed the realities of selling a game on the iPhone App Store. Now, spidweb sends in his experiences with a realistic level of success as an independent PC game developer. He writes "There is a lot of excitement about casual gaming and Indie game development these days, but there's also very little public information about how many games actually get sold, or the sort of income one can reasonably expect in this line of work. We've released full sales figures for a recent product to illustrate what sort of earnings can be generated by a quality niche product that isn't a massive hit. From the post: 'I am not the first Indie developer to reveal this sort of information. However, most public sales figures come from projects that were either blockbusters or disasters. Our games have never landed in either pool. I have been doing this for a living for almost fifteen years.'"

Ask Stenum writes "Rock Paper Shotgun has an interesting write-up about how Unreal Tournament 3 has risen from the dead after Epic Games patched it, made a deal with Valve to put it on Steam and making it available for free for a weekend. It's interesting to see how a multiplayer game that's almost one and a half years old suddenly has become what it never could be; a game with multiple players. What other (maybe older?) online multiplayer games would you like to see make a comeback?" UT3's resurgence was mentioned here briefly last week as part of our discussion on the future of game pricing.

cpudney writes "The Sydney Morning Herald reports that the Australian Communications and Media Authority (ACMA) has added several Wikileaks pages to its controversial blacklist. The blacklisted pages contain Denmark's list of banned websites. Simply linking to addresses in ACMA's blacklist attracts an $11,000 per-day fine as the hosts of the popular Australian broadband forum, Whirlpool, discovered last week when they published a forum post that linked to an anti-abortion web-site recently added to ACMA's blacklist. The blacklist is secret, immune to FOI requests and forms the basis of the Australian government's proposed mandatory ISP-level Internet censorship legislation. Wikileaks' response to notification of the blacklisting states: 'The first rule of censorship is that you cannot talk about censorship.'" So Australians aren't allowed to see what it is that the Danes aren't allowed to see?

Saul J writes with an update to the patent lawsuit that was filed by Fenner Investments back in 2007 against Nintendo and Microsoft. The suit alleged that the two companies had infringed upon a patent for a joystick port interface. The trial was set to begin today, but now Judge Leonard Davis of the US District Court in Tyler, Texas has ruled that there is no need for a jury trial. One of Nintendo's lawyers said, "Nintendo has a long history of developing innovative products while respecting the intellectual property rights of others. We also vigorously defend patent lawsuits when we firmly believe that we have not infringed another party's patent, despite the risks that this policy entails."

An anonymous reader writes "BoingBoing Gadgets has updated their story from yesterday on DRM contained in the new iPod Shuffle. (We also discussed this rumor last week.) It's a false alarm. There is a chip in the headphone controls but it is just an encoder chip. There is no DRM and no reason to believe that third party headphones wouldn't work with the new Shuffle. (Apple would still prefer you to license the encoder under the Made for iPod program, but with no DRM, there is no DMCA risk to a manufacturer reverse engineering it.) The money quote: 'For the record, we do not believe that the new iPod headphones with in-line remote use DRM that affects audio playback in any way.'"

An anonymous reader writes "Remember all those undersea cables breaking? PopSci.com introduces John Rennie, who '... has braved the towering waves of the North Atlantic Ocean to keep your e-mail coming to you. As chief submersible engineer aboard the Wave Sentinel, part of the fleet operated by UK-based undersea installation and maintenance firm Global Marine Systems, Rennie — a congenial, 6'4", 57-year-old Scotsman — patrols the seas, dispatching a remotely operated submarine deep below the surface to repair undersea cables.' The article goes on to outline the physical infrastructure of the Internet, including some of its points of vulnerability."

An anonymous reader writes "Remember all those undersea cables breaking? PopSci.com introduces John Rennie, who '... has braved the towering waves of the North Atlantic Ocean to keep your e-mail coming to you. As chief submersible engineer aboard the Wave Sentinel, part of the fleet operated by UK-based undersea installation and maintenance firm Global Marine Systems, Rennie — a congenial, 6'4", 57-year-old Scotsman — patrols the seas, dispatching a remotely operated submarine deep below the surface to repair undersea cables.' The article goes on to outline the physical infrastructure of the Internet, including some of its points of vulnerability."

An anonymous reader writes "Remember all those undersea cables breaking? PopSci.com introduces John Rennie, who '... has braved the towering waves of the North Atlantic Ocean to keep your e-mail coming to you. As chief submersible engineer aboard the Wave Sentinel, part of the fleet operated by UK-based undersea installation and maintenance firm Global Marine Systems, Rennie — a congenial, 6'4", 57-year-old Scotsman — patrols the seas, dispatching a remotely operated submarine deep below the surface to repair undersea cables.' The article goes on to outline the physical infrastructure of the Internet, including some of its points of vulnerability."

stoolpigeon writes "Web applications are all the rage, web applications that function within the context of social networking sites doubly so. I think it is safe to say that pretty much anyone looking to garner a large audience on the web, for financial or any other reasons, has to be considering how they can reach people on sites like Facebook, or all those users out there accessing the web via their iPhones. Sun Microsystems has entered this arena by providing a set of web-based development tools and a platform on which to host the resulting products that is now in beta and named Zembly. And while Zembly has not been open to the public for all that long, two of Zemblys architects with the help of two writers have published a new cookbook for the aspiring Zembly developer, Assemble the Social Web with Zembly." Read below for the rest of JR's review. Assemble the Social Web with Zembly author Gail Anderson and Paul Anderson with Todd Fast and Chris Webster pages 385 publisher Prentice Hall rating 8/10 reviewer JR Peck ISBN 978-0-13-714431-0 summary Let's Make a Social Application. Right Here. Right Now. Together. Zembly is relatively new and the name doesn't offer any insight into just what it is, so before I get to the book itself, I'll explain a little about just what Zembly is. It is a Sun project. In their promotional material on the site they claim, "Over two decades ago, Sun's motto, 'The Network is the Computer', foreshadowed the advent of today's cloud computing movement.We like to say that zembly is the development environment for Sun's bold vision ..." So Zembly is an on-line development environment. But more than just being an on-line editor, it is development in a social context aimed at social tools. The code written by one Zembly user is available to any other user.

Along with providing a social development environment, Zembly also provides the platform and resources where the applications developed there will live. To put it in literal terms the framework is comprised of Solaris, Java, Glassfish, and MySQL. It operates via Sun's Network.com cloud-computing business. That framework supports the use of HTML, CSS, JavaScript, FBML, and FBJS. There are templates in place to develop applications for several popular social networking sites and there will be more as users add them.

Assemble the Social Web with Zembly is an introduction to all this and serves primarily as a cookbook to help the reader get their head around how all the pieces work together, giving them a jump start into the process. As Zembly is all about collaboration it seems appropriate that this book is the product of four authors. Gail Anderson and Paul Anderson are experienced authors, with a number of published tech books between them. Todd Fast is the architect and CTO of Zembly. Chris Webster is another Sun employee and the Technical lead for Zembly and also a published author himself.

The book covers an overview of Zembly, a chapter on how to use the tool set and then moves through a series of chapters that provide examples of building widgets and services for Flickr, Zillow, Facebook, Dapper, and web apps for the iPhone. There is also a widget section that makes use of WeatherBug, Google Maps and Yahoo! Pipes. The results can be published as applications within those sites or embedded into other sites. I see the real potential for Zembly in places like Dapper and Pipes, where Zembly becomes an endpoint for those types of services that can consume almost anything. The usefulness of Zembly comes in allowing developers to integrate that into the social sites and the scalable hosting is already built right in.

The book is well organized and black & white illustrations are put to good use in making directions clear. The index is thorough. The authors do not assume a lot of prior knowledge on the part of the reader in regard to how the various social networks operate. This did mean at times I had to plow explanations of things that really didn't have anything to do with Zembly. The information on what Facebook applications are and what they do is a good example. This was a little annoying but fortunately these sections were short. I found the writing to be clear and to the point. The authors do not try to be hip or cool and focus on content.

To really get the most out of the book a reader should be familiar with JavaScript, html and css. It wouldn't hurt to also understand RESTful web services. Once the first two chapters explaining Zembly are over, this really is a cook-book, or set of examples/tutorials rather than instruction on how to code or do markup. The experienced developer could probably slide by even if they were not working regularly with these technologies. Someone who has never written a bit of code may want to spend some time building some familiarity with javascript before they tack this book. Zembly itself has some quick tutorials that require almost no knowledge of programming. I watched a graphic art guy at work throw together a Facebook widget/app in about 10 minutes using Zembly.

Zembly is still in what has become the ubiquitous beta state for on-line applications. And as it is under active development this book probably has a very short shelf-life. It wont be all that long before the platform moves along and leaves it behind. In an effort to shore up against that inevitability all the code and resources for the book are stored in Zembly. If changes are made today, tomorrows reader will be able to work with the updated structures. The book itself is also available in traditional ebook formats and through Safari.

One of the nicer things about the Zembly approach is that it removes the barrier of hosting costs to participate in this space. In turn the developer surrenders up their work to be used by others. This may be problematic for those who would rather keep all their code to themselves, but fits in-line nicely with the fact that the entire stack is built on FOSS products. Of course, once again the beta status means that this free ride is not something that is guaranteed for perpetuity. I'm guessing that at some point, this type of central hosting is going to necessitate an attempt by Sun to generate some income from the service.

Getting in on the front end of a technology can often be rather difficult. The Sun folks seem to be ahead of the curve on making it easier for people to participate with Zembly. There are excellent tutorials and documentation on the site itself. For those who want to take it a step further, there is this book with a wealth of examples and explanations that will really accelerate the learning process. I'm not sure if Zembly will become the next big thing or not, but anyone who wants to gamble that it will, here is a chance to make the most of the ride.

You can purchase Assemble the Social Web with Zembly from amazon.com. Slashdot welcomes readers' book reviews — to see your own review here, read the book review guidelines, then visit the submission page.

stoolpigeon writes "Web applications are all the rage, web applications that function within the context of social networking sites doubly so. I think it is safe to say that pretty much anyone looking to garner a large audience on the web, for financial or any other reasons, has to be considering how they can reach people on sites like Facebook, or all those users out there accessing the web via their iPhones. Sun Microsystems has entered this arena by providing a set of web-based development tools and a platform on which to host the resulting products that is now in beta and named Zembly. And while Zembly has not been open to the public for all that long, two of Zemblys architects with the help of two writers have published a new cookbook for the aspiring Zembly developer, Assemble the Social Web with Zembly." Read below for the rest of JR's review. Assemble the Social Web with Zembly author Gail Anderson and Paul Anderson with Todd Fast and Chris Webster pages 385 publisher Prentice Hall rating 8/10 reviewer JR Peck ISBN 978-0-13-714431-0 summary Let's Make a Social Application. Right Here. Right Now. Together. Zembly is relatively new and the name doesn't offer any insight into just what it is, so before I get to the book itself, I'll explain a little about just what Zembly is. It is a Sun project. In their promotional material on the site they claim, "Over two decades ago, Sun's motto, 'The Network is the Computer', foreshadowed the advent of today's cloud computing movement.We like to say that zembly is the development environment for Sun's bold vision ..." So Zembly is an on-line development environment. But more than just being an on-line editor, it is development in a social context aimed at social tools. The code written by one Zembly user is available to any other user.

Along with providing a social development environment, Zembly also provides the platform and resources where the applications developed there will live. To put it in literal terms the framework is comprised of Solaris, Java, Glassfish, and MySQL. It operates via Sun's Network.com cloud-computing business. That framework supports the use of HTML, CSS, JavaScript, FBML, and FBJS. There are templates in place to develop applications for several popular social networking sites and there will be more as users add them.

Assemble the Social Web with Zembly is an introduction to all this and serves primarily as a cookbook to help the reader get their head around how all the pieces work together, giving them a jump start into the process. As Zembly is all about collaboration it seems appropriate that this book is the product of four authors. Gail Anderson and Paul Anderson are experienced authors, with a number of published tech books between them. Todd Fast is the architect and CTO of Zembly. Chris Webster is another Sun employee and the Technical lead for Zembly and also a published author himself.

The book covers an overview of Zembly, a chapter on how to use the tool set and then moves through a series of chapters that provide examples of building widgets and services for Flickr, Zillow, Facebook, Dapper, and web apps for the iPhone. There is also a widget section that makes use of WeatherBug, Google Maps and Yahoo! Pipes. The results can be published as applications within those sites or embedded into other sites. I see the real potential for Zembly in places like Dapper and Pipes, where Zembly becomes an endpoint for those types of services that can consume almost anything. The usefulness of Zembly comes in allowing developers to integrate that into the social sites and the scalable hosting is already built right in.

The book is well organized and black & white illustrations are put to good use in making directions clear. The index is thorough. The authors do not assume a lot of prior knowledge on the part of the reader in regard to how the various social networks operate. This did mean at times I had to plow explanations of things that really didn't have anything to do with Zembly. The information on what Facebook applications are and what they do is a good example. This was a little annoying but fortunately these sections were short. I found the writing to be clear and to the point. The authors do not try to be hip or cool and focus on content.

To really get the most out of the book a reader should be familiar with JavaScript, html and css. It wouldn't hurt to also understand RESTful web services. Once the first two chapters explaining Zembly are over, this really is a cook-book, or set of examples/tutorials rather than instruction on how to code or do markup. The experienced developer could probably slide by even if they were not working regularly with these technologies. Someone who has never written a bit of code may want to spend some time building some familiarity with javascript before they tack this book. Zembly itself has some quick tutorials that require almost no knowledge of programming. I watched a graphic art guy at work throw together a Facebook widget/app in about 10 minutes using Zembly.

Zembly is still in what has become the ubiquitous beta state for on-line applications. And as it is under active development this book probably has a very short shelf-life. It wont be all that long before the platform moves along and leaves it behind. In an effort to shore up against that inevitability all the code and resources for the book are stored in Zembly. If changes are made today, tomorrows reader will be able to work with the updated structures. The book itself is also available in traditional ebook formats and through Safari.

One of the nicer things about the Zembly approach is that it removes the barrier of hosting costs to participate in this space. In turn the developer surrenders up their work to be used by others. This may be problematic for those who would rather keep all their code to themselves, but fits in-line nicely with the fact that the entire stack is built on FOSS products. Of course, once again the beta status means that this free ride is not something that is guaranteed for perpetuity. I'm guessing that at some point, this type of central hosting is going to necessitate an attempt by Sun to generate some income from the service.

Getting in on the front end of a technology can often be rather difficult. The Sun folks seem to be ahead of the curve on making it easier for people to participate with Zembly. There are excellent tutorials and documentation on the site itself. For those who want to take it a step further, there is this book with a wealth of examples and explanations that will really accelerate the learning process. I'm not sure if Zembly will become the next big thing or not, but anyone who wants to gamble that it will, here is a chance to make the most of the ride.

You can purchase Assemble the Social Web with Zembly from amazon.com. Slashdot welcomes readers' book reviews — to see your own review here, read the book review guidelines, then visit the submission page.

Frequent Slashdot contributor Bennett Haselton writes "A New Zealand court has allowed a plaintiff to serve papers on a defendant via Facebook, following a similar ruling from an Australian court last year. But as these rulings do not necessarily mean, as Facebook announced in a press release, that the courts have endorsed Facebook 'as a reliable, secure and private medium for communication.' The trend could lead to abuses if courts start taking 'Facebook service' too seriously." For more of the many words written by Bennett, hop on that curiously named link right below.

A New Zealand court has ruled that a plaintiff can serve papers on a defendant via a message sent to their Facebook account. Last December, an Australian court ruled that a company could serve papers on a couple after failed attempts to reach them by regular mail and e-mail. Facebook responded to the ruling with a statement that said, "We're pleased to see the Australian court validate Facebook as a reliable, secure and private medium for communication. The ruling is also an interesting indication of the increasing role that Facebook is playing in people's lives." I think there are two interesting questions here: (1) Is that really how courts view service via Facebook? And (2) What will happen if courts do begin to view service via Facebook that way?

As to the first question — the court's endorsement of service via Facebook does not mean that they think the service is necessarily secure or reliable. Courts often let you serve papers on a party in a court case via means that are less reliable than normal channels, provided that you've exhausted the more reliable means first. When I was trying to earn my way into heaven by suing spammers in Small Claims court, some states allowed corporations to be served by serving the papers on the Secretary of State in the corporation's home state, but only if you could prove that you had tried and failed to serve the corporation at their registered address. In cases where I served the Secretary of State, it's unlikely that the defendant ever even saw the papers (since the only thing the Secretary of State could do with them was forward them to the defendants' address on file, where I'd already tried to locate them), but it still "counted" because I had exhausted the regular means of serving the documents. Sometimes when serving an individual, if the sheriff couldn't reach someone at home, a judge would sign an order allowing the legal papers to be stuck to their front door (which is neither "secure" nor "reliable"), but only after the sheriff had been unable to deliver it to them in person. So a court's endorsement of Facebook as a means of service doesn't necessarily mean the court thinks that the means of service is reliable. It just means it's a good last resort when conventional methods haven't worked.

Facebook is not, after all, secure or reliable, although these limitations are not the fault of Facebook itself. By "not reliable," I don't mean that it loses or mis-routes messages — I've never seen that happen — but that you have no idea whether someone has signed in to read a message, or deleted it by accident, or lost it among all the other messages that they received. As for whether it's "secure," like most services, the greatest weakness in Facebook's security is in the 'forgot your password' feature — if you compromise someone's e-mail account, then you can have a password reset link sent to their e-mail address and compromise their Facebook account as well. So your Facebook account is only as secure as your e-mail account, and e-mail accounts are usually vulnerable in their own "forgot your password" feature, which often lets you access someone's e-mail account just by knowing their birth date, their zip code, and the answer to an easy question like "Who is your favorite fictional character?" And in any case, obtaining "service" via Facebook doesn't preclude the possibility that the person you served on Facebook was an impostor, or another person who happened to have the same name.

What would really change the game would be if courts started ruling that service via Facebook was valid even without first attempting to serve a party via mail or other means. I had my own experience with a case like this in 2000, when programmers Matthew Skala and Eddy Jansson released a program called "CPHack" which could decode the encrypted list of sites blocked by a program called Cyber Patrol, so that people who owned copies of the program could use CPHack to decrypt the list of blocked sites. (One of the more controversial aspects of such blocking software is that the list of blocked sites is hidden from purchasers of the program.) A judge granted Cyber Patrol a ruling forbidding the authors from distributing the program, and ordering anyone hosting a mirror copy of the program to remove it as well. That same day, I received a copy of the ruling via e-mail from Cyber Patrol's lawyer, ordering us to remove the mirror from the Peacefire site. I asked a lawyer if that was considered valid service (this was back when I still thought that a legal question like that always had an objective answer, as opposed to the question of "valid service" being an entirely subjective one that depended on what judge you happened to get), and he said that I shouldn't take any chances and should take the mirror down anyway, which we did. Dozens of other mirror sites, which had sprung up in anticipation of the legal controversy, were also served with papers, although the overseas ones mostly ignored them.

So this was very different from a ruling made by the 9th Circuit Court of Appeals two years later, allowing a Las Vegas casino to serve an offshore company via e-mail because regular methods had failed. The court in that case wrote, "When faced with an international e-business scofflaw playing hide-and-seek with the federal court, e-mail may be the only means of effecting service of process." But I was a domestic scofflaw whose mailing address was publicly known (in the WHOIS registration for the Peacefire site). What was the rationale for allowing me to be served by e-mail?

Unfortunately I think it's probably just a case where the rules were vague enough that the judge felt entitled to bend them to achieve an outcome that he wanted. The 9th Circuit didn't leave much doubt as to the level of objectivity in their ruling on e-mail service either, in calling the defendant an "international e-business scofflaw."

And these are the two main reasons why I think that allowing electronic "insta-service" via e-mail or Facebook — in cases where parties have not first tried to serve papers via regular means — would erode the rights of the little guy. First, in most of the cases I can think of where a powerful plaintiff was playing "whack-a-mole" with multiple defendants by using electronic service of process to shut down new sites as fast as they were springing up, the goal they were trying to achieve was (a) futile, if half the mirror sites were overseas anyway, and (b) ultimately incompatible with civil liberties. (Why shouldn't people have the right to decrypt the list of sites blocked by Cyber Patrol? After the ACLU got involved on appeal, a higher court ultimately ruled that mirror sites could not be ordered to take down CPHack. The HD DVD encryption key controversy is another well-known example.) In cases where a plaintiff has a legitimate claim against multiple sites — for example, sites that are violating the plaintiff's copyright by hosting unauthorized copies of content that they own — most service providers already publish an e-mail address where copyright owners can send a DMCA takedown notice, and where the copyright owner is risking large statutory financial penalties if they send a takedown notice that turns out to be baseless. There are no similar protections to prevent abuses of the system through electronic service of other kinds of legal notices.

The other reason this trend could work against the average person, is that any vague rule that is not consistently followed by different judges, puts non-lawyers at a disadvantage in court. Partly because it may confuse non-lawyers who hear that e-mail service was allowed in one case, and think that's part of "the rules," and then find that e-mail service was disallowed in another case, and wonder how "the rules" could allow it in one case but not in another, all the while laboring under the mistaken impression that there actually are "rules" which unambiguously determine whether or not e-mail service is allowed, when the truth is that it's just up to each individual judge. But also because every ambiguity in the rules is another opportunity for the judge's prejudices to influence the outcome. I do not think that most judges are prejudiced against people based on race or gender, but I doubt you could find any legal professional who thinks that most judges would take a case equally seriously regardless of whether it was brought by a professional lawyer or by a layperson representing themselves. (At one point in my spammer-suing career, I had only about a 50-50 chance of my motions even being read.)

So, let's not get carried away applauding judges for being "hip" and "with it" for allowing service via e-mail or Facebook. And if they start allowing it more frequently, can we at least ask that they pick one rule and stick with it?

1 a bee writes "With the White House claiming national security grounds for failing to release ACTA related information, including negotiating documents and even the list of participants, the spotlight is now on just who does have access. Turns out, according to James Love, hundreds of advisers, many of them corporate lobbyists, are considered 'cleared advisers.' The list looks a who's who of captains of industry."

Iddo Genuth writes "After several delays, including twice over the past week, the space shuttle Discovery has finally been launched into space. The spacecraft took off at precisely 7:43 p.m. EDT, embarking on the STS-119 mission, which will provide the International Space Station with the fourth and final set of solar arrays — and which will make the ISS brighter than Venus. The shuttle will also deliver to the ISS its newest crew member, Japan's Aerospace Exploration Agency astronaut Koichi Wakata, who will replace flight engineer Sandra Magnus at the station."

Iddo Genuth writes "After several delays, including twice over the past week, the space shuttle Discovery has finally been launched into space. The spacecraft took off at precisely 7:43 p.m. EDT, embarking on the STS-119 mission, which will provide the International Space Station with the fourth and final set of solar arrays — and which will make the ISS brighter than Venus. The shuttle will also deliver to the ISS its newest crew member, Japan's Aerospace Exploration Agency astronaut Koichi Wakata, who will replace flight engineer Sandra Magnus at the station."

SpuriousLogic writes "I work as a senior software engineer, and a fair amount of my time is spent interviewing new developers. I have seen a growing trend of what I would call 'TV reality' college graduates — kids who graduated school in the last few years and seem to have a view of the workplace that is very much fashioned by TV programs, where 22-year-olds lead billion-dollar corporate mergers in Paris and jet around the world. Several years ago I worked at a company that did customization for the software they sold. It was not full-on consultant work, but some aspects of it were 'consulting light,' and did involve travel, some overseas. Almost every college graduate I interviewed fully expected to be sent overseas on their first assignment. They were very disappointed when told they were most likely to end up in places like Decater, IL and Cedar Rapids, IA, as only the most senior people fly overseas, because of the cost. Additionally, I see people in this age bracket expecting almost constant rewards. One new hire told me that he thought he had a good chance at an award because he had taught himself Enterprise Java Beans. When told that learning new tech is an expected part of being a developer, he argued that he had learned it by himself, and that made it different. So today I see an article about the growing narcissism of students, and I want to ask this community: are you seeing the sorts of 'crashing down to Earth' expectations of college grads described here? Is working with this age bracket more challenging than others? Do they produce work that is above or below your expectations of a recent college grad?" We discussed a similar question from the point of view of the young employees a few months back.

I Believe in Unicorns writes "Red Hat's patent policy says 'In an attempt to protect and promote the open source community, Red Hat has elected to... develop a corresponding portfolio of software patents for defensive purposes. We do so reluctantly...' Meanwhile, USPTO Application #: 20090063418, 'Method and an apparatus to deliver messages between applications,' claims a patent on routing messages using an XQuery match, which is an extension of the 'unencumbered' AMQP protocol that Red Hat is helping to make. Is this a defensive patent, or is Red Hat cynically staking out a software patent claim to an obvious extension of AMQP? Is Red Hat's promise to 'refrain from enforcing the infringed patent' against open source a reliable contract, or a trap for the unwary? Given the Microsoft-Red Hat deal in February, are we seeing Red Hat's 'Novell Moment?'" Reader Defeat_Globalism contributes a related story about an international research team who conducted experiments to "quantify the ways patent systems and market forces might influence someone to invent and solve intellectual problems." Their conclusion was that a system which doesn't restrict prizes to the winner provides more motivation for innovation.

volume4 writes "The switch has been flipped and Jaiku has been moved to App Engine. Google will no longer be developing Jaiku, so the code and the future of Jaiku is in the hands of the open source community. From the Jaiku blog: 'Today, we are open sourcing the Jaiku code base under the Apache License 2.0. The code is available as JaikuEngine on Google Code Project Hosting as of now. Anyone can set up and run their own JaikuEngine instance on Google App Engine.'" We discussed Google's purchase of Jaiku in 2007, and their subsequent decision to halt development a few months ago.

volume4 writes "The switch has been flipped and Jaiku has been moved to App Engine. Google will no longer be developing Jaiku, so the code and the future of Jaiku is in the hands of the open source community. From the Jaiku blog: 'Today, we are open sourcing the Jaiku code base under the Apache License 2.0. The code is available as JaikuEngine on Google Code Project Hosting as of now. Anyone can set up and run their own JaikuEngine instance on Google App Engine.'" We discussed Google's purchase of Jaiku in 2007, and their subsequent decision to halt development a few months ago.

theodp writes "Just when you thought annual reviews couldn't get worse, BusinessWeek reports that HR departments at companies like Microsoft and IBM are starting to use mathematical analysis to determine the value of each employee. At an undisclosed Internet company, analysis of (non-verbal) communications was used to produce a circle to represent each employee — those determined to generate or pass along valuable info were portrayed as large and dark-colored circles ('thought leaders' and 'networked curators'), while those with small and pale circles were written off as not adding a hell of a lot. 'You have to bring the same rigor you bring to operations and finance to the analysis of people,' explains Microsoft's Rupert Bader. Hey, who could argue with what Quants did for finance?"

hessian notes a Cornell survey, published in the Psychological Bulletin, of 35 years of sociological studies that concludes that women tend to choose non-math-intensive fields for their careers not because they lack mathematical ability, but because they want flexibility to raise children or prefer less math-intensive fields of science. "'A major reason explaining why women are underrepresented not only in math-intensive fields but also in senior leadership positions in most fields is that many women choose to have children, and the timing of child rearing coincides with the most demanding periods of their career, such as trying to get tenure or working exorbitant hours to get promoted,' said lead author Stephen J. Ceci... The authors concluded that hormonal, brain, and other biological sex differences were not primary factors in explaining why women were underrepresented in science careers, and that studies on social and cultural effects were inconsistent and inconclusive. They also reported that although 'institutional barriers and discrimination exist, these influences still cannot explain why women are not entering or staying in STEM careers,' said Ceci."

Eurogamer reports that Sony Online Entertainment will be adding the ability to do real money trading to at least some of their Vanguard: Saga of Heroes servers. It's the same service they opened for a pair of Everquest II servers a while back. Quoting: "The service, offered by Live Gamer, allows players to sell items, currency and characters for real cash through a secure channel, authorised by the game operator. Most real-money trading in MMOs is a 'grey' market that doesn't have the operator's consent. ... Sony Online Entertainment recently said that it had no intention to bring its other real-money trading initiative — the Station Cash item shop — to Vanguard."

Fred Trotter writes "CCHIT is the dominant Electronic Health Record certification body in the US. It is also decidedly anti-FOSS and has been for years. Certification of one kind or another will be required for EHR systems to qualify for funding under the Stimulus Act. If CCHIT is chosen as the certification body, and the current certification strategies continue, it will not be possible to have a funded EHR that is both certified and truly FOSS. Now, however, CCHIT has agreed to meet the FOSS Health IT community at HIMSS 09 to address this issue." We discussed the shortcomings in the stimulus bill as it relates to FOSS a few days back.

volume4 brings news that David Wood of the Symbian Foundation has made a post detailing their plans for a release schedule, with new versions due out every six months. We discussed Nokia's acquisition of Symbian for the purpose of open sourcing the popular mobile OS last year. Quoting: "There's a lot of activity underway, throughout the software development teams for all the different packages that make up the Symbian Platform. These packages are finding their way into platform releases. The plan is that there will be two platform releases each year. ... Symbian^2, which is based on S60 5.1, reaches a functionally complete state at the middle of this year, and should be hardened by the end of the year. This means that the first devices based on Symbian^2 could be reaching the market any time around the end of this year — depending on the integration plans, the level of customisation, and the design choices made by manufacturers. Symbian^3 follows on six months later — reaching a functionally complete state at the end of this year, and should be hardened by the middle of 2010."

Eric Goldman writes "Earlier this month, we discussed HB 450, the Utah Legislature's third attempt to regulate keyword advertising after the past two efforts failed miserably. The latest attempt barely passed the Utah House, aided in part by a 'yes' vote from Representative Jennifer Seelig, who also happens to be a lobbyist-employee of 1-800 Contacts, the principal advocate of HB 450. Nevertheless, HB 450 died in the Utah Senate without a vote when the Utah Legislature adjourned last night. Despite the seeming good news, it would be surprising if the Utah Legislature didn't try a fourth time to regulate keyword advertising in a future session."

theodp writes "Steve Jobs wasn't around to convince you that you should be impressed, but on Wednesday Apple unveiled a 4GB Shuffle that's half the size of its predecessor. Holding up to 1,000 songs, the pre-shrunk Shuffle sports a 10-hour battery life and also adds a new VoiceOver feature that can recite song titles, artists, and playlist names, as well as provide status information. Even without a show from Steve, the new player is generally leaving folks dazzled, although there are some complaints." Update: 3/14 at 14:10 by SS: Reader Mike points out some disturbing news that the new Shuffle contains DRM which, according to a review at iLounge, prevents it from fully working with any headphones that don't have an Apple "authentication chip."

NewYorkCountryLawyer writes "You may recall that in an RIAA case, SONY BMG Music v. Tenenbaum, the district court ruled that an oral argument about the constitutionality of statutory damages could be streamed, and the RIAA has been fighting that with a petition for 'mandamus or prohibition' in the appeals court, which is opposed by the press. Interestingly, it now turns out that the appeals court's oral argument about the streaming will itself be recorded and then streamed. It is hard to imagine how a court which routinely streams its own oral arguments can rule that it is somehow inappropriate for similar oral arguments in the district court to be streamed as well."

NewYorkCountryLawyer writes "You may recall that in an RIAA case, SONY BMG Music v. Tenenbaum, the district court ruled that an oral argument about the constitutionality of statutory damages could be streamed, and the RIAA has been fighting that with a petition for 'mandamus or prohibition' in the appeals court, which is opposed by the press. Interestingly, it now turns out that the appeals court's oral argument about the streaming will itself be recorded and then streamed. It is hard to imagine how a court which routinely streams its own oral arguments can rule that it is somehow inappropriate for similar oral arguments in the district court to be streamed as well."

NewYorkCountryLawyer writes "You may recall that in an RIAA case, SONY BMG Music v. Tenenbaum, the district court ruled that an oral argument about the constitutionality of statutory damages could be streamed, and the RIAA has been fighting that with a petition for 'mandamus or prohibition' in the appeals court, which is opposed by the press. Interestingly, it now turns out that the appeals court's oral argument about the streaming will itself be recorded and then streamed. It is hard to imagine how a court which routinely streams its own oral arguments can rule that it is somehow inappropriate for similar oral arguments in the district court to be streamed as well."

NewYorkCountryLawyer writes "You may recall that in an RIAA case, SONY BMG Music v. Tenenbaum, the district court ruled that an oral argument about the constitutionality of statutory damages could be streamed, and the RIAA has been fighting that with a petition for 'mandamus or prohibition' in the appeals court, which is opposed by the press. Interestingly, it now turns out that the appeals court's oral argument about the streaming will itself be recorded and then streamed. It is hard to imagine how a court which routinely streams its own oral arguments can rule that it is somehow inappropriate for similar oral arguments in the district court to be streamed as well."

CWmike writes "The fallout from Thursday's arrests of a District of Columbia IT security official and contractor quickly raised questions about the fate of Vivek Kundra, the new federal CIO who until recently ran the office now mired in bribery allegations. Appointed by President Barack Obama as CIO less than two weeks ago, Kundra was CTO for the District of Columbia. But yesterday, Kundra's former office in a downtown government building was a crime scene. A White House official, speaking on background, confirmed today that Kundra took a leave of absence from his new CIO job shortly after federal investigators arrested two men in the DC government office on bribery charges. The official would not elaborate on the reasons for the leave; there were no indications yesterday that Kundra was involved in any wrongdoing. Kundra's decision could slow his plan to create a 'revolution' in the federal government's use of technology."

CWmike writes "The fallout from Thursday's arrests of a District of Columbia IT security official and contractor quickly raised questions about the fate of Vivek Kundra, the new federal CIO who until recently ran the office now mired in bribery allegations. Appointed by President Barack Obama as CIO less than two weeks ago, Kundra was CTO for the District of Columbia. But yesterday, Kundra's former office in a downtown government building was a crime scene. A White House official, speaking on background, confirmed today that Kundra took a leave of absence from his new CIO job shortly after federal investigators arrested two men in the DC government office on bribery charges. The official would not elaborate on the reasons for the leave; there were no indications yesterday that Kundra was involved in any wrongdoing. Kundra's decision could slow his plan to create a 'revolution' in the federal government's use of technology."

techprophet writes to mention that a new take on self-healing plastic could provide a long-term solution to scratched screens. The new polymer, developed by scientists at the University of Southern Mississippi, uses UV light to reform bonds between molecules rather than embedded healing agents of similar systems. "At the core of their design is polyurethane, which is an elastic polymer that already has decent scratch resistance. To enhance its ability to withstand mechanical damage, Ghosh and Urban added two more components, OXE and CHI. OXE has an unstable chemical structure (a four-membered ring containing three carbons and one oxygen) that makes it prone to being split open. CHI is UV sensitive. The idea is that, if the polyurethane gets damaged by a scratch, the unstable ring structure of OXE will open to create two reactive ends. Then, UV light can trigger CHI to form new links with the reactive ends of OXE and thereby fix the break in the polymer."

An anonymous reader writes "Following the long-awaited release of FFmpeg 0.5, Phoronix has conducted an interview with three FFmpeg developers (Diego Biurrun, Baptiste Coudurier, and Robert Swain) about this project's recent release. In this interview they talk about moving to a 3/6-month release cycle, the criteria for version 1.0, Blu-Ray support on Linux, OpenCL and GPGPU acceleration, multi-threading FFmpeg, video APIs, their own video codecs, and legal challenges they have run into."

FiveRings writes "BusinessInsider has a story about Worlds.com, a company that inherited the patent on virtual worlds from the Starlight Starbright Foundation and is taking it to court against NCSoft over the company's various MMOs. If successful, he will press on and sue the makers of Second Life and World of Warcraft as well. The article notes that the NCSoft case is being held in east Texas, which has been a favorable venue for patent trolls in the past."

TRNick writes "Is the future of gaming more or less free, perhaps funded by advertising or micropayments? A bunch of MMOs have pioneered the way, and now they are being followed by the likes of EA, Sony and id Software, each of which is offering some form of free gaming. But it's not just the big guys. TechRadar talks to a new generation of indie developers who are making names for themselves. 'I make most of my money from sponsors,' says one. 'We're all here because we love making games first and foremost,' says another. But can free games ever make enough money to fund the really ambitious, event games that get the headlines?" While paid games aren't likely to be on their way out any time soon, more and more developers and publishers are experimenting with cheaper pricing, and the results so far seem positive.

TRNick writes "Is the future of gaming more or less free, perhaps funded by advertising or micropayments? A bunch of MMOs have pioneered the way, and now they are being followed by the likes of EA, Sony and id Software, each of which is offering some form of free gaming. But it's not just the big guys. TechRadar talks to a new generation of indie developers who are making names for themselves. 'I make most of my money from sponsors,' says one. 'We're all here because we love making games first and foremost,' says another. But can free games ever make enough money to fund the really ambitious, event games that get the headlines?" While paid games aren't likely to be on their way out any time soon, more and more developers and publishers are experimenting with cheaper pricing, and the results so far seem positive.

Gamasutra reports that Mythic Entertainment is consolidating a number of their Warhammer Online servers to keep population levels within an acceptable range. 43 servers are set to close in North America and Oceania, and 20 more in Europe. Mythic posted details of the character transfers at the game's website. CEO Mark Jacobs also made a "State of the Game" post, highlighting the live expansion that's currently underway, as well as the changes and updates they have planned for the near future.

Jack Spine writes "The inventor of the World Wide Web has pointed out some of the dangers of deep packet inspection. Sir Tim said that ISPs 'snooping' on data was similar to the interception of mail. 'This is very important to me, as what is at stake is the integrity of the internet as a communications medium,' Berners-Lee said on Wednesday. TBL's comments come as the UK government is gearing up to intercept all web communications in the UK through the Intercept Modernisation Programme, and echo comments he made last year about Phorm."

Jack Spine writes "The inventor of the World Wide Web has pointed out some of the dangers of deep packet inspection. Sir Tim said that ISPs 'snooping' on data was similar to the interception of mail. 'This is very important to me, as what is at stake is the integrity of the internet as a communications medium,' Berners-Lee said on Wednesday. TBL's comments come as the UK government is gearing up to intercept all web communications in the UK through the Intercept Modernisation Programme, and echo comments he made last year about Phorm."

stoolpigeon writes "My past as a DBA probably makes me a bit biased, but the reaction I've seen the most when a database application isn't performing as well as would be liked seems to focus on the database side of things. The search for a solution usually seems to center around tuning db parameters, the building (or removal) of indexes and, if the budget allows, throwing hardware at the problem. In their new work, Refactoring SQL Applications, Faroult and L'Hermite bring a much wider range of options to the table. There is a lot in this little book for the developer charged with fixing an existing application and I think a lot of good information that could save one from making a number of headache-inducing mistakes on a new application." Keep reading for the rest of JR's review. Refactoring SQL Applications author Stephane Faroult with Pascal L'Hermite pages 293 publisher O'Reilly Media, Inc. rating 9/10 reviewer JR Peck ISBN 978-0-596-51497-6 summary Good for a developer charged with fixing an existing application. The book is divided into eight chapters; the first two deal with how to approach a problematic application in general. In the preface the authors say, "This book tries to take a realistic and honest view of the improvement of applications with a strong SQL component, and to define a rational framework for tactical maneuvers." I found this to be true throughout the entire book and was impressed by how well the examples, suggestions and problems echoed my real-life experience. This book is first and foremost practical. There is really almost nothing in the book that does not come immediately to bear upon the problem at hand. I've seen others do a lot less with many more pages.

The examples and benchmarks are compared across three different popular relational database management systems. They are MySQL, Oracle RDBMS and Microsoft SQL Server. I thought that this brought up a couple interesting issues that are not directly addressed in the book. First is that the authors are talking about how to improve performance, not comparing platforms, but the numbers are there and may be of some interest to people who would like to compare them. Secondly, I've met a number of people over the years who get quite animated about insisting that a good DBA does not need to know any certain solution, but rather just the fundamentals. I think Faroult and L'Hermite put this idea to rest, though unintentionally. In order to discuss how to best understand what exactly is happening and how best remedy issues, they show that it is necessary to have an understanding of platform specific issues and tools. This is true on two levels. The first is that the location of use of the built in tools for each platform are different. The second is that what works for one platform does not necessarily work for another.

For example, Chapter Two "Sanity Checks" contains a section on parsing and bind variables. The authors compare performance when queries are hard coded, with new prepared statements on each iteration (firm coded) and with one prepared statement and changing the parameter value on each iteration in a loop (soft coded). On Oracle and SQL Server the performance was poorest with hard coded, better with firm coded and best with soft coded. MySQL did best with soft coded as well but actually took a performance hit moving from hard coded to firm coded. This had to do with differences in how MySQL server caches statements. The authors took the time to rewrite their code from java to C in order to ensure that the issue was not related to language or driver issues. This is not to say that one can ignore RDBMS and SQL fundamentals, but rather that to get top performance requires knowledge of platform specific issues. This also comes out again when dealing with optimizers.

With that in mind, the authors recommend that readers have a solid understanding of SQL and some programming language. Most examples are SQL and code is given in Java and PHP. There are also examples that illustrate SQL extensions showing procedures, functions, etc. written for all three RDBMS products covered. The authors stick primarily to standard SQL but do make note and at times show examples of how things will look in each of the other databases. This information is current and reflects the most recent versions of the each product.

The fourth chapter, "Testing Framework" is incredibly useful. The authors cover generating test data and then checking correctness of outcomes through comparison. This is really useful information for anyone working to improve an application, or writing one for the first time. I think it also a large part of why this book could really appeal to new and experienced developers as well as the developer working on existing or brand new applications. I think there is a good chance that only the most extremely experienced developer would find nothing new here, or at least some new way to approach a problem. New developers can learn quite a bit and avoid some bad habits and assumptions without having to gain that information the hard way. And then the tools for generating random data, large amounts of data and comparing results will provide excellent opportunities for learning and real world application.

The next three chapters cover dealing with specific types of issues and how to improve performance. The last chapter then quickly describes a scenario of just how the authors step into real world situations and start to attack a problem. This is followed with two appendices. The first is scripts and samples, the second tools that are available to help in finding issues and resolving them. Some of the authors tools use SQLite, which is discussed briefly in the chapter on creating test data as some of the tools depend upon it.

I think that it has been a while since I've read a book that could have such a rapid return on investment. There are many suggestions and insights that should enable anyone to squeeze better performance out of just about any database application. While the focus is on the application side, there is plenty that requires understanding and work on the database side as well. There is discussion of the parameters and hardware I mentioned at the start of this review. But rather than the only options, they are one part in a much larger and systematic approach.

The authors relate that often refactoring for this type of application comes into play when something that used to work does not work any more. This can often lead to an environment of high pressure and emotion. The desire for a rapid resolution can lead to casting about in the dark for a quick fix or a feeling that cost is no longer as significant since a fix must be had now. The authors argue, and I agree, that this is exactly when a rational, disciplined process of tracking down and fixing issues is the most valuable. I agree. The issue is of course that someone in a position to do something must have the ability to take that approach. This book will get one well on the way to being in that place. Of course it can't take a brand new developer or DBA an expert. Much like a degree it can give them some fundamental tools that will allow them to take full advantage of experience as it comes rather than just crashing and burning.

If I could I'd have any developer on a database centric application read this, and DBAs as well. There is a lot here for both sides to learn about just how much they depend upon and impact one another. This may be an idealistic dream, especially for larger shops where often the relationship between those two groups is adversarial, but I think that such an approach could only make life much better for everyone involved. For anyone looking to enter this world on either side of the DBA or developer equation, this may make a nice addition to their education. For that individual wearing both hats this could be a life saver. In this small book they will learn many things to look out for as well as gain exposure to some of the similarities and differences in what are arguably the top three relational database management systems right now.

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

stoolpigeon writes "My past as a DBA probably makes me a bit biased, but the reaction I've seen the most when a database application isn't performing as well as would be liked seems to focus on the database side of things. The search for a solution usually seems to center around tuning db parameters, the building (or removal) of indexes and, if the budget allows, throwing hardware at the problem. In their new work, Refactoring SQL Applications, Faroult and L'Hermite bring a much wider range of options to the table. There is a lot in this little book for the developer charged with fixing an existing application and I think a lot of good information that could save one from making a number of headache-inducing mistakes on a new application." Keep reading for the rest of JR's review. Refactoring SQL Applications author Stephane Faroult with Pascal L'Hermite pages 293 publisher O'Reilly Media, Inc. rating 9/10 reviewer JR Peck ISBN 978-0-596-51497-6 summary Good for a developer charged with fixing an existing application. The book is divided into eight chapters; the first two deal with how to approach a problematic application in general. In the preface the authors say, "This book tries to take a realistic and honest view of the improvement of applications with a strong SQL component, and to define a rational framework for tactical maneuvers." I found this to be true throughout the entire book and was impressed by how well the examples, suggestions and problems echoed my real-life experience. This book is first and foremost practical. There is really almost nothing in the book that does not come immediately to bear upon the problem at hand. I've seen others do a lot less with many more pages.

The examples and benchmarks are compared across three different popular relational database management systems. They are MySQL, Oracle RDBMS and Microsoft SQL Server. I thought that this brought up a couple interesting issues that are not directly addressed in the book. First is that the authors are talking about how to improve performance, not comparing platforms, but the numbers are there and may be of some interest to people who would like to compare them. Secondly, I've met a number of people over the years who get quite animated about insisting that a good DBA does not need to know any certain solution, but rather just the fundamentals. I think Faroult and L'Hermite put this idea to rest, though unintentionally. In order to discuss how to best understand what exactly is happening and how best remedy issues, they show that it is necessary to have an understanding of platform specific issues and tools. This is true on two levels. The first is that the location of use of the built in tools for each platform are different. The second is that what works for one platform does not necessarily work for another.

For example, Chapter Two "Sanity Checks" contains a section on parsing and bind variables. The authors compare performance when queries are hard coded, with new prepared statements on each iteration (firm coded) and with one prepared statement and changing the parameter value on each iteration in a loop (soft coded). On Oracle and SQL Server the performance was poorest with hard coded, better with firm coded and best with soft coded. MySQL did best with soft coded as well but actually took a performance hit moving from hard coded to firm coded. This had to do with differences in how MySQL server caches statements. The authors took the time to rewrite their code from java to C in order to ensure that the issue was not related to language or driver issues. This is not to say that one can ignore RDBMS and SQL fundamentals, but rather that to get top performance requires knowledge of platform specific issues. This also comes out again when dealing with optimizers.

With that in mind, the authors recommend that readers have a solid understanding of SQL and some programming language. Most examples are SQL and code is given in Java and PHP. There are also examples that illustrate SQL extensions showing procedures, functions, etc. written for all three RDBMS products covered. The authors stick primarily to standard SQL but do make note and at times show examples of how things will look in each of the other databases. This information is current and reflects the most recent versions of the each product.

The fourth chapter, "Testing Framework" is incredibly useful. The authors cover generating test data and then checking correctness of outcomes through comparison. This is really useful information for anyone working to improve an application, or writing one for the first time. I think it also a large part of why this book could really appeal to new and experienced developers as well as the developer working on existing or brand new applications. I think there is a good chance that only the most extremely experienced developer would find nothing new here, or at least some new way to approach a problem. New developers can learn quite a bit and avoid some bad habits and assumptions without having to gain that information the hard way. And then the tools for generating random data, large amounts of data and comparing results will provide excellent opportunities for learning and real world application.

The next three chapters cover dealing with specific types of issues and how to improve performance. The last chapter then quickly describes a scenario of just how the authors step into real world situations and start to attack a problem. This is followed with two appendices. The first is scripts and samples, the second tools that are available to help in finding issues and resolving them. Some of the authors tools use SQLite, which is discussed briefly in the chapter on creating test data as some of the tools depend upon it.

I think that it has been a while since I've read a book that could have such a rapid return on investment. There are many suggestions and insights that should enable anyone to squeeze better performance out of just about any database application. While the focus is on the application side, there is plenty that requires understanding and work on the database side as well. There is discussion of the parameters and hardware I mentioned at the start of this review. But rather than the only options, they are one part in a much larger and systematic approach.

The authors relate that often refactoring for this type of application comes into play when something that used to work does not work any more. This can often lead to an environment of high pressure and emotion. The desire for a rapid resolution can lead to casting about in the dark for a quick fix or a feeling that cost is no longer as significant since a fix must be had now. The authors argue, and I agree, that this is exactly when a rational, disciplined process of tracking down and fixing issues is the most valuable. I agree. The issue is of course that someone in a position to do something must have the ability to take that approach. This book will get one well on the way to being in that place. Of course it can't take a brand new developer or DBA an expert. Much like a degree it can give them some fundamental tools that will allow them to take full advantage of experience as it comes rather than just crashing and burning.

If I could I'd have any developer on a database centric application read this, and DBAs as well. There is a lot here for both sides to learn about just how much they depend upon and impact one another. This may be an idealistic dream, especially for larger shops where often the relationship between those two groups is adversarial, but I think that such an approach could only make life much better for everyone involved. For anyone looking to enter this world on either side of the DBA or developer equation, this may make a nice addition to their education. For that individual wearing both hats this could be a life saver. In this small book they will learn many things to look out for as well as gain exposure to some of the similarities and differences in what are arguably the top three relational database management systems right now.

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

je ne sais quoi writes "The Apple rumor mill is churning today. Reuters and the DOW Jones news wire are reporting that an anonymous source in Taiwan has leaked that Apple has ordered some 10-inch touch-screens from WinTek, the maker of the touch-screen for the iPhone. It looks like an Apple netbook could possibly be in the works for a delivery date in Q3 of this year, in time for back-to-school sales. CNET and Engadget have completely unsubstantiated mock-ups."

superglaze (ZDNet UK) writes "Google is gearing up to launch cookie-based 'interest-based' advertising, which involves monitoring the user's passage across various WebSense partner sites. The idea is to have better-targeted advertising, which is not a million miles away from what Phorm is trying to do — the difference, it seems at first glance, is that Google is being relatively up-front about its intentions."

Julie188 writes "When the Android Market began offering paid apps last month, developers with the unlocked version of Google's Android phone quickly learned that they couldn't access them. The policy, which threatened to alienate the small developer base that Google needs to nurture at all costs, didn't make much sense. And now, with the release of Version 1.1 of Android for the developer phone, developers can access paid apps — as long as they aren't copy-protected. But in a weird way, that's good news. Very few developers currently copy-protect their Android apps simply because Android's copy-protection scheme is notoriously weak."

Norsefire writes "Two economists at Washington University in St. Louis are claiming that copyright and patent laws are 'killing innovation' and 'hurting [the] economy.' Michele Boldrin and David K. Levine state they would like to see copyright law abolished completely as there are other protections available to the creators of 'intellectual property' (a term they describe as 'propaganda,' and of recent origin). They are calling on Congress to grant patents only where an invention has social value, where the patent would not stifle innovation, and where the absence of a patent would damage cost-effectiveness."

Glyn Moody writes "For years, the content industries having been trying to get laws passed that would stop people sharing files. For years they failed. Then they came up with the 'three strikes and you're out' idea — and it is starting to be put into law around the world. First we had France, followed by countries like Italy, Ireland — and now South Korea: 'On March 3, 2009, the National Assembly's Committee on Culture, Sports, Tourism, Broadcasting & Communications (CCSTB&C) passed a bill to revise the Copyright Law. The bill includes the so called, "three strikes out" or "graduated response" provision.' Why has the 'three strikes' idea caught on where others have failed? And what is the best way to stop it spreading further?"