As mentioned in Beauty, a previous post, I’m shutting down Amethyst on the Internet. I’m my only current customer and it’s taking time and money to keep it running that can be better spent elsewhere. It may not be a viable commercial product, but it continues to be very useful to me. It is the major way I read news. If I can’t drop an RSS feed for some news/information source into Amethyst, I’m much less likely to read it regularly.
Development will be ongoing. With just one user profile, direction is clearer and fewer tradeoffs need be juggled. Rails 3 has outgrown my needs but Rails 2 is not getting any updates, bug fixes, or security fixes. The first two I can deal with myself, but generally not the last. On the Internet, that’s a problem. On my own laptop, it’s a problem I can live with.
Padrino is a lighter weight Web framework built on top of Sinatra. It’s somewhere around the functionality of Rails 1 when I started. And I know Web frameworks better now so I can fill in most of the holes. Some of the speed annoyances of Rails 2 are gone on Padrino. Or at least on the partial conversion to Padrino already done.
I’ve considered open sourcing Amethyst, however as noted in Beauty, much of the code is not something I’m proud of. Unless there is a request, I won’t publish it. I am working on making the Padrino port code I can be proud of and am willing to show in public. Currently it is running in split mode, the backend that reads the subscribed RSS feeds is the old Rails 2 code. The front end is partially ported to Padrino. I’ll push it to GitHub when a minimal front end and complete backend are working in Padrino.
I’ll continue blogging here about the Padrino port.