|
|
Re: Things I Learned at QCon
|
Posted: Dec 10, 2008 10:41 AM
|
|
> 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.
|
|
Previous Topic
