1,906 karma · joined June 21, 2007
http://news.ycombinator.com/item?id=809038 (17 hours ago)
http://news.ycombinator.com/item?id=737464 (36 days ago)
http://news.ycombinator.com/item?id=250566 (415 days ago)
http://news.ycombinator.com/item?id=149283 (527 days ago)
http://news.ycombinator.com/item?id=148202 (529 days ago)
I don't think that follows. Nell's Primer was only a prototype. As a practical matter the kind of infrastructure that went into developing it would over time be replaced by something more economically and socially efficient. The story itself suggests that neither Miranda or the Primer's designers anticipated Nell's needs.
If you still need a human teacher, and that teacher has to be paid, what exactly have you gained by interposing the Kindle between the teacher and the student?
It's likely that little is gained in that limited student/teacher/employment context but in my experience[1] I think there are considerable educational opportunities once people step outside that traditional box.
Exactly. Although the nanotech stuff remains distant, a present day Kindle or tablet system could easily incorporate synchronized interaction between children like Nell and actors like Miranda.
I might feel more sympathy for this guy if he were one of the many recent graduates unable to find the kind of jobs they need to pay off private student loans (with exorbitant rates) instead of being part of an industry that profited from them while ignoring their employment predicaments. What sympathy do guys like these ever show for their unemployed debitors?
"We the people..."
First, GWL once told me the bulk of the code is actually rather mundane GUI form definitions (the sort of crap that is trivial to generate with high level interface tools). There's only a small amount of actual "logic" at that level that ever needs to be maintained (the real control isn't done in Tcl).
Second, even if there are 50,000 lines of Tcl (actually I think the actual number is closer to 300,000), it doesn't mean it's one big script. It's probably more fair to compare it to a unix system with hundreds or thousands of separate smaller write-once scripts.
Ironically I think the real fault here lies with GWL and other Tcl enthusiasts for quoting a true but misleading "number of lines" in the first place. The number of separate scripts and average script length would be more meaningful and representative of the system's real complexity.
This is a well known problem pg hasn't gotten around to fixing. See YC: "unknown or expired link" -- fix it already (790 days ago) http://news.ycombinator.com/item?id=28944
Before the web I used to drive 50 miles every other weekend to buy books from Computer Literacy to add to my personal library when I didn't have a need for them because of the time saved having them at hand later. I don't do this anymore, in part because for my needs the web is often sufficient but also because Computer Literacy eventually went out of business and there's no comparable store anymore worth that trip.
These days I'm thrilled whenever I do find a printed programming book likely to save me time compared to searching the web. The last such book I found was Kurt Jung and Aaron Brown's "Beginning Lua Programming". It's full of well-organized time-saving details and an excellent companion to Roberto Ierusalimschy's "Programming in Lua", a book at the same quality level as K&R's "The C Programming Language". Unless the price is an absolute bargin, I won't bother buying a printed book unless it's as good as those.
- When I'm working with a fast compiler, I setup a small CI system to immediately compile my code and run my tests every time I save my changes. If I can't do this for some reason then I setup a trivial background script to do this constantly and watch the output in another window.
- I try not to cut corners. It's easy to stay in the flow once I have things setup so that I can build and extend my tests and scaffolds along with my code.
Small moves, Everest, small moves...
No. Although this particular dialog is bad, the only time an application should ever tell the user something that simple is if the code is smart enough to know that there really is no corrective action the user can take. If that's not the case then the application should offer to help the user identify the root cause of the problem and tell them what appears different from the last time things worked properly if possible. This is especially important if the user is expected to do any configuration.
While there may be cases where this is true, I've never encountered any and I find this difficult to believe without some specific examples.
These seven influences got me to thinking about one abstraction that was indeed like a biological cell on the one hand and an entire computer on the other which could be universally used at all levels of scales in both software and hardware to "model anything" (including all the old inconvenient things computing was using).
That's perhaps the most enlightening statement about the history of Smalltalk I've ever seen.
I'm not an expert on lisp or functional languages so I'm willing to give him the benefit of the doubt on the first two pages where he presents the design tradeoffs of Qi. Then on the next page instead of learning more about Qi, I find myself in the middle of an argument where his word choice confuses the distinction between free/unsupported open source and free/unencumbered open source. WTF? Didn't he just tell us on the previous page one of his strategies for Qi development was "3. Infiltrate don't confront".
And then I get to learn how he's decided to resign his job and become a wandering Taoist.
But I doubt he would have been as critical of government support for projects had his own efforts been more successful since presumably the university partially supported his research (or at least didn't take the kind of hostile attitude he would have encountered at many corporations).
I think this particular situation shows that there is a difference between having expertise and having an ability to capitalize that expertise. Perhaps had he spent a little more time networking to find people who would be willing to support his ideas, things would have worked out better for him.