Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

gnat (29)

gnat
  (email not shown publicly)

Journal of gnat (29)

Monday February 03, 2003
03:59 PM

Mono wrapper

[ #10372 ]
Sterling Hughes has written PHP wrapper for Mono. Very cool!

<?php
$Console = new Mono('System.Console');
$Console->WriteLine('Hello World');
?>

Where's the Perl equivalent? I want to write off .NET, but I keep hearing good things about the .NET web forms interface. And it's always wise to keep up with Miguel. (As if anyone could keep up with Miguel!)

--Nat

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Writing off .NET (Score:4, Insightful)

    by ziggy (25) on 2003.02.03 16:19 (#16674) Journal
    I want to write off .NET, but I keep hearing good things about the .NET web forms interface.
    It's been about 2.5 years since .NET was announced, and I have yet to see why we need something like it. In many ways, .NET is simply a glitzier name for C#, and C# is nothing more than Java rethought (with better libraries). A large portion of the original promise is unrealized and will continue to remain so for a very long time.

    Among the big goals for .NET was the idea of a "common language runtime". I can see the need for bridging a compiled language and a dynamic language in the same project, but I can't see the need for multiple dynamic languages in one project/application, or contorting many languages into the moral equivalent of C# with differently flavored syntactic sugar.

    Most of the benefit that .NET promises is available today (and was available 3-5 years ago) as web services (XML-RPC, SOAP, REST, roll-your-own, or UltraOmniSuperHypedML). That's attacking the same problem from a different direction, and it is gaining a lot more adoption, mindshare and traction. No, it's not pretty, but it is functional, and it is here and solving problems today.

    Even the .NET webloggers on oreillynet admit that there may not be a good reason to use .NET today, unless you're rewriting an existing project and want to take advantage of some new whiz-bang feature.