AJAX book, Web 2.0 Workgroup and T-dot Enablr

Manning released some preview chapters for Ajax in Action today. Chapter 4: The page as an application and Chapter 9: Dyanmic Double Combo are available now. It’s either this or Pragmatic AJAX and with Ben Gailbraith and Dion Almaer of the Ajaxian this book should rock. “Ship It!”: http://www.pragmaticprogrammer.com/titles/prj/index.html and Agile Web Development with Rails are fantastic. I think I’ll stick with the Pragmatic books for now.

Toronto has an interesting looking company, Enablr with 2 great looking services: Transcribr and Stenographr . I am guessing that this is just a frontend to human-enabled/wetware-enabled podcast transcription services. But a great idea, hats off to Ken , AJ and Andrew .

The TechCrunch , WeBreakStuff , and Read/Write Web folks have started the Web 2.0 Workgroup . Great starting point for Web 2.0 blog commentary. The Ajaxian is the other spot.

This entry was posted on Tuesday, October 11th, 2005 at 9:15 pm and is filed under Articles. You can follow any comments to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

  • Ken King | King Mark

    <p>David,</p> <p><br />
    Thanks for the kind words. </p> <p><br />
    Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.</p> <p><br />
    Our decision to go this route was motivated by two things &Atilde;&cent;&acirc;&sbquo;&not;' making it simple for the user to get what they want, and doing something <strong>now.</strong> The frontend experience came first, wetware was what we could do right away, and next we&Atilde;&cent;&acirc;&sbquo;&not;&acirc;&bdquo;&cent;ll move on to refining the backend.</p>

  • http://www.kingmarketing.ca/weblogs/kenking Ken King | King Marketing

    David,

    Thanks for the kind words.

    Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.

    Our decision to go this route was motivated by two things â€' making it simple for the user to get what they want, and doing something now. The frontend experience came first, wetware was what we could do right away, and next we’ll move on to refining the backend.