Live data from Hacker News

Ask HN: Whatever happened to Wolfram Alpha?

news.ycombinator.com

41–50 of 281 posts

Re: Ask HN: Whatever happened to Wolfram Alpha?

#41
My guess is that it’s a bit too complicated/slow for a lot of ordinary people and too finicky for a lot of technical people.

I’m a frequent Mathematica user and I find almost all of my use cases require several different attempts to get the desired result w/wolfram alpha. Meanwhile, most people who don’t get the right result the first time will probably just give up and not think to rephrase the query.

Re: Ask HN: Whatever happened to Wolfram Alpha?

#42
post #35

1. It's slow, even for simple microsecond computations like log(2). Takes about 5-20 seconds to load a page on my 1Gb fiber connection. Opening Python/SymPy Gamma is much faster for most things. https://gamma.sympy.org/input/?i=log%282%29 2. Every time I use it, a box saying NEW: Use textbook math notation to enter your math. TRY IT pops up over the result, and clicking the X doesn't hide it the next time I search. T…

> Opening Python/SymPy Gamma is much faster for most things.

Is there a way to make it plot multivariate functions? I tried but whenever I enter two variables it says "Cannot plot multivariate function." I've seen many Python packages plotting multivariate functions so I'm convinced it should be possible.

Re: Ask HN: Whatever happened to Wolfram Alpha?

#43
post #35

1. It's slow, even for simple microsecond computations like log(2). Takes about 5-20 seconds to load a page on my 1Gb fiber connection. Opening Python/SymPy Gamma is much faster for most things. https://gamma.sympy.org/input/?i=log%282%29 2. Every time I use it, a box saying NEW: Use textbook math notation to enter your math. TRY IT pops up over the result, and clicking the X doesn't hide it the next time I search. T…

> Takes about 5-20 seconds to load a page on my 1Gb fiber connection

Wolfram Alpha is implemented in Mathematica, which --- to understate the situation --- was never intended as a high performance backend server language. I suspect that's the reason for the bad performance.

"As a result, the five million lines of Mathematica code that make up Wolfram|Alpha are equivalent to many tens of millions of lines of code in a lower-level language like C, Java, or Python." [1]

Sure, there's something to be said for implementing logic in high-level code, but without a plan for lowering that high-level logic to machine code in a way that performs well, you're setting yourself up for long-term pain.

[1] https://blog.wolframalpha.com/2009/05/01/the-secret-behind-t...

Re: Ask HN: Whatever happened to Wolfram Alpha?

#44

I use it regularly. Sometimes it’s broken, and maybe nobody notices but me? :) Their natural language queries for things that I know they know about are amazing. Here are some that I have used recently. You really need to see these results to appreciate them. I wanted to know how tall my daughter might be. 8 year old female 55 lbs http://www.wolframalpha.com/input/?i=8%20year%20old%20female... I wanted to know the nu…

Yeah; I use it for the occasional repeating specialized query, but have never broadened my usage to anything more-general.

Re: Ask HN: Whatever happened to Wolfram Alpha?

#45
post #35

1. It's slow, even for simple microsecond computations like log(2). Takes about 5-20 seconds to load a page on my 1Gb fiber connection. Opening Python/SymPy Gamma is much faster for most things. https://gamma.sympy.org/input/?i=log%282%29 2. Every time I use it, a box saying NEW: Use textbook math notation to enter your math. TRY IT pops up over the result, and clicking the X doesn't hide it the next time I search. T…

> Takes about 5-20 seconds to load a page on my 1Gb fiber connection Wolfram Alpha is implemented in Mathematica, which --- to understate the situation --- was never intended as a high performance backend server language. I suspect that's the reason for the bad performance. "As a result, the five million lines of Mathematica code that make up Wolfram|Alpha are equivalent to many tens of millions of lines of code in a…

