InfoQ Homepage Languages Content on InfoQ
-
.NET 4.0 Brings XAML 2009, but Not for WPF Users
At PDC 2009, Michael Shim and Rob Relyea presented Microsoft’s plans for the future of XAML. Long term, they plan on unifying the various XAML languages and parsers, but for now developers will only get XAML 2009 for non-UI technologies like Workflow Foundation. The new parser, on the other hand, will bring new functionality to everyone who needs to analyze, manipulate, or generate XAML.
-
JDK 7 Milestone 5 Includes Concurrency and Performance Updates, But Is Not Feature Complete
Sun's Java SE team recently released the Milestone 5 build of JDK 7. This was expected to be a feature complete release of Java 7 but is some way short of that. InfoQ takes a look at what has been added and some of the major features still missing.
-
Mark Reinhold on Closures for Java
Following on from last week's surprise announcement at Devoxx that Sun would be adding closures to Java, Mark Reinhold has published a blog entry providing more background to the decision.
-
Evented I/O for Javascript with Google V8-based Node.js
Node.js allows scalable ѕtandalone Javascript server programs by bundling Google's V8 with libraries for event-based I/O. InfoQ takes a look at what makes Node.js tick.
-
JDK 7 Unexpectedly Gets “Simple” Closures, but is Pushed Back to End of 2010
During his Devoxx talk, Mark Reinhold has announced that JDK 7 will have Closures. With the inclusion of this much debated feature, JDK 7 schedule will be extended until around September 2010.
-
Proposal: A Compromise on Using Dynamic in C#
Jeffrey Palermo, CTO of Headspring Systems, proposes a compromise in using dynamic for C#: the ability to make an entire method dynamic while keeping assemblies static.
-
Google Experiments with a New Language, Go
Go is a Google experimental open source new language resembling C but adding features like reflection, garbage collector, dynamic types, concurrency, and parallelism.
-
Writing New .NET Languages with Irony
Irony is a framework created by Roman Ivantsov and used to write internal DSLs or entire new languages that run on .NET, the grammar being written in C#.
-
IronScheme Nears Final Release
IronScheme, the R6RS implementation of Scheme for DLR, has reached RC1 after one year of being in beta.
-
Sun Drops the Swing Application Framework from Java 7
The Swing Application Framework will not make it into Java 7, though a number of forks have subsequently sprung up to continue its development. Plans for another much requested feature, CSS-based styling for Swing components, have also been abandoned.
-
State of Python on the JVM
In the past year or so Python has really been gaining a lot of traction on the JVM, thanks to the recent advancements of Jython. In this news item we'll talk to the Jython project lead about Jython and the state of Python on the JVM.
-
JDK 7: What Frequently Rewritten Methods Should be Included in java.util.Objects?
In preparation for the arrival of a new class in JDK7 called java.util.Objects which will contain frequently-written utility methods, Joe Darcy of Sun has put out a request to the OpenJDK core-libs-dev group for ideas on what methods should be contained in this class. InfoQ would like to pass this request along to the wider Java community.
-
The Scheme Language Is to Be Split in Two
The Scheme Steering Committee is proposing the split of the Scheme language in two which temporarily are called Small Scheme and Large Scheme.
-
Can the Simple Module System save JSR294?
Over the past month there has been a lot of debate on the current state of the Java Modularity working group (JSR 294). Although the JSR tries to find common ground between different module systems (notably Sun's Project Jigsaw and OSGi), the current set of proposals are overly complex and introduce the world's first concept of a meta-module system. Can the Simple Module System save JSR294?
-
Call Native Code From Your Android Applications
Responding to a call from developers, the Android Native Developer Kit (NDK) now supports calling native code in the Dalvik virtual machine. CPU-intensive operations that don't allocate much memory may benefit from increased performance and the ability to reuse existing code. Some example applications are signal processing, intensive physics simulations, and some kinds of data processing.