InfoQ Homepage News
-
Ivy 2.0: Released As An Apache Project
Ivy, a tool for managing (recording, tracking, resolving and reporting) project dependencies which provides tight integration with Apache Ant, has released its 2.0 beta version. This is the first release as an Apache project, it brings enhanced compatibility with Maven 2 repositories, improved concurrency support and a few other significant changes.
-
Microsoft: MEDC Cancelled
Microsoft is closing shop on a popular conference targetted at mobile device application developers.
-
Agile Kanban: Visual Tracking Beyond the Team Room
In the beginning Agile was largely a developer-driven initiative, sometimes improving development processes only to find the real bottlenecks lay outside developer control. In his latest InfoQ article, Kenji Hiranabe analyses Lean manufacturing's "Kanban" visual tracking tool, how it differs from the Agile taskboard, and how it helps identify more far-reaching improvements.
-
Understanding Seam Nested Conversations and Timeouts
Jacob Orshalick recently explored Seam's nested conversation model and related timeouts using Seam's demo booking example.
-
Doer vs. Talker: Working Software over Comprehensive Documentation
In Are You a Doer or a Talker? Jeff Atwood of Coding Horror echoes the agile manifesto's 'Valuing working software over comprehensive documentation.' Noting an article by John Taber, Atwood draws parallels between transportation studies and transportation construction projects.
-
Rubinius adds Multi-VM support
Rubinius adds a new feature called "Multi-VM", which allows to run multiple Ruby VMs inside an OS process. We talked with Evan Phoenix of the Rubinius project about the benefits and implementation of this feature.
-
Mike Hankey on Clipboard Programming
One of the corner-stones of Windows is the universal clipboard. Every well-designed application is expected to have at least minimal clipboard support and many are quite sophisticated. Yet the .NET framework doesn't expose all of its functionality directly, making it a mystery to most developers. Mike Hankey seeks to bring it to light with The Code Project article ClipSpy+.
-
Specialized Message Patterns for SOA
Adobe have just published a document on SOA message exchange patterns. It also contains a good primer on SOA principles. Duane Nickull, the chair of the OASIS SOA Reference Model Technical Committee, is a co-author, making this well worth a look.
-
Is the Proprietary Nature of the Flash Player Keeping You From Using Flex?
Per Olesen published a blog recently entitled, Flash is Still Closed Source and Proprietary Technology, where he argues that Flash is still a proprietary platform.
-
Editorial: Selecting a .NET Web Framework
In the past selecting a web framework for .NET languages was a non-issue. Your choice was between pure ASP.NET or a hybrid design that mixed classic ASP with ASP.NET. And even that was seen as a temporary hack rather than a conscious choice. But with the introduction of ASP.NET MVC, .NET developers have to start making the hard decisions.
-
Open Source Flex Development Frameworks Show that Platform is Gaining Momentum
A number of open source development frameworks have sprouted up around Adobe Flex. InfoQ took a moment to identify a few of the major ones.
-
JBoss Rolls Out Developer Studio 1.0 and Tools 2.0
JBoss recently released new versions of their JBoss Developer Studio and JBoss Tools products.
-
JEE 6: Extensibility, Profiles and Pruning
Whilst the public details are still a little sketchy, the general direction of Java EE 6 is becoming apparent and reflects the changing role of the Java EE standard.
-
MarkMail Takes Mailing List Archives to the Next Level
Late last year MarkLogic rolled out MarkMail, a free service for searching mailing list archives based on their MarkLogic XML content server. Currently MarkMail supports Apache.org, Mozilla.org, PHP and MySQL lists. InfoQ sat down with Jason Hunter of MarkLogic to find out more details on site and where it is heading in the future.
-
An Agile Developer's Responsibility
What is a developer's responsibility when a customer asks for a quick and dirty solution? Should they listen to the customer and take the short cut because, after all, they are paying the bill? Should they instead always do what is technically the "best" option in their opinion? Or is there a middle road that should be taken?