499 karma · joined June 11, 2010
I know that open source projects have struggled with the onslaught of AI slop. If I thought that was the motivation, I'd get it.
But that is so clearly not what is going on here.
I really appreciated tailwind, but it solved problems that fewer people face these days.
If they used AI to write this and that gave them more time to volunteer their time towards developing this fantastic piece of open source software, then this all seems like a good thing to me.
I know I am removing the train of thought that led you down this path, but is there anything I just said that is factually false?
Some of the things I like about RubyLLM: 1. the DSL - You can chain methods like ActiveRecord. 2. the Structure - If gives a way to organize agents, tools & prompts 3. the Portability - The costs of AI usage, will one day be an issue for any successful product. Being able to easily test and move from Anthropic to DeepSeek cut my bill down by over 90%. Knowing how easy RubyLLM makes it, ignoring this eventuality feels reckless to me. 4. ActiveRecord Integration - With a simple `bin/rails generate ruby_llm:install `, you can save each chat to your database. 5. Agent Training - This is a side benefit of the above, but has been a huge unlock for me. Since I have all my chats saved, I will regularly pull down that history and give it to claude code to refine my agent instructions.
It's hard not to see them as bottom feeders of the software industry and I wish we would starting treating them like pariah. Submit the PR or STFU.
Having acknowledged that, Apple shifted to the value extraction phase of its business lifecycle.
It sucks.
It like when your favorite band starts selling out, but as publicly traded company, I am not sure it is avoidable.
Having SSH in the name helps developers quickly understand the problem domain it improves upon.
The only real drawback that I've discovered is that it uses canvas to generate the charts. So, when you UI changes to dark mode, you need to reload your charts to update the color scheme ... which in the grand scheme of things is really minor.
With the addition of Phlex::Kit, it has made building out a component library pretty easy too. RubyUI https://github.com/ruby-ui/ruby_ui does a great job of showing off how to do this.
Sure, if you are building an enterprise application, this likely doesn't make any sense.
But, if you are building something for a consumer audience. Or if you are trying to differentiate yourself by building something beautiful. Then maybe wrap these 100 lines of code in a very specific class name (.fancyGlassFrostedGlass) and call it day?