> That's kinda funny. Our revenue per employee is lower than the industry average.
That's true for investment banks too (i.e. lower than comparable management positions in other fields), but this doesn't mean the higher-ups aren't money-hungry egomaniacs. In fact, it can be argued that when the salaries of mid-level employees are low compared to industry norms, that fact may be used to argue that the company is top-heavy, even possibly money-hungry.
> But you can read large swathes of our code by looking in the right place in the installation.
This is misleading. One can read all sorts of user-level script code, but no source code at all. It's not an accident, and it explains why Mathematica cannot be used in serious mathematical work, work meant for technical and scientific publication and peer review.
Read my post again: revenue / employee, not salary / revenue.
> One can read all sorts of user-level script code, but no source code at all.
What? Probably half of the Wolfram Language is written in the Wolfram Language. How is top-level code not source code?
> it explains why Mathematica cannot be used in serious mathematical work, work meant for technical and scientific publication and peer review.
You keep saying that... I think the truth is more subtle. A tool like Mathematica might play a crucial role in some result, but the proof or result itself doesn't a priori need to rest on any black box software at all to be reproducible.
A nice family of examples would be the class of NP problems, for which the discovery might have been difficult, and achieved via proprietary tools, but the verification is possible via open-source tools or with direct human insight.
And that's not even considering physics, biochemistry, engineering, and astronomy, where many of the tools you use will always be expensive and built by industry, and have no impact on peer review. Especially if they are a means to visualizing data to generate hypotheses, or processing or wrangling data into a tractable form.
I can write BASIC code all day long without having access to the engine, the interpreter. But if I publish my result, there will be problems.
Also, if the language under discussion were so open, people would write third-party imitations -- not imitations of the results, but of the methods as well. But they can't. They can't because the source is secret.
> And that's not even considering physics, biochemistry, engineering, and astronomy, ...
The only way a result from a proprietary source would not be an issue is if the result isn't original. A routine statistical result, one that anyone can duplicate, isn't likely to be an issue. But an original result, one in which the mathematics itself is key to the result, would require full disclosure.
> ... where many of the tools you use will always be expensive and built by industry, and have no impact on peer review.
Not really. Any significant result must be completely transparent. To understand the reasons, review the history of the Mars Climate Orbiter:
http://en.wikipedia.org/wiki/Mars_Climate_Orbiter
Even though the specifications were perfectly clear, even though everything was out in the open, two teams used different unit systems, and a critical mid-flight burn went wrong. Imagine how much worse such things would be if any part of important technical processing was concealed from close inspection.
Is a telescope a proprietary source? Is a commercially manufactured CCD a proprietary source? Maybe they got the response curve wrong! Okay, test it before you announce your galactic dust measurement paper! I take that attitude towards "experimental mathematics" that involve computers in some deep way.
And no need to patronize with Wikipedia links, I know the story about the Mars Climate Orbiter. And I don't think it even demonstrates your point. As I understand it, vxWorks, which many of the NASA missions use, is closed source. You have to pay to see the source. And I'm sure that Wolfram Research would or could do the same thing for e.g. intelligence agencies (and hopefully will do for everyone in the future, fingers crossed).
Let me do some patronizing of my own: are you sure your understanding of what the language does is up to date? You seem to talk of it as if it were a predominantly a CAS: http://reference.wolfram.com/language/index.html
Translation: "Don't document your claims like a scientist. What kind of conversation do you think this is?"
> As I understand it, vxWorks ...
Not relevant to the discussion except as another example of the dangers of closed-source systems.
Personally, I would love to see Mathematica's simplification and integration routines some day and discuss them with everyone. That's one of the "basic" things that the free CASes still get so woefully wrong, and for me is one of the most interesting secrets.
So you guys (?) released publicly some boring code about linking Mathematica with Hadoop. Big whoop, it's just a wrapper. Where's the real interesting stuff?
Which means that open-sourcing our projects during their actual development isn't worth the significant development cost (an entire toolchain would need to be open-sourced, and documented). And it also is somewhat antithetical to our design process, which is kinda centralized around Stephen himself, who for the most part really does have a good sense of design.
I think that could change, though, and then I think there is a really good opportunity to open source more of our stuff and start building stuff collaboratively with a wider community. Especially when our Cloud stuff comes online.
Also, I regularly bug Wolfram about open-sourcing some core part of the kernel. He's not in principal against it, but points out that it would cost a lot, buy us nothing in the short term, and fork the language. But I think it'll happen eventually, hopefully sooner rather than later.
Collaborations in Wolfram language will be a pretty unique experiment, for they are likely to unite people from very different fields (including, of course, lots of non-programmers). It's going to be great.
There is likely a lot left to be done in the core language, but encourage folks to start with v1 of the language: http://reference.wolfram.com/legacy/v1/
Once the core of the language is working, implementing things like simplification and integration become much easier: http://webcache.googleusercontent.com/search?q=cache%3Arefer...
It seems unlikely that such a movement would grow to be the size of Mathematica or the Wolfram language, but then again Linux and Wikipedia also seemed unlikely at the time.
We used to integrate with Sage, but no longer. The main reason is that it wasn't really used for anything, but made installing Mathics much more complicated
Should I work on Mathics, Sympy, Maxima, or Axiom? Or is Sage itself growing its own routines?
If you're familiar with / interested in Mathematica, I'd suggest helping Mathics out. The Mathematica language is massive, and there's heaps of low hanging fruit left in Mathics.
(Mathics core developer here btw)
I suggested Mathics because you appear to be interested in what Mathematica can do but resent that it closed source. Since it does not appear that it will be open sourced soon (Taliesin discussed this elsewhere and I got a similar answer from Stephen in an AMA http://www.reddit.com/r/IAmA/comments/tmutz/stephen_wolfram_...), and because duplicating even a portion of a system with a 25-year head start would require a massive amount of effort, it seems the best choice would be to work on a program that would best organize the efforts of the other programs. To agree with that statement one probably has to agree that the language is the best one to build a system around.
I currently work on Octave because there's so much Matlab code out there that needs to be liberated. Is it the same case with Mathematica code? Are people able to easily take their code from Mathematica and run it in Mathics?
I'd really like to see Mathics become the Octave of Mathematica.
)set output tex on
)set output mathml on
That's kinda funny. Our revenue per employee is lower than the industry average. If the company was interested in money uber alles, there are many more profitable and less interesting ways of doing it than what we do now.
> not a single source line of Mathematica code is exposed
Well, not sure what you mean by 'exposed'. But you can read large swathes of our code by looking in the right place in the installation. We also have some official open source projects, like our HadoopLink: https://github.com/shadanan/HadoopLink