InfoQ Homepage Development Content on InfoQ
-
New Code Analysis Tool FxCop Beta: 200 bug fixes, anonymous methods support
With over 200 bug fixes and performance improvements, this beta is what many FxCop users have been clamoring for. FXCop checks .NET managed code assemblies for conformance to the Microsoft .NET Framework Design Guidelines. Beyond basic library design and naming convention checks, FxCop is especially valuable in pointing out globalization, interoperability, and security issues.
-
Pattie Maes on Ambient Intelligence
At OOPSLA 2007, Pattie Maes gave an interesting talk about the MIT ambient intelligence projects. One project, ReachMedia, was particularly interesting from an architectural, mashup and social networking perspective.
-
Mozilla Labs announces Prism
On Friday, Mozilla Labs’ announced Prism, their entry into the budding market-trend of platforms for running web applications on the desktop, similar to Adobe AIR.
-
Interview: Jay Fields and Zak Tamsen on Domain Specific Languages
Jay Fields and Zak Tamsen talked with InfoQ about Domain Specific Languages (DSLs), and how they have successfully used them in their projects at ThoughtWorks to empower businesses, reduce development time, and increase the agility of projects.
-
Interview: Joe Walker discusses DWR
InfoQ spoke with Joe Walker at QCon London 2007 about the DWR toolkit. Walker discussed DWR 2.0 including new features such as details about reverse AJAX, the deal with TIBCO, DWR support in IDEs, the integration with Spring, future plans for DWR, and interesting applications of DWR from the very large to the very flashy.
-
Ruby on Mac OS X Leopard with DTrace, XCode and Interface Builder support
The newly released Mac OS X Leopard ships with the Ruby 1.8.6 and various Ruby libraries and tools installed. Leopard also includes DTrace probes for profiling Ruby, XCode and Interface Builder support and more.
-
JavaRebel: Dynamic Classloading in the JVM
JavaRebel brings Ruby and PHP style dynamic reloading of classes to Java. While it currently has several limitations it can speed up development dramatically.
-
Lisp on the .NET Runtime
Continuing our coverage of Lisp, we present some of the efforts underway to port the venerable language to the .NET runtime. Variants we look at include IronLisp, LispSharp, and Common Larceny.
-
MinWin Core: 25MB on Disk and 100 Files
The Microsoft MinWin core is 25MB in size on disk and contains 100 files total. This appears to be a major overhaul of Windows when contrasted with a minimal install of Windows Vista at 4GB on disk and 5000 files in size.
-
Rhino Mocks 3.3 is Ready
The latest version of the very popular mocking framework, Rhino Mocks version 3.3 is complete and ready to be used by your tests. This release provides many new features including Remoting Proxies and more.
-
Presentation: Prototype and Script.aculo.us: spending weekends at home again
Script.aculo.us creator Thomas Fuchs gives an overview about the concepts and functionality of both Prototype and the script.aculo.us libraries, provides advice on what and what not to expect and gives pointers and hints on how to get started.
-
Respect Demeter's Law through Rails Plugin
The Law of Demeter or Principle of Least Knowledge is a design guideline for developing software. It's not rare to see common Rails practices violating it. Luke Redpath brings a way to remedy this by providing Demeter's revenge plugin.
-
Microsoft: Hypercall API extended to Open Specification Promise
Today Microsoft announced its hypercall API will now be included under the Open Specification Promise. Microsoft co-announced with Citrix and Novell.
-
Adobe and the Future of Software
Adobe has been up to some interesting things of late from their work with Adobe Flex, to their efforts on the Adobe Integrated Runtime (AIR), and their recent announcement that they intend to move all of their software to the web in a model know as Software as a Service (SaaS).
-
Crap4J Seeks to Use Algorithms to Determine Code Quality
Despite its humorous name the Crap4J project has a serious goal. The project seeks to define an algorithm using factors such as code complexity and test code coverage to determine the quality of code.