tag:blogger.com,1999:blog-11295132.post113770050947101208..comments2024-02-24T01:46:31.188-08:00Comments on A Neighborhood of Infinity: Eleven Reasons to use Haskell as a Mathematiciansigfpehttp://www.blogger.com/profile/08096190433222340957noreply@blogger.comBlogger15125tag:blogger.com,1999:blog-11295132.post-3008335464574775192014-06-14T13:41:59.914-07:002014-06-14T13:41:59.914-07:00There are only two hard problems in Computer Scien...There are only two hard problems in Computer Science: cache invalidation, naming things, and off-by-one errors.Rayhttps://www.blogger.com/profile/06695198078418928146noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-62230890398081517972012-07-06T22:31:26.558-07:002012-07-06T22:31:26.558-07:00Did you find anything interesting in your investig...Did you find anything interesting in your investigation of the relationship between elliptic functions and modular forms? :)elhombrenoreply@blogger.comtag:blogger.com,1999:blog-11295132.post-27366231232423323902010-07-02T13:58:08.139-07:002010-07-02T13:58:08.139-07:00Typo: singled out element, the >>identitiy&l...Typo: singled out element, the >>identitiy<<Vaghttps://www.blogger.com/profile/05936282034517218281noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-45252836744133327622009-08-18T13:32:42.097-07:002009-08-18T13:32:42.097-07:00I think I should adopt the rule of always releasin...I think I should adopt the rule of always releasing my first draft. It may have a few typos but that's fine. When you go back to fix typos you start working locally rather than globally and you introduce structural errors. Have two threes is a good example of that :-)sigfpehttps://www.blogger.com/profile/08096190433222340957noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-3674906289878820302009-08-18T13:23:08.836-07:002009-08-18T13:23:08.836-07:00Two threes ... See? That's what happens when y...Two threes ... See? That's what happens when you break the prime number list rule.<br /><br />Less importantly, I'm going to have a deeper look at Haskell because of this well-argumented post.Sebastiannoreply@blogger.comtag:blogger.com,1999:blog-11295132.post-24057500073995860722009-08-17T23:12:41.971-07:002009-08-17T23:12:41.971-07:00Nice post! Thanks for writing it!
ps. recusrion -...Nice post! Thanks for writing it!<br /><br />ps. recusrion -> recursionshaprhttps://www.blogger.com/profile/15312354728640161096noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-13419001301009967162009-03-03T04:53:00.000-08:002009-03-03T04:53:00.000-08:00As one of the original authors of Macaulay, you ha...As one of the original authors of Macaulay, you had me at "hello"!<BR/><BR/>I've been teaching Haskell to anyone I can. With my student the other day, we wrote a screenful of one-liners (leavened by comments and type declarations) that reverse-search atomic lattices represented as bitfields. The result: Code that could find all instances on 5 atoms in a quarter second (Macaualay2 could only handle 4 atoms) and all 2^36 or so instances on 6 atoms in 14 hours. That's an instance per bit on my 8 GB linux box, all the while using a memory footprint measured instead in MB.<BR/><BR/>So Haskell can mix it up at the machine level with the best of them. With its lazy functional overhead, Haskell is often slower than C, step by step, but its conceptual clarity allows one to effortlessly combine steps to form algorithms that would be way too painful to write in procedural languages. People mired in language efficiency debates haven't moved on yet; I don't bother with the mere constant improvements of strictness annotations or overclocking my hardware, I instead look for better algorithms.<BR/><BR/>How efficiently does a language mind-meld with its user? That's the whole ball of wax. I'm in my 50s; if one could reject the language debate static and accept this principle in one's 20s, one would be way ahead.<BR/><BR/>As an engine author, I'd reverse your "giant engine" comparison. All languages and packages pick their engine and tune it. Macaulay2 optimizes Grobner bases, Prolog optimizes unification. Lisp optimizes the lambda calculus, while logicians have since moved on to merge the lambda calculus with type and category theory. This is the engine that Haskell optimizes; look under the hood of GHC Haskell, and one sees the biggest engine of them all, written by the best programmers of them all. Haskell made a better choice of domain for its engine.<BR/><BR/>Oh yeah, Integers are easy to use, but 32-bit Ints pervade the basic libraries. We're lucky we wrote "length64" on a hunch before our 14 hour run; the standard version would have overflowed.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-11295132.post-82231772416316697262009-01-13T15:04:00.000-08:002009-01-13T15:04:00.000-08:00@Jake: Really, you find letters less finite than ...@Jake: Really, you find letters less finite than numbers?L Shttps://www.blogger.com/profile/10866289941226429119noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-49857304597709231642007-09-28T23:35:00.000-07:002007-09-28T23:35:00.000-07:002, 3, whatever, who cares about that.This post is ...2, 3, whatever, who cares about that.<BR/><BR/>This post is a very good resource for those interested in learning "those" details about programming languages that can make the difference and avoid missing a lot of time in the search for the appropiate one.<BR/><BR/>This information is totally worthy. :)<BR/>I'm considering learning Haskell...Davhttps://www.blogger.com/profile/05517649216535537358noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-23141498728976185452007-07-02T08:23:00.000-07:002007-07-02T08:23:00.000-07:00Joe/Jake,Tell that to the number theorists.Joe/Jake,<BR/><BR/>Tell that to the number theorists.sigfpehttps://www.blogger.com/profile/08096190433222340957noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-86439834151436295132007-07-02T08:21:00.000-07:002007-07-02T08:21:00.000-07:00@ lemmingmathematician's don't work with numbers, ...@ lemming<BR/><BR/>mathematician's don't work with numbers, we work with letters.<BR/><BR/>Numbers are far to finite for us flighty math folk. We leave them to the Accountants and Statisticians.<BR/><BR/>~~JoeJoe Fredettehttps://www.blogger.com/profile/07170469679136904832noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-31065484406054131602007-06-26T14:57:00.000-07:002007-06-26T14:57:00.000-07:00"I think there's a rule against making lists with ..."I think there's a rule against making lists with prime numbers of elements but I'm ignoring it."<BR/><BR/>Counter-example: how about the (presentation) rule of three? See http://www.presentationhelper.co.uk/presentation_rule_of_3.htmAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-11295132.post-3810645893888973972006-11-22T05:17:00.000-08:002006-11-22T05:17:00.000-08:00There are three kinds of mathematicians:
Those who...There are three kinds of mathematicians:<br />Those who can count and those who cannot.lemminghttps://www.blogger.com/profile/00724887803871304225noreply@blogger.comtag:blogger.com,1999:blog-11295132.post-77460100966797384372006-11-15T02:05:00.000-08:002006-11-15T02:05:00.000-08:00Apparently Haskell's Num is so bad, there are two ...Apparently Haskell's Num is so bad, there are two threes. :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-11295132.post-1162687390909300022006-11-04T16:43:00.000-08:002006-11-04T16:43:00.000-08:00I appreciate this is tediously pedantic, but you m...I appreciate this is tediously pedantic, but you might want to count those reasons again.matthttps://www.blogger.com/profile/17613815121791429722noreply@blogger.com