Friday, October 31, 2014
Sunday, June 17, 2012
For CoffeeScript, make sure you can run coffee from a command line:
- node, download here: http://nodejs.org/
- npm, now included in node
- CoffeeScript, use the CoffeeScript with Node and npm instructions (basically one line, but...)
- Some kind of programmer's text editor. I'll be using jEdit, but I'd recommend VIM or TextMate as they both have great CoffeeScript integration.
For Dart, install the Dart editor, which is an IDE with a browser (Dartium).
- Dart editor, download here: http://www.dartlang.org/docs/editor/getting-started/
- Unpack the archive someplace and run the program from there.
Monday, April 30, 2012
Wednesday, June 30, 2010
- Still not getting an iPad (I'm a h8r), but Gruber's got a point against my main beef (the closed platform) http://bit.ly/a0vO6j
Apr 02 2010
- No scripting/coding on the iPhone was pad enough. But the iPad could have been great 4 kids to learn 2 code. Too bad. http://bit.ly/ayKHYM
- if I had an iPad rather than a real computer as a kid, I’d never be a programmer today -- Alex Payne http://al3x.net/2010/01/28/ipad.html
Apple has again tweaked section 3.2.2 of the agreement, adding in a loophole which will allow them to approve certain interpretive code tools. The old section 3.2.2 read like this: No interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple’s Documented APIs and built-in interpreter(s).
While the updated version looks like this: Unless otherwise approved by Apple in writing, no interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple’s Documented APIs and built-in interpreter(s). Notwithstanding the foregoing, with Apple’s prior written consent, an Application may use embedded interpreted code in a limited way if such use is solely for providing minor features or functionality that are consistent with the intended and advertised purpose of the Application.And I particularly hope that Squeak and Scratch and other great programming environments for kids and otherwise make it onto the iPad or similar devices.
But, the iPad is just too good for me to not want one. Stefan Miller let me try his iPad a couple of times and I'm sold.
The main reason is that I want a great PDF reader. The iPad is significantly better than the Kindle or even the Kindle DX for reading PDFs. I also want to annotate, and that capability is available as well.
I read a lot of books on programming. These books tend to be heavy and expensive. The PDF versions can often be had for less than half the cost. But, that means carrying a laptop. (I've been known to hold my HP EliteBook sideways with the screen orientation on portrait.
Hopefully innovative programming environments like the Lively Kernel will make it possible to write some code on the device and do some programming with kids. Quoting an interview with Dan Ingalls:
The fact that the Lively Kernel is just a web page and you click on it and you're running this system, it's a system that can do graphics editing, can produce images, can do simple programs, like Squeak that you can save a page from, means that basically anywhere you have a network computer, you can have authoring.
That's one ingredient. Another is I noticed that there is a certain challenge you have before you can become a developer for say the iPhone and yet the iPhone has Safari in it and it runs Lively Kernel applications just fine. It seems to me there is an opportunity here for something much more open than the App Store in which everybody can contribute and produce and share active content.And, I hold out hope that eToys, Squeak and Scratch will someday be approved as well.
But, for now, I am looking forward to compromising my principles! The iPad is on my birthday list! As are a number of apps, gift cards will be welcomed!
Monday, January 18, 2010
While browsing the site, found a picture of me presenting Seaside at ICC4. The book in the picture is Learning Programming with Robots. I think I was answering a question about Alice.
Tuesday, January 12, 2010
Friday, January 8, 2010
The original Refactoring book by Martin Fowler had a big impact on how I thought about writing software. I’d used the refactoring tools in Smalltalk, but the book changed the way I thought about refactoring and gave names to many new refactorings.
This Ruby edition of the book is highly anticipated. I received my copy at a drawing in our local Ruby user’s group. Part of the deal was you had to write a review (you are reading it) in exchange for the book. Nearly everyone at the meeting wanted a crack at the book.
The authors suggest that if you have the original work, you probably shouldn’t purchase this new edition. I don’t agree. There is plenty of new content with around 20 new refactorings and a few new code smells to make the difference worthwhile. There is a tremendous amount of thoughtful Ruby code snippets inserted throughout the text.
In fact, this is one of those books that is great for everyone on a team to have a copy. It is the kind of book that can be used to raise the quality of communication across the team.
You can see the respect the new authors had for the original work, as the new refactorings jibe with the old. Much of the text remains unchanged, which is good as things like the justification, most of the code smells, and background have aged well. Even the order of the refactorings has been largely preserved, which makes it easy to compare the two editions.
Jay Fields and Shane Harvey have updated the examples and step-by-step examples using idiomatic Ruby. Where the original book used Java for the code examples, the examples were pretty language-agnostic, not using anything from beyond the core SDK and even avoiding things like inner classes in examples. This book leverages Ruby’s strengths.