3 ms·
Very nice indeed. I bet it wasn’t the intention of the author, but the intro sounded a bit critical of Octopress and of how it fell behind, and so on. Perhaps
by eecc 5y ago
Very nice indeed. I bet it wasn’t the intention of the author, but the intro sounded a bit critical of Octopress and of how it fell behind, and so on.
Perhaps I woke up in the wrong mood, but I’d have praised the authors and community of the tool, it’s open-source, was built with generosity out of one’s own free time. That’s quite a capital!
So, we all know stuff gets abandoned, people do move on, perhaps they could handle handovers or sunsetting better, but let’s be first of all grateful.
- capableweb 5y agoI'd agree with you, but the passage is really not passing any blame and is being factual, not exaggerated or flaming the authors in any way. I think it's a pretty fair observation even if critical. Doesn't mean the work so far wasn't appreciated. For posterity, here is the passage: > I started using Octopress back then and was still using it until today. In recent years I became frustrated with it since on every new system I had to install a version of Ruby that happened to work with Octopress, which wasn't always the case. When it did work, I started getting deprecation warnings from Ruby while compiling this blog. On top of this, Octopress seemed no longer maintained. The website says "Octopress 3.0 is Coming" but this announcement was from 2015 and the website hasn't been updated ever since. It felt like time to move on.
- Borkdude 5y agoThanks for the feedback. I added the following: Octopress worked great for my blogging purposes and I'm grateful that it existed. However, in recent years I became frustrated with the experience of using it, which is probably due to a lack of my familiarity with the Ruby ecosystem.
- ewalk153 5y agoThis is a lovely, honest sentiment. Thanks for sharing (here and on your blog).