On Tue, May 13, 2014 at 3:59 AM, Hendrik Boom wrote:
> On Mon, May 12, 2014 at 10:18:47AM -0400, Matthias Felleisen wrote:
>> You can, and everyone else on this list can:
>>
>> do not use the word 'macro' ever again.
>>
>> Period.
>>
Yet, I have you on record as declaring not so long ago: "my
und
Neil Toronto writes:
> My dissertation is on programming languages for Bayesian analysis, which
> can handle arbitrary, possibly recursively defined models and arbitrary
> probabilistic conditions.
I have only skimmed it until now, but it looks like a very important
step in a direction I lik
Greetings.
On 2014 May 13, at 13:36, Matthias Felleisen wrote:
> This is not a misconception. It's an understanding based
> on spending 15 years next to a top-10 department in scientific
> computing, in a computer science department that was spun off
> from that department, and a huge research
Jay Kominek writes:
> Perhaps you could add a page to the Racket wiki on github, like the
> intro projects page
> (https://github.com/plt/racket/wiki/Intro-Projects) but which
> covers... "Scientific Racket projects"? Divide it up like "machine
> learning", "statistical analysis", "file forma
On 2014-05-12 21:59:07 -0400, Hendrik Boom wrote:
> The world needs a good, flexible, exact garbage collector that can be
> used by a variety of languages. Ideally, its interface to the rest of
> the world should admit of implementations that are just
> stop-and-collect, or stop-and-copy, or multi
On 05/13/2014 10:26 AM, Jay Kominek wrote:
On Tue, May 13, 2014 at 9:35 AM, Konrad Hinsen
I see Racket's strength for scientific computing in a very different
aspect: the possibility to define languages tailor-made for expressing
computational models in some application domain. Scientists gener
Stephen De Gabrielle writes:
> FWIW the http://software-carpentry.org team have done some
> excellent work on teaching scientists how to
> code. 'Data-carpentry' seems to be topical for them (looking
> at the twitter feed).
Software Carpentry is doing a very good job indeed in my biased
opin
On Tue, May 13, 2014 at 9:35 AM, Konrad Hinsen
wrote:
> I have doubts about some points on that list:
>
> - machine learning
For what it's worth, I implemented Pegasos awhile back:
https://gist.github.com/jkominek/1275886
It's intended for SVMs on large datasets (like, read everything once
and
FWIW the http://software-carpentry.org team have done some excellent work
on teaching scientists how to code. 'Data-carpentry' seems to be topical
for them (looking at the twitter feed).
On Tuesday, 13 May 2014, Konrad Hinsen wrote:
> Matthias Felleisen writes:
>
> > > Note however that I di
> - machine learning
I know Dan King did a bit with machine learning in Racket a while ago, but
I have no clue what state its in:
https://github.com/danking/racket-ml
On Tue, May 13, 2014 at 10:35 AM, Konrad Hinsen
wrote:
> Stephen Chang writes:
>
> > > That said, it's interesting to look at
Stephen Chang writes:
> > That said, it's interesting to look at why Python became such a
> > popular language in science.
>
> Coincidentally, I just read this article:
> http://www.talyarkoni.org/blog/2013/11/18/the-homogenization-of-scientific-computing-or-why-python-is-steadily-eating-oth
Matthias Felleisen writes:
> This is not a misconception. It's an understanding based
> on spending 15 years next to a top-10 department in scientific
> computing, in a computer science department that was spun off
> from that department, and a huge research group in the latter
> that support
On Tue, May 13, 2014 at 09:53:27AM +0200, Konrad Hinsen wrote:
> Matthias Felleisen writes:
>
> > > Note however that I didn't look at performance, which is not
> > > really important for most of what I do.
> >
> > In hindsight that is obvious from your use of Python :-) It should
> > have c
Hi,
Hear, hear. Let's have GC as part of the OS.
==
Arthur Nunes-Harwitt
Computer Science Department, Rochester Institute of Technology
Room 70-3509
585-475-4916
==
"I don'
On 05/13/2014 04:59 AM, Sam Tobin-Hochstadt wrote:
On May 13, 2014 3:38 AM, "Konrad Hinsen" mailto:konrad.hin...@fastmail.net>> wrote:
>
> Sam Tobin-Hochstadt writes:
>
> > On Mon, May 12, 2014 at 10:18 AM, Matthias Felleisen
> > mailto:matth...@ccs.neu.edu>> wrote:
> > >
> > >> If th
> That said, it's interesting to look at why Python became such a
> popular language in science.
Coincidentally, I just read this article:
http://www.talyarkoni.org/blog/2013/11/18/the-homogenization-of-scientific-computing-or-why-python-is-steadily-eating-other-languages-lunch/
Not sure if this
This is not a misconception. It's an understanding based
on spending 15 years next to a top-10 department in scientific
computing, in a computer science department that was spun off
from that department, and a huge research group in the latter
that supported the former.
What has changed is the w
On May 13, 2014 3:38 AM, "Konrad Hinsen" wrote:
>
> Sam Tobin-Hochstadt writes:
>
> > On Mon, May 12, 2014 at 10:18 AM, Matthias Felleisen
> > wrote:
> > >
> > >> If the FFI can provide
> > >> C-pointer access to something like a flvector, and ensure that it's
> > >> not garbage-collected f
Matthias Felleisen writes:
> > Note however that I didn't look at performance, which is not
> > really important for most of what I do.
>
> In hindsight that is obvious from your use of Python :-) It should
> have clicked in me, but I am just so used to think "scientific
> computation ~ si
Sam Tobin-Hochstadt writes:
> On Mon, May 12, 2014 at 10:18 AM, Matthias Felleisen
> wrote:
> >
> >> If the FFI can provide
> >> C-pointer access to something like a flvector, and ensure that it's
> >> not garbage-collected for the duration of a C function call, then a
> >> good interface
Hendrik Boom writes:
> > > Making languages with different garbage
> > > collectors work together is such a pain that I am not very motivated
> > > to try. I guess this problem will ensure the survival of C for many
> > > years to come.
> >
> > A student of mine tried twice to integrate Pyt
On Mon, May 12, 2014 at 10:18:47AM -0400, Matthias Felleisen wrote:
>
> On May 12, 2014, at 3:56 AM, Konrad Hinsen wrote:
>
> > Note however that I didn't look at performance, which is not
> > really important for most of what I do.
>
>
> In hindsight that is obvious from your use of Python :-
"Macros" may be evil but "grafts" are perfectly sensible operations on
trees. To hear some tell it, it's the best way to propagate some
low-hanging fruit. Wait, am I mixing metaphors?
On Mon, May 12, 2014 at 12:24 PM, Matthias Felleisen
wrote:
>
> I'll watch from the other side as we wait for t
I'll watch from the other side as we wait for the last "macros are evil"
programmer to die. Oh but we just found a reason in a different thread that
will keep C alive, so perhaps you'll join me there first :-)
On May 12, 2014, at 11:26 AM, Matthew Flatt wrote:
> At Mon, 12 May 2014 11:0
At Mon, 12 May 2014 11:06:11 -0400, Matthias Felleisen wrote:
>
> On May 12, 2014, at 10:58 AM, Matthew Butterick wrote:
>
> >
> > To be fair, that will be difficult given how often the docs refer to the
> m-word ;)
>
>
> Yes, I am losing this battle even with those of my own students who wo
On Mon, May 12, 2014 at 5:06 PM, Matthias Felleisen wrote:
>
> On May 12, 2014, at 10:58 AM, Matthew Butterick wrote:
>
> >
> > To be fair, that will be difficult given how often the docs refer to the
> m-word ;)
>
>
> Yes, I am losing this battle even with those of my own students who work
> on
On May 12, 2014, at 10:58 AM, Matthew Butterick wrote:
>
> To be fair, that will be difficult given how often the docs refer to the
> m-word ;)
Yes, I am losing this battle even with those of my own students who work on
syntactic matters (Matthew, Ryan, and Shriram).
On May 12, 2014, at 7:18 AM, Matthias Felleisen wrote:
>> I agree that the term "macro" should be banned, but I don't think I
>> can contribute much to that.
>
>
> You can, and everyone else on this list can:
>
> do not use the word 'macro' ever again.
To be fair, that will be difficult
On Mon, May 12, 2014 at 10:18 AM, Matthias Felleisen
wrote:
>
>> If the FFI can provide
>> C-pointer access to something like a flvector, and ensure that it's
>> not garbage-collected for the duration of a C function call, then a
>> good interface should be doable.
This is the `f64vector` (or `f3
On May 12, 2014, at 3:56 AM, Konrad Hinsen wrote:
> Note however that I didn't look at performance, which is not
> really important for most of what I do.
In hindsight that is obvious from your use of Python :-) It should
have clicked in me, but I am just so used to think "scientific
computat
Hi Matthias,
Thanks for your comments!
> Hi Konrad, thanks for the post. It is quite illuminating because
> I wouldn't have thought that we're that close to 'performant' in
> this domain.
I was a bit surprised as well, but I found that the math library
is really a pretty good foundation fo
On May 10, 2014, at 8:42 AM, Konrad Hinsen wrote:
given Racket’s academic and teaching background, it is quite possible that
there are lots of students using Racket who find sufficient support locally
that they never manifest themselves on the mailing list.
Separate from the local support
No, it's an idea and nothing else.
On May 11, 2014, at 9:13 PM, Andrew Dudash wrote:
> > We have discussed making the successor of Racket (Racket II)
>
> There's a successor in the works?
>
>
> On Sun, May 11, 2014 at 7:00 PM, Norman Gray wrote:
>
> Matthias, greetings.
>
> This is a m
> We have discussed making the successor of Racket (Racket II)
There's a successor in the works?
On Sun, May 11, 2014 at 7:00 PM, Norman Gray wrote:
>
> Matthias, greetings.
>
> This is a minor tangent to a very interesting thread...
>
> On 2014 May 11, at 22:24, Matthias Felleisen wrote:
>
>
Matthias, greetings.
This is a minor tangent to a very interesting thread...
On 2014 May 11, at 22:24, Matthias Felleisen wrote:
> 3. Well, minor point but when you state that "I am aware of
> only three other languages developed in a similar context:
> OCaml, Haskell, and Scala." please do
On May 10, 2014, at 8:42 AM, Konrad Hinsen wrote:
> Hi everyone,
>
> I just published a blog post about my first experiences with Racket:
>
> http://khinsen.wordpress.com/2014/05/10/exploring-racket/
>
> Comments welcome.
>
> This is also a good occasion to thank everyone on this list who h
Hi everyone,
I just published a blog post about my first experiences with Racket:
http://khinsen.wordpress.com/2014/05/10/exploring-racket/
Comments welcome.
This is also a good occasion to thank everyone on this list who has
helped me by answering questions during the last few months.
Konr
37 matches
Mail list logo
