Recent Entries
- Blosxom 2.1.1 released
- Blosxom 2.1.0 released
- Using Blosxom as Feed Generator
- The Blosxom Plugins Distribution is Coming
- Blosxom Development Excitement
- Old and New Annotated Blosxom Script
- Textile 2 Plugin
- Wikipedia Trouble for Blosxom!
- Blosxom Prime Site Moved

User Site
News
Tips
Help
User
Flavours
Plugins
Developer

Registry Listings
V2 Plugin Registry
V3 Plugin Registry
ModBlosxom Plugin Registry
Flavour Registry
Other Files and Hacks
Images and Logos

Site
Editors
Colophon
Email

Blosxom
Blosxom Prime
New Mailing Lists
Old Mailing List
SF.net Project
Blosxom Wiki
Del.icio.us Tag
IRC: #blosxom on
Freenode     

Syndication
RSS


Locations of visitors to this page

Recent Comments
Past Two Days
Past Week

Books of Interest


Seach the Site


Advanced Search

Blosxonomy: Ruby Port of Blosxom
November 21, 2005.    

While Blosxom may not have taken the world by storm like other blogging systems (like, say, Wordpress), it certainly started a trend. That's is why we find the Blosxom meme being ported from the original Perl to Java (Blojsom), PHP (Blosxom.PHP), Python (PyBlosxom), Lisp (Lisp-Blosxom) and many others.

Now we can add Ruby to the list with Blosxonomy.

Blosxonomy is a very lightweight Blosxom like blogging system written in Ruby, and designed around four core ities: simplic-ity, taggabil-ity, extensibil-ity and compatibil-ity.
Welcome to the show, Ruby!

3 comments  |  permalink

Click the button to

 

Dan wrote
2005/11/29 14:06:29
Another "ity"
You forgot to add "itty bitty"
Douglas Nerad wrote
2005/11/29 18:45:49
That's true!
Tim Fanelli wrote
2005/11/30 05:05:31
Itty bitty
Itty bitty might actually be a solid itty to add. You forget that Blosxonomy is only about 5 weeks old now - so not many people have had a chance to check it out yet (I know of about a handful of Blosxom and pyBlosxom users who are checking it out), and Ruby is a very new language that doesn't have anywhere near the number of developers that Perl and Python have which is making it difficult to get people to send in patches. And for now, it's "itty bitty" code base makes the learning curve minimal for converts, keeps my response times low, and leaves plenty of room for developers to come into play.