Please create an account to participate in the Slashdot moderation system
We've run a few two-part videos, but this is the first time we've split one video into six parts -- with two running today, two tomorrow, and two Thursday. But then, how many people do we interview who have had as much of an effect on the nature of information transmission -- as opposed to just publishing -- as Tim O'Reilly? We don't know for sure, but there's a good chance that O'Reilly books are owned by more Slashdot readers than books from any other publisher. That alone makes Tim O'Reilly worth listening to for nearly an hour, total. (Alternate Video Links: Video 1 ~ Video 2; transcript below covers both videos.)
Our engineering interns have started down a new path: Using Github from the beginning (I set the repo private), and, after a bare minimum is completed, flipping the repo public and continuing development in the open using Github. How do PO and Legal reviews fit in? How can we ensure we're not exposing ourselves or diluting our IP if we're doing semi-constant development, publicly, sans a heavily gated review process? What does everyone else do? Or does corporate America avoid this entire opportunity/entanglement/briar patch?
Stenotype machines are usually most visible when court reporters are using them. They've been around since the 1800s, when their output was holes in paper tape. Today's versions are essentially chorded keyboards that act as computer input devices. (Douglas Engelbart famously showed off a chorded keyboard during his 1968 Mother of All Demos.) Today you have The Open Steno Project, and Stenosaurus is a member. And while Joshua's project may not have an actual website quite yet, it has an active blog. And the 225 WPM claim? Totally possible. The world record for English language stenography is 360 WPM. And you thought the Dvorak Keyboard was fast. Hah! (Alternate Video Link)
- open source, with a community following ; the kind of stuff Slashdotters would prefer
- tidy software architecture; simple things should remain simple
- allow open API allowing usage across many languages (say: Python & Java)
- clear licensing status, not estranging future commercial use
- serious multilingual & font support
- PDF-handling rich features, not limiting usage for invoicing, e-commerce, reports & data mining
- digital signing should not go against other features
I'd like to poll the collective Slashdot crowd wisdom about if/which PDF related libraries, they have written software with, keeps them happy for *all* the above reasons. And if not happy with that all, what do they thing is the best bet for learning one piece of software in the area, with great reusability across different circumstances and little need for extra hacks? I'd really like to hear the smoked out war stories. It is easy to obtain a list of such libraries, yet tricky to understand whethe people have obtained success with them!