The Artima Developer Community
Sponsored Link

Weblogs Forum
Things I Learned at QCon

16 replies on 2 pages. Most recent reply: Dec 10, 2008 10:41 AM by Elizabeth Wiethoff

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 16 replies on 2 pages [ « | 1 2 ]
Raoul Duke

Posts: 127
Nickname: raoulduke
Registered: Apr, 2006

Re: Things I Learned at QCon Posted: Dec 8, 2008 3:20 PM
Reply to this message Reply
Advertisement
> As far as maintenance goes I agree it's harder to maintain
> the same LOC in Python but for the exact same reason. The
> code is of greater density and the way different types
> interact is less predictable due to various customizations.

ja, for me, personally speaking, in my own leetle world here, i think a team which knew how to use a good statically typed language that had decent type inference (SML, O'Caml, Haskell, Scala, QI2, heck perhaps even Erlang with Dialyzer) would do better imhumbleo even at the prototyping stage. but maybe i'm just crazy.

Elizabeth Wiethoff

Posts: 89
Nickname: ewiethoff
Registered: Mar, 2005

Re: Things I Learned at QCon Posted: Dec 10, 2008 10:41 AM
Reply to this message Reply
> http://www.letmegooglethatforyou.com/?q=qcon

Cute, but gah! For the Javascript averse, http://www.google.com/search?q=qcon

> the http://qcon.infoq.com/ site consists of marketing
> verbiage that provides no information about what
> actually differentiates it from XCon, YCon, or ZCon.)

QCon is organized by InfoQ, not InfoX or InfoY or InfoZ. :-) I'm guessing 'Q' stands for 'queue', if anything.

> in Python ... the way different types interact
> is less predictable due to various customizations.

At least it's more predictable than Ruby, on account of Python classes and modules being less "open" and a cultural aversion to opening things up at the drop of a hat. (!) Combine Python's not-so-openness with pydoc output being more intelligible than rdoc output (even without docstrings), and Python's easier for another developer to follow and digest. IMNSHO, grumble, grumble.

> i think a team which knew how to use a good statically
> typed language that had decent type inference (SML,
> O'Caml, Haskell, Scala, QI2, heck perhaps even Erlang
> with Dialyzer) would do better imhumbleo even at the
> prototyping stage.

I'm enjoying reading Expert F#, even though I have no Windows machine.

Flat View: This topic has 16 replies on 2 pages [ « | 1  2 ]
Topic: JavaPosse Roundup 2009 Dates Set Previous Topic   Next Topic Topic: Speaking at a Castle in Denmark


Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2017 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use - Advertise with Us