snydeq writes "Simon Phipps sheds light on a fight for control over Vert.x, an open source project for scalable Web development that 'seems immunized to corporate control.' 'Vert.x is an asynchronous, event-driven open source framework running on the JVM. It supports the most popular Web programming languages, including Java, JavaScript, Groovy, Ruby, and Python. It's getting lots of attention, though not necessarily for the right reasons. A developer by the name of Tim Fox, who worked at VMware until recently, led the Vert.x project — before VMware's lawyers forced him to hand over the Vert.x domain, blog, and Google Group. Ironically, the publicity around this action has helped introduce a great technology with an important future to the world. The dustup also illustrates how corporate politics works in the age of open source: As corporate giants grasp for control, community foresight ensures the open development of innovative technology carries on.'"

Last week you asked Jazz technical lead Erich Gamma questions about Jazz or anything else in his realm of expertise. Here are his answers, along with many external links and places to continue the conversation if you are interested.

powerlord writes "The Neo Project (mentioned in a recent slashdot article) recently stopped its bid to recover the X-Box private key citing legal reasons: "Due to legal reasons, we will no longer be hosting or participating in the xbox challenge." DCers.com, a site devoted to distributed computing sheds some light on Neo's sudden flip-flop with a blurb claiming that: "... many legitiment DC'ers that have been working this project since it started that have decided to quit because of the new Neo client that also tries to crack the X-Box encryption." and that they believed this might ultimately kill The Neo Project."

$kr1p7_k177y wrote to us regarding Daniel Swan's release of the comp.os.linux.security FAQ. It's what you'd imagine, but with the growth lately, this should be helpful tool. There's also an interview with him that sheds more light on the reasons behind the FAQ.

Buckaroo writes: "Interesting article at EETimes on what Intel's architects originally had in mind for the P4 - 1 slow ALU, 2 fast ALUs, 2 FPUs, 16K of L1 cache, 128K of L2 cache, 1 MB of external L3 cache, etc. - It was all too big and hot, so a bunch of it got the chop." This article sheds new light on the reasons behind performance problems with the chip.

Cliff Lampe sheds light again on a subject you may be all too aware of whenever you open a desk drawer: complexity. Specifically, this review of Harnessing Complexity, which Cliff assures us is not of the "shallow business guru" variety, sounds like a great way to get a bird's eye view of a fascinating topic.

Ben Green says, "First of all, I want to thank Robin Miller, Hemos, and CmdrTaco for giving me the opportunity to participate in this discussion. Slashdot has been a great resource for me both professionally and recreationally, since I started at Gore 2000."

Tal Cohen has taken a close look at Douglas R. Hofstadter's Godel, Escher, Bach -- 20th Anniversary Edition. He's returned to the book to try and explain what the book is really about-using a new foreword. Definitely a book worth checking out - click below to read more.