Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Jan 26, 2007
With the extensive functionality added to support LINQ, many people have been asking if C# and VB are becoming functional languages. Mads Torgersen, C# Language PM, answers this question in his article by the same name.
The first area he addresses is expression-orientated constructors. By allowing any property to be set in the constructor, developers can easily compose nested constructors. Currently the class's author has to guess which properties the developer may want to set during initialization, and without optional parameters, these lists could become quite long.
The next area is value-based programming, an area that Mads admits C# is still weak in. While writing immutable types is possible, there is some overhead such as manually overloading the hash code and equality operators.
With anonymous types, C# and VB get one-step closer to true dynamic typing. They are not there yet, but at least you do not have to create so many trivial classes.
Pattern matching and tuples are two more areas that you will not be seeing in C# any time soon. You will however see extended support for C#'s anonymous functions and lambda expressions. There is even a way to curry functions, though as Mads says, "it ain’t pretty".
Finally, C# will support type inference. Besides making anonymous types possible, type inference can significantly reduce the amount of redundant code a developer has to write. This is one reason why dynamic typing has been praised so much recently. But unlike true dynamic typing, the compiler still outputs statically checked early bound code.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Transforming Software Delivery: An IBM Rational Case Study
Getting Started with Stratos - an Open Source Cloud Platform
As a java developer I have to say; c# is leading the way.
Hopefully java will follow.
I never realized that Microsofts interest in functional programming is tied to the usefulness of functional programming in parrallel programming. The multicores are coming...
If you really want to see where Microsoft is going with all this, take a look at PLINQ. PLINQ talk at DAMP
You can also watch for more PLINQ articles from InfoQ at www.infoq.com/PLINQ/.
I have tried in 2005 to sketch here the overall move of Java, C#, their future and the relationships with functional languages. This sketch is still online with reality. It give also hints about multi-core perspective and the Java/C# move to functional languages.
And into another post, more ramblings on programming languages, I have tried too to give more thoughts about this move, and reasons why such "exotic" languages, like functional languages, have NO intrinsic performance problems.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
3 comments
Watch Thread Reply