Live data from Hacker News

Version 11 of Mathematica

blog.wolfram.com

91–100 of 106 posts

Re: Version 11 of Mathematica

#91
post #24

Earlier quoted context omitted.

> An open question independent of the author: What do people use Mathematica for that can't be done in R, SAS, Matlab, SPSS or Python libraries. All those don't offer a seamless environment, that's hassle free, easy to setup, with commercial support, a great GUI, great documentation and works across so many science domains and with different approaches. So, the question is quite (but not that severely) like "what peo…

We (see https://cloud.sagemath.com ) and others (e.g., https://www.continuum.io/ ) do offer commercial support for Python (etc.) and an easy to setup environment. Of course, Matlab is also commercially supported by Mathworks, and it seems that R is now commercially supported by Microsoft ( https://www.microsoft.com/en-us/cloud-platform/r-server ). [Edit: added Microsoft]

and an easy to setup environment.

Hardly so[1] --especially for general/non-technical users.

[1] http://doc.sagemath.org/pdf/en/installation/installation.pdf

Re: Version 11 of Mathematica

#92
post #54

Earlier quoted context omitted.

Mathematica is kind of the opposite of "the bleeding edge". If you want the latest algorithms, statistics, etc., those will be found in R, C++, Python etc. in the author's website. If you want well-tested, mostly-robust algorithms, those (might) be in Mathematica; they follow innovation, rather than leading it. Mathematica also has some algorithms from the 70's and 80's that aren't widely available as open source, an…

>> some algorithms from the 70's and 80's that aren't widely available as open source What would be those (if you got a minute)?

I was thinking of symbolic integration when I wrote that, but there are also the various numerical solvers and special functions. Honestly though I'm not sure, I never really got into that part of it.

Re: Version 11 of Mathematica

#93

Earlier quoted context omitted.

Mathematica is kind of the opposite of "the bleeding edge". If you want the latest algorithms, statistics, etc., those will be found in R, C++, Python etc. in the author's website. If you want well-tested, mostly-robust algorithms, those (might) be in Mathematica; they follow innovation, rather than leading it. Mathematica also has some algorithms from the 70's and 80's that aren't widely available as open source, an…

>> The part I've found most useful has been Wolfram|Alpha; it's really nice to be able to say "August 2, 2016 - September 4, 2017" and get back the number of days, weeks, and hours between those two times. In Python: import datetime # standard module timedelta = datetime.datetime(2016, 8, 2) - datetime.datetime(2017, 9, 4) timedelta.days > -398 timedelta.days / 7 > -57 timedelta.days / 7. > -56.857142857142854 timede…

Add a parser (so I can say "August" or "Aug" instead of 8) and I might start using it (just because the Wolfram|Alpha page loads so slowly).

For example something like this: https://dateparser.readthedocs.io/en/latest/

Importing packages every time I want to use them is rather tedious though. I guess I need PYTHONSTARTUP as well.

Overall, though, 10 minutes to setup something I only use once or twice a year seems like a waste.

Re: Version 11 of Mathematica

#94
post #88

Earlier quoted context omitted.

>> The part I've found most useful has been Wolfram|Alpha; it's really nice to be able to say "August 2, 2016 - September 4, 2017" and get back the number of days, weeks, and hours between those two times. In Python: import datetime # standard module timedelta = datetime.datetime(2016, 8, 2) - datetime.datetime(2017, 9, 4) timedelta.days > -398 timedelta.days / 7 > -57 timedelta.days / 7. > -56.857142857142854 timede…

Yuck.

It looks a little nicer if you say

    from datetime import datetime, timedelta
But the code already looked pretty good to me.

Re: Version 11 of Mathematica

#95

Earlier quoted context omitted.

>> The part I've found most useful has been Wolfram|Alpha; it's really nice to be able to say "August 2, 2016 - September 4, 2017" and get back the number of days, weeks, and hours between those two times. In Python: import datetime # standard module timedelta = datetime.datetime(2016, 8, 2) - datetime.datetime(2017, 9, 4) timedelta.days > -398 timedelta.days / 7 > -57 timedelta.days / 7. > -56.857142857142854 timede…

Add a parser (so I can say "August" or "Aug" instead of 8) and I might start using it (just because the Wolfram|Alpha page loads so slowly). For example something like this: https://dateparser.readthedocs.io/en/latest/ Importing packages every time I want to use them is rather tedious though. I guess I need PYTHONSTARTUP as well. Overall, though, 10 minutes to setup something I only use once or twice a year seems lik…

No need to, already included (though I'm not so familiar with the datetime module, so I had to look for it):

    datetime.datetime.strptime("Aug 18 2015", "%b %d %Y")
    > datetime.datetime(2015, 8, 18, 0, 0)
Like xapata said, if you import from datetime, it looks "nicer". I prefer to see where things come from most of the time, because I keep open long sessions and it can become messy otherwise.

I don't really see how this can take 10 minutes to setup. You can have the import already in a file called dateutils.py and you only set it up once:

    import datetime
    def string2date(val):
        return datetime.datetime.strptime(val, "%b %d %Y")
Then your session becomes easier

    from dateutils import *
    string2date("Jul 4 1776")
    datetime.datetime(1776, 7, 4, 0, 0)
However, I think at this point we're talking more about our personal preferences for tools rather than the original subject. It just struck me that your example was something that is available in Python using standard library modules.

Re: Version 11 of Mathematica

#96
post #9

I recommend that Stephen Wolfram skeptics read this press release. I was surprised by language-level support for 3D printing: In Version 11 it’s finally realistic to take any 3D plot, and just 3D print it. I didn't know that I wanted this until I saw it. Generally I prefer small, simple languages. But Mathematica is my favorite large language. I'm also happy that, even though Mathematica 11 introduces flashy features…

> Generally I prefer small, simple languages. I would argue that MMA is a small language hiding behind a gigantic, domain-specific library.

The thing is, the entire standard library is in the default namespace. I personally dislike that, but then again, I was raised on python.

Re: Version 11 of Mathematica

#97

I do wonder if they have ever thought of building a Mathematica Machine like the old Lisp and Smalltalk machines?

Lisp Machines had already something like Mathematica.

It's called Macsyma and existed long before Mathematica. Macsyma was ported to Lisp Machines, in fact Lisp Machines exist partly because of Macsyma. It was one of the early Lisp applications which needed better and dedicated (not timeshared) hardware.

http://lispm.de/macsyma/macsyma.html

Re: Version 11 of Mathematica

#98
post #96

Earlier quoted context omitted.

> Generally I prefer small, simple languages. I would argue that MMA is a small language hiding behind a gigantic, domain-specific library.

The thing is, the entire standard library is in the default namespace. I personally dislike that, but then again, I was raised on python.

For those that haven't used Mma, the uppercase/lowercase convention helps a lot here. Built in functions start with uppercase letters, like LinearProgramming. You should name your functions with a lowercase letter. So the namespace is messy, but you're never going to accidentally collide with a built in name.

Re: Version 11 of Mathematica

#99

Earlier quoted context omitted.

Add a parser (so I can say "August" or "Aug" instead of 8) and I might start using it (just because the Wolfram|Alpha page loads so slowly). For example something like this: https://dateparser.readthedocs.io/en/latest/ Importing packages every time I want to use them is rather tedious though. I guess I need PYTHONSTARTUP as well. Overall, though, 10 minutes to setup something I only use once or twice a year seems lik…

No need to, already included (though I'm not so familiar with the datetime module, so I had to look for it): datetime.datetime.strptime("Aug 18 2015", "%b %d %Y") > datetime.datetime(2015, 8, 18, 0, 0) Like xapata said, if you import from datetime, it looks "nicer". I prefer to see where things come from most of the time, because I keep open long sessions and it can become messy otherwise. I don't really see how this…

A coworker noted that dateparser[0] is a strong module for this use case.

[0] https://pypi.python.org/pypi/dateparser

Re: Version 11 of Mathematica

#100

Somehow the mixing of computation and data sources makes me uneasy. In classical Mathematica, you could be pretty sure that computations with future versions would give the same output. Now what happens when, for example, the average size of an egg increases over time, and then with version 12 the data is updated, and suddenly your notebooks give different results when you rerun them. Also, where does the data come f…

But how is that different from having a program that pulls data from an external API or an URL? What if the data changes, the API breaks backwards compatibility or the site just goes offline?

This stuff is packaged nicely, but it's really just another API…

Post reply on HN