ActiveBlog

Finally, a work blog!
by David Ascher

David Ascher, July 25, 2005

I'm quite pleased to finally be able to post on an ActiveState blog (or activator blogs, since that's the word we use to refer to ActiveState employees). I've had a personal blog for a little while now, and that's been...

I'm quite pleased to finally be able to post on an ActiveState blog (or activator blogs, since that's the word we use to refer to ActiveState employees). 

I've had a personal blog for a little while now, and that's been fun -- but it's always been quite tricky to figure out whether I could/should talk about "work" topics on it (like, say, programming languages).  With a work blog and a personal blog, it'll be easier for me, and clearer for the readers.

Like all good blogs, this one is still ill-defined.  I will probably end up talking about:

  • ActiveState developments (new products, features, people, events, etc)
  • Industry/community trends, events, announcements
  • Whatever else strikes my fancy
  • Responses to reader questions/comments

As to the last point -- please post your comments or send me questions.  I enjoy hearing from customers, fans and critics.  If you have something to say to me personally or to "ActiveState", send it my way (DavidA [at] ActiveState [dot] com).

I will also not be talking about:

  • Python Software Foundation business -- I'll leave my musings on that topic as a PSF director to the upcoming PSF blog.
  • Anything having to do with spam or security -- I'll leave that topic to others more qualified to answer.

Before we start, however, some thanks.  Setting it up took a fair bit of work, mostly by Kerry Taylor, our
communications pro), and Chad Lindstrom, our web developer extraordinaire. 

As usual, opinions on this blog are mine (at least at the time that I write them), not those of ActiveState, Sophos, or anyone else.

Subscribe to ActiveState Blogs by Email

Share this post:

Comments

1 comments for Finally, a work blog!
Permalink

I would love to see a discussion of the "appropriateness" of Python for various applications. One of the fundamental engineering decision I run up against time and time again is the foundational decision of which programming language is the "best" for developing various applications. REal time applications -- Python probably not the choice, but C. Scientific modeling? Fortran is still viable. Business applications? Cobol is deeply entrenched, but would Python serve for new applications? Anyway. How does Python fit into the progamming language family for various appliction phyla?