"The actual print production process was quite an adventure—going right to the edge of what was possible."
I liked the book a lot, but have a hard time not seeing this as hyperbole. Yes, it's the printing industry..but it's just just diagrams and text; I don't remember anything that a few weeks of learning LaTeX couldn't accomplish?
I think that he means getting print production in sufficient high dpi without getting e.g. unwanted moire patterns or blur of details. The postscript file might be conceptually simple, but there's a lot of weird problems when mass-printing in high quality, both dpi-wise and color-wise.
It would be interesting to see how effective those programs would be if run on the device. I can't decide if I'd have found them enlightening or distracting.
Setting aside Wolfram's book, I also wonder if Knuth's Art of Computer Programming, Abelson and Sussman's Structure and Interpretation of Computer Programs, or the Introduction to Algorithms books would benefit. We'll see soon I'm sure.
But getting back to the static version, certainly one benefit is to avoid carrying the dead tree versions, as Wolfram pointed out.
When I think "which of my college classes could I have learned more from if I'd had an iPad version of the textbook", data structures and algorithms stands out the most. I'd love to see a really good adaptation of an already-good static textbook in these fields... I'm not in school anymore, but I might read it just for fun.
Yes. Both data structures and CS theory (making proofs about different computation models, &c.) courses would benefit tremendously even from having better PC/web-based visualizations/simulations. Stepping through the behavior of turing machines, or graph searching algorithms, or what have you, is much much clearer on a computer than on a blackboard or paper.
Come to think about it, it is actually kind of exciting. You could also have a REPL for every example and solve the problems on the spot (and get immediate feedback).
It is exciting! But what I wonder about is what a tablet gets you that you don't get with downloading PLT Scheme and visiting http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-11.html... Or in the case of NKS, tracking down Mathematica and downloading the code from the book and playing with that on a PC. I don't have an ipad, so I can only guess.
Wolfram mentions getting excited about zooming in on the diagrams, and about using the app to refer to parts of the book for himself or to show others. In fact, it seems like the tablet would be great for two people exploring a book or data together.
Mainly convenience, I suppose. Also the immediate feedback on solutions could be good.
How many times do you really do the exercises in books, no matter how much the authors stress that it is important to do the exercises? I tend to skip and save them "for later".
Of all the disciplines that will be revolutionized by computers, I do not think programming will be one of them, because it has already been revolutionized by programming. You already have an unparalleled ability to self-teach programming because programming has already closed the feedback loop as tightly as it can possibly be, with REPLs and so on and so forth.
Don't forget that whatever glorious visual interactive treats you envision will have to be, you know, implemented, and decent odds it's already either implemented or not really worth implementing for programming. Sure, it's nice to see a tree balancing or a linked list getting traversed but the virtues of pretty animations start fading as you get a hang of the material.
The value of digital education won't and doesn't come from putting a thin, shiny veneer of digital on top of analog textbooks, it will come from enabling entirely new learning modes based around instantaneous and copious feedback that humans can't give, because there aren't enough of them or because they simply can't feed back fast enough. Try to model more disciplines to look like how a modern self-taught hacker learns programming, don't pine as a programmer for flashy textbook-like "digital textbooks" for programming.
That's exactly what I was thinking. The iPad is about as powerful as the desktops of the day were when NKS was written. It wouldn't take a whole heck of a lot to have interactive simulations embedded in the pages instead of diagrams.
For people who've read 'A New Kind of Science' on here...what did you think of it?
I find that people's opinions of the book are quite polarized either they found it fascinating or were put-off by Wolfram's self-congratulating. So what does HN think?
There is plenty to admire in the book but Wolfram's self-aggrandizing and complete lack of protocol wrt credit to others in the field is terribly off-putting. I think this book could have had far more impact if he had just bothered to tone down his ego and be charitable about prior work (whether or not he developed certain ideas independently; that doesn't excuse you from being honest about who did the work first)
I think the split is between people who knew about cellular automata before reading the book, maybe even simulated their own cellular automata, and those who weren't familiar with the concept before. If you're in the former group, you'll find a lot of needless hyperbole about fairly standard results that were known for decades. Plus a few interesting ideas mixed in between. Plus even more hyperbole. If you're in the latter group, and didn't really know what cellular automata are about, your mind will be blown (and rightly so, these things are cool), and you won't mind Wolfram's tone so much.
Here is a general thought about it. I think anyone who ever played with CA more seriously had a similar idea, but NKS took it a step further and tried to formalize it. It's an interesting read, with A LOT of bloat in the book. Actual book is damn huge, and IMO it could have easily been a book of ~300 pages at most.
Aside from that, I think it's quite interesting and well worth a read, even if you're not into CA itself - that is, if you can navigate yourself around the bloat.
I've read the book from a data compression/information complexity interest standpoint. So, I can't comment on it's pretensions over it's usefulness in all area of sciences.
It has two parts, the main text and the supplement, which is actually longer. I've read most of the main text.
There's not much practically useful info in there that you couldn't pick up by reading good Wikipedia articles or other online articles, esp. now that the book has been our for years:
My impression was that there were about 50 or 100 pages worth of insight, padded out and repeated over and over again to fill a 1100 page (or whatever) book. I only made it to about page 500 before giving up, feeling like I’d read the same part 3 or 4 times already, and just skimming the rest and looking at the pictures. Wolfram’ prose also oozes ego, which doesn’t help.
I've worked under a person very much like Wolfram in terms of an ego so large they can't see the world around it. I remember having a product planning meeting one time where he went into a great detail about this sweeping plan he had come up with. With a great many diagrams and thought points and slides (oh the slides!), he described a system he believed would radically change humanity, advance the species etc. etc. etc. At the end of his speech, somebody asked, "aren't you just describing essentially this piece of technology <listing several extant examples>?" To which he paused for a good minute, minute and a half and responded "no! it's totally different!" It reminded me of the 7 minute abs routine.
The problem was not that he hadn't come up with something interesting. It was that what he had come up with was something everybody had come up with. He had just spent so much time holed up in his office writing and making diagrams that he hadn't poked his head up into the world enough to realize that he hadn't come up with anything unique or interesting.
This ego feeding manifested itself in all kinds of interesting ways. For example, his ego required that the things we were producing were unique based on what he knew. Even if we were building something that was essentially the same thing that everybody else in the world had built, he'd direct us to build it in some fashion that often ignored the practical results of good engineering practice (learned through thousands of iterations of trial and error over decades) and make it function in a way that was unique to our products, but not necessarily better, and because we were ignored so many hard lessons others had learned for us, often with significant downsides. Long after these things had been implemented, and the downsides of this approach were now readily apparent and in-your-face, we'd go back to him -- to which his reply would be, "I'll have a solution in the next version!"
Months later he'd roll out his new development roadmap that failed entirely to address those issues, pretending like they had never been brought up (no Adoubt since they bruised his ego) and sent us off in another random, but already well understood direction, but cock angled so we'd end up making another round of well documented mistakes.
A real simple example, instead of showing aggregate sums for discrete values in a data field as a simple bar chart, he insisted we use a different metaphor that had long since been abandoned by the field -- only he refused to acknowledge it. This fit the "novelty" requirement for his ego, but failed the "useful" part of building software.
What finally ended it all was a perfect storm of past customers all coming and complaining that they weren't getting the product they were paying for. In some cases we'd even been paid to fix long outstanding problems created by our failure to design well understood parts of the software around well understood metaphors. The result is that he very quickly went to being "no longer with the company".
My lessons from that experience is that innovation is important, but it has to be built on the solid foundation of past experience. Even Newton understood this, "If I have seen a little further it is by standing on the shoulders of Giants."
The problem with something like "A New Kind of Science" is that it's not new. It's a study of the applications of a well understood field onto other fields. If it was written without ego the title would have been "A Study of the Applications of Cellular Automata and State Machines" or "Recognizing Computation in Cross-Domain Studies Using Cellular Automata", or the lofty "An Exhautive Review of Cellular Automata with Applications as Turing Machines." In other words, NKS brings us back to square one with Turing's "What is computable?" Only looked at from another angle.
It's not that what's in the book isn't interesting, it is. It's that it's not revolutionary in the way Wolfram wishes it was. It's "merely" evolutionary and Wolfram refuses to understand that. And ju...
Really interesting collection of cool things you can do with Cellular Automata. I've implemented a few of the automata in the book for fun (they're all pretty simple), but I've yet to find a real-world use for any of it.
If you don't take the "this will change the world and is the most important thing since math was invented" tone too seriously, it's pretty entertaining. And who's to say, it might turn into a revolution. Certainly the ideas about complexity theory he puts forth are interesting and worth thinking about.
If I had to boil it down, it would be "Any system is either trivially simplistic, or complex enough to do anything." Think logic gates built with conway's game of life, or adders built with dwarf fortress pumps, that kind of thing. He's trying to unify all complex systems with cellular automata.
That's my take on it, at least. Read it a while ago. If you're interested in cellular automata or complexity, it's worth reading.
This would be really cool on the ipad if the illustrations were interactive, kind of like the NKS Explorer PC app he released a few years ago. That was a fun tool to play with this stuff.
I think Wolfram is onto something. He may have an ego the size of Texas, but my intuition tells me that it really is a new kind of science. I also think it might be 50 years or more before the mainstream community acknowledges it.
I bought it on the day of release and I actually read the whole thing cover to cover. Not because it was good but because I was always expecting some kind of genius insight to appear.
It never did.
The book is filled with confused science, pretty graphics and massive ego stroking. Huge disappointment.
Summary: So far, only the iPad has been an awesome enough e-reader to make Stephen Wolfram willing to release "A New Kind of Science" to be viewed on it.
I found the footnotes, which are about as long as the text, to be a very interesting stand-alone read. Wolfram's self-congratulating doesn't bother me, although his work sometimes borders on confusing a posteriori computer models with reality. (Not that he's the only one who does that.) I highly recommend NKS.
32 comments
[ 5.2 ms ] story [ 76.4 ms ] threadI liked the book a lot, but have a hard time not seeing this as hyperbole. Yes, it's the printing industry..but it's just just diagrams and text; I don't remember anything that a few weeks of learning LaTeX couldn't accomplish?
edit: typo.
http://www.stephenwolfram.com/scrapbook/page8/#2002_build
Setting aside Wolfram's book, I also wonder if Knuth's Art of Computer Programming, Abelson and Sussman's Structure and Interpretation of Computer Programs, or the Introduction to Algorithms books would benefit. We'll see soon I'm sure.
But getting back to the static version, certainly one benefit is to avoid carrying the dead tree versions, as Wolfram pointed out.
Wolfram mentions getting excited about zooming in on the diagrams, and about using the app to refer to parts of the book for himself or to show others. In fact, it seems like the tablet would be great for two people exploring a book or data together.
How many times do you really do the exercises in books, no matter how much the authors stress that it is important to do the exercises? I tend to skip and save them "for later".
Don't forget that whatever glorious visual interactive treats you envision will have to be, you know, implemented, and decent odds it's already either implemented or not really worth implementing for programming. Sure, it's nice to see a tree balancing or a linked list getting traversed but the virtues of pretty animations start fading as you get a hang of the material.
The value of digital education won't and doesn't come from putting a thin, shiny veneer of digital on top of analog textbooks, it will come from enabling entirely new learning modes based around instantaneous and copious feedback that humans can't give, because there aren't enough of them or because they simply can't feed back fast enough. Try to model more disciplines to look like how a modern self-taught hacker learns programming, don't pine as a programmer for flashy textbook-like "digital textbooks" for programming.
I find that people's opinions of the book are quite polarized either they found it fascinating or were put-off by Wolfram's self-congratulating. So what does HN think?
Cosma Shalizi is a gem.
Aside from that, I think it's quite interesting and well worth a read, even if you're not into CA itself - that is, if you can navigate yourself around the bloat.
I've read the book from a data compression/information complexity interest standpoint. So, I can't comment on it's pretensions over it's usefulness in all area of sciences.
It has two parts, the main text and the supplement, which is actually longer. I've read most of the main text.
There's not much practically useful info in there that you couldn't pick up by reading good Wikipedia articles or other online articles, esp. now that the book has been our for years:
http://en.wikipedia.org/wiki/Cellular_automaton
I'd still consider buying it for the iPad if it's cheap (<$10), just so I can browse and read it when I'm bored on the subway..
Weinberg’s review in the New York Review was quite good: http://www.nybooks.com/articles/archives/2002/oct/24/is-the-...
The problem was not that he hadn't come up with something interesting. It was that what he had come up with was something everybody had come up with. He had just spent so much time holed up in his office writing and making diagrams that he hadn't poked his head up into the world enough to realize that he hadn't come up with anything unique or interesting.
This ego feeding manifested itself in all kinds of interesting ways. For example, his ego required that the things we were producing were unique based on what he knew. Even if we were building something that was essentially the same thing that everybody else in the world had built, he'd direct us to build it in some fashion that often ignored the practical results of good engineering practice (learned through thousands of iterations of trial and error over decades) and make it function in a way that was unique to our products, but not necessarily better, and because we were ignored so many hard lessons others had learned for us, often with significant downsides. Long after these things had been implemented, and the downsides of this approach were now readily apparent and in-your-face, we'd go back to him -- to which his reply would be, "I'll have a solution in the next version!"
Months later he'd roll out his new development roadmap that failed entirely to address those issues, pretending like they had never been brought up (no Adoubt since they bruised his ego) and sent us off in another random, but already well understood direction, but cock angled so we'd end up making another round of well documented mistakes.
A real simple example, instead of showing aggregate sums for discrete values in a data field as a simple bar chart, he insisted we use a different metaphor that had long since been abandoned by the field -- only he refused to acknowledge it. This fit the "novelty" requirement for his ego, but failed the "useful" part of building software.
What finally ended it all was a perfect storm of past customers all coming and complaining that they weren't getting the product they were paying for. In some cases we'd even been paid to fix long outstanding problems created by our failure to design well understood parts of the software around well understood metaphors. The result is that he very quickly went to being "no longer with the company".
My lessons from that experience is that innovation is important, but it has to be built on the solid foundation of past experience. Even Newton understood this, "If I have seen a little further it is by standing on the shoulders of Giants."
The problem with something like "A New Kind of Science" is that it's not new. It's a study of the applications of a well understood field onto other fields. If it was written without ego the title would have been "A Study of the Applications of Cellular Automata and State Machines" or "Recognizing Computation in Cross-Domain Studies Using Cellular Automata", or the lofty "An Exhautive Review of Cellular Automata with Applications as Turing Machines." In other words, NKS brings us back to square one with Turing's "What is computable?" Only looked at from another angle.
It's not that what's in the book isn't interesting, it is. It's that it's not revolutionary in the way Wolfram wishes it was. It's "merely" evolutionary and Wolfram refuses to understand that. And ju...
If you don't take the "this will change the world and is the most important thing since math was invented" tone too seriously, it's pretty entertaining. And who's to say, it might turn into a revolution. Certainly the ideas about complexity theory he puts forth are interesting and worth thinking about.
If I had to boil it down, it would be "Any system is either trivially simplistic, or complex enough to do anything." Think logic gates built with conway's game of life, or adders built with dwarf fortress pumps, that kind of thing. He's trying to unify all complex systems with cellular automata.
That's my take on it, at least. Read it a while ago. If you're interested in cellular automata or complexity, it's worth reading.
This would be really cool on the ipad if the illustrations were interactive, kind of like the NKS Explorer PC app he released a few years ago. That was a fun tool to play with this stuff.
It never did.
The book is filled with confused science, pretty graphics and massive ego stroking. Huge disappointment.