Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Jonathan Allen on Dec 12, 2006
In order to support LINQ, Visual Basic is adding support for lambda expressions. Lambda expressions are essentially inline functions and are a corner-stone of functional programming languages like Lisp and Haskell. As the next version of Visual Basic edges ever closer, certain syntactical issues need to be addressed.
On Friday, Paul Vick of Microsoft asked developers what syntax they want for this new capability. He presented three options.
The first is a very concise, C#-like syntax.
1: C#-style, "x => x + 1"
The second is more verbose, but also makes it clear that an in-line function is being used.
2: VB-style, "Function(x) x + 1"
Finally there is a mixed style that uses a backslash, because it resembles a lambda, and C#'s => notation.
3: Hybrid-style, "\x => x + 1"
DiegoV has proposed a fourth syntax with some interesting characteristics. It uses the parameter binding operator (:=) and the parameter's name.
4: bar(x):=x+1
Surprisingly #2 seems to be getting the majority of the support right now. As Sriram Krishnan says,
Definitely #2 - one of the things I loved in VB was that I didn't have to rack my heads as to what a cryptic character meant - which I had to do often in Perl
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
The 5 Mandates of Software Development Teams - Presto Manifesto
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Right Collaboration Architecture Drives Business Transformation
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
No comments
Watch Thread Reply