Comments on: Static Languages: Rationalizations and Myths

By: Yaws « No sé cómo llamar a este blog

Yaws « No sé cómo llamar a este blog — Sun, 23 Mar 2008 21:58:51 +0000

[...] me ha llevado a este artículo, que es realmente interesante de por sí. Pero la cuestión es que me ha hecho saber sobre Yaws, un [...]

By: Tom Davies

Tom Davies — Thu, 14 Feb 2008 02:54:28 +0000

@Mark Snyder — I completely agree with your 3 points, EXCEPT that “static typing really encumbers development during the prototyping phase, when the shape of key abstractions is in flux”. For me, static typing is especially valuable when things are changing fast, and I want to have my key abstractions as explicit structures, not buckets of random name/value pairs.

By: Tim Ewald

Tim Ewald — Mon, 11 Feb 2008 02:11:29 +0000

Steve,

I loved this post. I’ve been using Ruby quite a bit lately and I’ve been blown away by how productive it is. I hear a lot of skepticism from some, especially about the issue of scaling to a large project or team. I haven’t done it yet, so I can’t say whether it works or not. But given the productivity boost, it has got to be worth going down the path to see. Hopefully I’ll be able to report on that soon – my team is about to rebuild our site with Rails (moving from ASP.NET).

Tim-

By: chorny

chorny — Sat, 09 Feb 2008 21:56:05 +0000

You can have typesafety in Perl (for basic types requires module from CPAN, for classes – integrated in Perl itself).

By: Patrick Logan

Patrick Logan — Thu, 07 Feb 2008 19:02:00 +0000

Wow. I’ve been flat out fighting the flu for seven days, and come back to this. I’m sick to my stomach all over again.

Bill Burke seems a troll.