Yet, no mention of concurrency/parallelism primitives. sigh
Modern Language Wishlist
51–60 of 75 posts
Re: Modern Language Wishlist
#52Earlier quoted context omitted.
Is it just me or did anyone else feel he was talking about Go? I have never understood why Go doesnt get the love that it deserves. (No seriously, he described Go)
I think a lot of languages could be described by most of the items on the wishlist. I thought Clojure was an extremely close fit, but then I program a lot in Clojure :) I don't think Go matches all his criteria, though. For instance, Go is not homoiconic.
Re: Modern Language Wishlist
#53hmm, what exactly does he mean by data-oriented programming? iirc that's something where you don't store data chopped up into objects, but have arrays that keep all the data of one "aspect" of all "objects"... or something like that. something game programmers would use, helps avoid cache misses. is that what he was talking about? if so, what does it have to do with macros?
I meant data-driven programming. http://www.faqs.org/docs/artu/ch09s01.html More data (and data structures) and less code. It's very common in Lisps and other homo-iconic languages.
Re: Modern Language Wishlist
#54I'll add one that people don't seem to think about much: the ability to encapsulate an ongoing computation and grab new values from it at leisure. Examples: Haskell has lazy lists; Python has generators; Unix shells have pipes; in Go you can whip this up pretty easily with a goroutine and a channel; etc. Does his ideal language allow for this?
Re: Modern Language Wishlist
#55The most obvious thing I can see that he wasn't explicit about was Unicode support. Should be native, just work and included from day one.
Re: Modern Language Wishlist
#56Most languages have most of the listed features. The most interesting uncommon idea on that list to me is model of time. But only when it allows reversible computing. I don't know how practical that is though. Anyways I've separated out the parts of the list which I think are less common. And listed examples off the top of my head so by no means is the below meant to be exhaustive. The uncommon ones: * Units - F# and…
Re: Modern Language Wishlist
#57Earlier quoted context omitted.
How far is Python from this list? Macros are missing but the remaining list seem close to me.
Math sucks a lot in Python 2.7: 3 / 2 == 1 Python 3 fixes that, thou, but still it uses floating point numbers instead of rational numbers.
import decimal
import fractions
Re: Modern Language Wishlist
#58Most languages have most of the listed features. The most interesting uncommon idea on that list to me is model of time. But only when it allows reversible computing. I don't know how practical that is though. Anyways I've separated out the parts of the list which I think are less common. And listed examples off the top of my head so by no means is the below meant to be exhaustive. The uncommon ones: * Units - F# and…
Most of the features are not hard to find, but you have to switch languages a lot if you want to use them all.
Re: Modern Language Wishlist
#59Most languages have most of the listed features. The most interesting uncommon idea on that list to me is model of time. But only when it allows reversible computing. I don't know how practical that is though. Anyways I've separated out the parts of the list which I think are less common. And listed examples off the top of my head so by no means is the below meant to be exhaustive. The uncommon ones: * Units - F# and…
Also, CLOS (Common Lisp) has after, before and around methods for "aspect oriented".
Re: Modern Language Wishlist
#60Most languages have most of the listed features. The most interesting uncommon idea on that list to me is model of time. But only when it allows reversible computing. I don't know how practical that is though. Anyways I've separated out the parts of the list which I think are less common. And listed examples off the top of my head so by no means is the below meant to be exhaustive. The uncommon ones: * Units - F# and…
Python is not homoiconic but the ast module allows for wicked stuff.
> Error (managing numeric Imprecision)
Python decimal module does not handle precision error but handles significance, so that(from the doc) "for instance, 1.3 * 1.2 gives 1.56 while 1.30 * 1.20 gives 1.5600". This underrated module also does much more.
Anyway I feel this precision stuff might be a job for numpy/scipy.