I doubt the bad performance is due to evaluating expressions itself. If I type N[Log[2]] into Mathematica, it evaluates in less than a millisecond. It's probably because Wolfram Alpha is using natural language process to try to process my query and then finally deciding that by N[Log[2]], I mean N[Log[2]]. And it's probably not because of that, but because their grid scheduler isn't optimized for sub-second latency.

Re: Ask HN: Whatever happened to Wolfram Alpha?

#46
post #35

1. It's slow, even for simple microsecond computations like log(2). Takes about 5-20 seconds to load a page on my 1Gb fiber connection. Opening Python/SymPy Gamma is much faster for most things. https://gamma.sympy.org/input/?i=log%282%29 2. Every time I use it, a box saying NEW: Use textbook math notation to enter your math. TRY IT pops up over the result, and clicking the X doesn't hide it the next time I search. T…

> Opening Python/SymPy Gamma is much faster for most things. Is there a way to make it plot multivariate functions? I tried but whenever I enter two variables it says "Cannot plot multivariate function." I've seen many Python packages plotting multivariate functions so I'm convinced it should be possible.

I don't think so. You'd need to run it in a terminal with something like

    from sympy.plotting import plot3d
    x,y=symbols('x y')
    plot3d(x*y, (x, -10,10), (y, -10,10))

Re: Ask HN: Whatever happened to Wolfram Alpha?

#47
post #35

1. It's slow, even for simple microsecond computations like log(2). Takes about 5-20 seconds to load a page on my 1Gb fiber connection. Opening Python/SymPy Gamma is much faster for most things. https://gamma.sympy.org/input/?i=log%282%29 2. Every time I use it, a box saying NEW: Use textbook math notation to enter your math. TRY IT pops up over the result, and clicking the X doesn't hide it the next time I search. T…

Your Internet bandwidth is not relevant when talking about a compute-heavy backend like this. Wolfram|Alpha is not going to load any faster on a 1Gbps connection than it will on a 20Mbps connection, other than some static assets, but even that isn't going to be hugely noticeable if we're talking about 2ms RTT on fibre vs 8-20ms RTT on cable/DSL. If you're downloading a giant file off a nearby CDN, then sure, 1Gbps fibre is useful. I can max out my 1400Mbps cable connection downloading things this way (it's mind-blowing...), and my latency to my upstream gateway outside of my house is 8ms. But Wolfram|Alpha isn't going to load 40% faster for me than it will for you since it's I/O bound and your end-to-end latency is waiting for the backend to complete your request.

I will say, though, that Wolfram|Alpha could be "optimised" in the sense that it could do less fancy JS and be a simple box with a submit button, like SymPy Gamma.

Re: Ask HN: Whatever happened to Wolfram Alpha?

#48
post #15
post #2

What do you mean? I used it to solve a nasty impedance network for the real and imaginary components yesterday and the solutions were accurate. Edit: Maybe it's just good enough that people treat it as a tool and see no need to market it. It consistently has worked fine-ish for years and is useful at what it does.

My meaning was just that I saw it sometimes referenced on HN, but I haven't seen it mentioned for a while now. Hence my search and results showing 8 years since. I guess what I should be doing is looking at the Alexa ranking of Wolfram Alpha.

[deleted]

Re: Ask HN: Whatever happened to Wolfram Alpha?

#50
post #45

Earlier quoted context omitted.

> Takes about 5-20 seconds to load a page on my 1Gb fiber connection Wolfram Alpha is implemented in Mathematica, which --- to understate the situation --- was never intended as a high performance backend server language. I suspect that's the reason for the bad performance. "As a result, the five million lines of Mathematica code that make up Wolfram|Alpha are equivalent to many tens of millions of lines of code in a…

I doubt the bad performance is due to evaluating expressions itself. If I type N[Log[2]] into Mathematica, it evaluates in less than a millisecond. It's probably because Wolfram Alpha is using natural language process to try to process my query and then finally deciding that by N[Log[2]], I mean N[Log[2]]. And it's probably not because of that, but because their grid scheduler isn't optimized for sub-second latency.

Ha, hearing the word "process" in Wolfram's voice, there.
Post reply on HN