All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

How much of that is the interface vs the language?
I think your giving C# too much credit in and of itself, though in the end the C# developer is more agile because of it your right.
Its a loss to Perl that we don't have the interface to do such things (or perhaps other things more worthwhile and fundamental).
Not something that a half-baked eclipse setup or emacs mode fixes obviously. The Visual Studio setup is quite powerful for that side of the fence, even if at times they are abstracting users from t

I think a lot of it is in the language. Perl has grown up and unfortunately it's still in the clothes it wore as a teenager and they don't fit well. Many of the things the C# and Java communities can do work because the languages have a regular syntax and introspection.

Many of the things the C# and Java communities can do work because the languages have a regular syntax and introspection.

Similarly, many of the things the C# and Java communities have to do (in particular, dependency injection governed by voluminous XML configuration files) is because the languages have other inflexibilities.

I think the obvious moral equivalent to static introspection in static languages is dynamic programming (open classes, closures, eval) in dynamic languages. Instead of clicking buttons in an IDE that generates code for you, you write code against an API that abstracts away a bunch of metaprogramming. The difference is that you are not limited by your tools in how far and fast you can go because you can always abstract out further from the basis you start with.