Since the initial Lambda proposal was released (and the in-depth InfoQ analysis), there has been a subsequent state of the lambda which has significantly moved the goalposts of the lambda project in JDK 7. Read on to find out what's new.
LESS and Sass are Ruby tools that allow to reduce redundancy in CSS files by introducing variables, mixins, and other time proven language features into CSS. We take a look at how the two tools work and what they offer.
Ola Bini, a core JRuby developer and author of the book Practical JRuby on Rails Projects, has been developing a new language for the JVM called Ioke. This strongly typed, extremely dynamic, prototype based object oriented language aims to give developers the same kind of power they get with Lisp and Ruby, combined with a nice, small, regular syntax.
Smalltalk, a language that has had a big influence on Ruby, is making a comeback. We take a look at the current situation and talk to Randal L. Schwartz about Smalltalk.
A look at what to watch out for in metaprogramming when it comes to speed, and: how ParseTree can be used to implement LISP/Scheme-style Macros in Ruby and avoid some of the issues of Open Classes.
Style enforcement has long been a hotly debated topic. Not only are their arguments over what style a team should standardize on, but also on whether or not there should be a standard style at all. In a move that is sure to add fuel to the flames, Microsoft has released StyleCop, the style enforcement tool they use internally.
C# 3 added the keyword "var". This allows for local type inference when the compiler can unequivocally determine what type the variable should be. There is, however, some debate as to when it should be used.
Collection initializers were supposed to be released along with LINQ in C# 3 and VB 9. While C# did get them, they were cut from the VB release. Part of the reason was the Visual Basic team wanted to make VB's version more powerful. We present the leading options for the new syntax.
Line continuation characters have always been a wart on the VB syntax. Unlike languages in the Pascal and C families, Visual Basic does not require a trailing semi-colon to denote the end of a statement. The trade-off for this is that it does need a character to indicate when the statement does not end. Paul Vic is proposing to eliminate continuation characters in most common cases.