Re:Mending the Bitter Absence of Reasoned Technical Discussion
by trapper on Sunday April 05, 2009 @07:44PM
(#547921)
Explain with examples?
[ Parent
| on HN ]
Re:Mending the Bitter Absence of Reasoned Technical Discussion
by ankhmoop on Sunday April 05, 2009 @09:23PM
(#548045)
What technical limitation prevents a language from being fast, easy to use, and well designed? Alex seems to argue that Scala is 'fast, good, and easy', and I would tend to concur.
What I've seen of C# 3.0 and F# also implies that those languages could meet this criteria, but my experience with them is limited.
Re:Mending the Bitter Absence of Reasoned Technical Discussion
by trapper on Monday April 06, 2009 @07:37AM
(#548688)
Software engineering is about tradeoffs. I'll take that a step further: everything is about tradeoffs. You can always optimise for one use case to the exclusion of the others.
Are you saying that fortran isn't faster than scala/jvm based languages? That APL isn't better for matrice's? That lisp macros aren't more powerful? Or that php isn't simpler than scala?
Being good at all three may be possible, but being optimal at all three is probably impossible.
Re:Mending the Bitter Absence of Reasoned Technical Discussion
by ankhmoop on Monday April 06, 2009 @02:35PM
(#549329)
"Being good at all three may be possible, but being optimal at all three is probably impossible."
Why?
Re:Mending the Bitter Absence of Reasoned Technical Discussion
by ankhmoop on Friday April 10, 2009 @03:29AM
(#555831)
"Multi-objective optimization (or programming),[1][2] also known as multi-criteria or multi-attribute optimization, is the process of simultaneously optimizing two or more conflicting objectives subject to certain constraints."
Note "conflicting objectives". Why do you believe the objectives are conflicting?