This is the documentation for the development version of IPython. I don't think they care that they're "missing out on installs" by releasing documentation about what's changed in version 1.0
However, if you'd like to try out IPython 1.0, it's an open source project. You can checkout the latest code at https://github.com/ipython/ipython
Sure. The simplest approach is to use a naive Bayesian classifier (you can find a bunch of open source implementations).
In my app, I actually track client-side actions -- essentially, clicks, but with more context. Anyway, you can treat a single user session like you would the text of an email, where the "actions" are the words.
From there, all you need to do is capture a bunch of sessions and tell the classifier which users are not strong computer users and which know what they're doing, passing the corresponding "documents".
Now you can feed in new documents and determine which of your users know what they're doing, and which aren't really computer users.
(It my experience, people fall into one of those two camps.)
Great question. In my career so far I have deployed Web apps in ASP Classic, PHP, ASP.NET and Ruby on Rails. It appears that RoR can only handle a small fraction of activity compared to the other technologies before maxing out system resources. There are some lighter weight Ruby frameworks out there (Rack, Sinatra) that are probably more appropriate for large-scale back ends. Still, I have not worked with any Web technology that is performant enough to confidently endorse.
No, this is now the latest template. That's what I'm using in all my books now, and it's coming from a more advanced project for writing music books http://orkestrix.org/
My goal was, if I could write about code and music at the same time, then making a build system for books would be easy. The above is the end result of that work. Enjoy.
I understand you don't want to use LilyPond because it is too complex, but you may want to know that LilyPond comes with a tool to convert from ABC to LilyPond (abc2ly). One could use it to write the music examples in ABC and have LilyPond typeset them. I'd consider using a setup like this to typeset the "final" version since LilyPond's typography is so nice.
As others have stated, this probably isn't the best way to do a survey. At the very least, you're going to have some bias from posting this on HN late at night (in the US).
You'll be able to survey a much larger audience, get more responses, and have statistically significant results. In addition, Google has a nice dashboard which lets you compare answers according to various demographic information such as gender, age, location, income, etc.
My experience with LabVIEW, for the brief amount of time I worked with it for our high school robotics team, was slightly frustrating. I liked the dataflow paradigm, and to some degree the dashboard system, but connecting and managing the "wires" was a pain. Especially since I'm more comfortable/faster with a keyboard than I am with a mouse.
It also seemed to be harder to read and understand the flow of the code, which made debugging a pain sometimes. I remember struggling to figure out why my code wasn't working, only to find out I had used 1 instead 1.0 as a constant. The only indicator of the data type was a thin colored border around the box.
LabVIEW seems to do a great job as a kind of Visual Basic for scientists and engineers, but I'd probably find it frustrating to spend any substantial amount of time programming with it.
I understand the frustration. I've run into from a few of my students on the FTC teams that I mentor in my neighborhood. I think that this can be attributed to a lack of really great educational material (there is good stuff out there, but it can be hard to find when the build season really picks up), but on the flip side, I've seen kids in elementary school pick up the basics of dataflow programming, especially when working with the NXT-G software that comes with the Mindstorms NXT.
It's definitely a tool and one should always use the best tool for the job. Sometimes the best tool is not necessarily the one with the most suited features, but the one that you're most adept at using. Either way, thanks for the input, really. It helps a lot to understand what people walk away with when they use a product you've been a part of, and I love that HN users are honest and gracious in their feedback. Cheers.