5 ms·
The Wolfram Language is quite cool. Sure, it's a shame it's proprietary - but it has a lot to offer, a few neat ideas, and makes for great, visual demos such as
by GuiA 11y ago
The Wolfram Language is quite cool. Sure, it's a shame it's proprietary - but it has a lot to offer, a few neat ideas, and makes for great, visual demos such as the ones featured in that talk. The fact that you can get cool things running in a few lines of code, like the 3D stack of edges, is appealing - I don't think there are many languages out there that allow you to do things like this in a few lines of code, and with such flexibility.
(it is quite a shame that Wolfram always has to assert how great they are, how revolutionary it is, how they invented everything, how unlike anything else ever done before their work is. It's off putting. Let your work speak for itself, and leave the meta comments out. But I digress.)
I like the "tweet a program" concept. One issue with kids growing up mostly on mobile phones is that it makes them less likely to try to see what's inside and program it themselves. One solution some have attempted is to have IDEs directly running on tablets/phones, but those tend to be fairly clunky. Allowing people to experiment with computation in unconventional manners, e.g. over Twitter, strikes me as an interesting path.
I had a similar project a couple years ago where you would tweet concise instructions to a bot that ran them into a virtual machine, for which the output was a 32x32 pixel image buffer and would get tweeted back to you. If you've played with forth salon or shadertoy, it's the same idea but with a language optimized so as to get cool results in <140 characters. Sadly, like many of my other bots, Twitter shut it down.
But yeah, given their aspirations for education etc., some open source components would be nice. It strikes me as a great exploratory/prototyping language, although it'd probably be hard to maintain large codebases of it due to the fuzziness of the instructions and a certain opacity in the backend.
All that being said, the tail end of the talk (about immortality and the singularity and the box of trillion souls - basically, when the paragraphs don't have code examples anymore) does fall into the standard techno-religious singularity crackpot speculation where things sound vaguely scientific - just enough to give them an air of credibility - but where the terms used are fuzzy and slippery enough to be manipulated into whatever direction the speaker wishes while maintaining an illusion of rigorous reasoning.
- deleted 11y ago[deleted]
- shiggerino 11y ago>Very much agree. And Wolfram used to be a university professor; he darned well knows how to give credit to others when it is due. And he should know that science is supposed to be done by collaboration, transparently sharing information, not by peddling proprietary libraries. But he doesn't care, and he never has. Here's a good write-up about it from 2003: http://chem.tufts.edu/science/Shermer/E-Skeptic/SkepticsOnWolfram.html http://chem.tufts.edu/science/Shermer/E-Skeptic/SkepticsOnWo...
- ForHackernews 11y agoThere's also this classic: "A Rare Blend of Monster Raving Egomania and Utter Batshit Insanity" http://bactra.org/reviews/wolfram/ http://bactra.org/reviews/wolfram/
- deleted 11y ago[deleted]
- dvdfvo 11y agoI'm assuming there isn't any video and audio recording of that Caltech debate?
- Avshalom 11y agoI dunno, a lot of us got our start on TI calculators, and their input was comparatively awful. But they had a small environment and a hierarchial menu of the various key words and common functions. And it worked pretty well.
- GuiA 11y agoThat's a good point! I also started programming on a graphing calculator. One difference is that calculators were very limited in what they could do. No camera, no GPS, no internet connection, the screen was monochrome and 80x80 or so pixels... so the very limited language and input methods worked fine. But on modern day devices, you want to build complex apps that can interact over the network, use the various sensors on the device, display rich media, manipulate video/images in real time, etc. The programming environment has to allow for all of this, which is the tricky part.
- eruditely 11y agoThis is unfair to him, let him move on from previous 'mistakes' people are too harsh on him.