techscruggs

This sounds like exactly the kind of thing that some with a small penis would say ...

The post effectively communicated what it needed to. It seemed both written and structured in a way that was optimized for human consumption.

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.

Let me make sure I am hearing you right. 1) The person you report to asked you to accomplish a discrete task 2) of standing up one of the most common websites on the planet 3) and your response was to begin building your own custom CMS?

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?

It analogous to Active Storage and aws-sdk-s3.

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.

Do you have any details published around 2.0? Would love to learn more.

And thank you! It is absolutely awesome and a true joy to work with.

He is using a 2022 M2, which you can get that for about $2k used. That is beyond reasonable.

The incentives structure is deeply broken in the field of Security Research. They are the middle management of the FOSS world. Celebrated for dumping more work on volunteers. The more urgent the work, the more they are celebrated. Acknowledging the realistic impact of issues or the pragmatic implications of an issue are at odds with their incentives.

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.

MacOS isn't a hard requirement. You could spin it up on a VPS. Hetzner is great and very inexpensive https://www.hetzner.com/cloud/

I remember a time ...

Remember that Steve Jobs appointed his COO Tim Cook to take over Apple. Not Ives or Cue or Federighi. I've always seen this as an acknowledgment that without Jobs the company would not be able to innovate in the same way.

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.

I like this idea!

Having SSH in the name helps developers quickly understand the problem domain it improves upon.

That is a rather dismissive attitude that could cause you to overlook some great technologies.

I've been using apache echarts for a while. It is excellent. As you dig deep, some of the examples and libraries are in Chinese, which can be challenging.

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.

Well, taste for a Global Interpreter Lock, at least.

Same. Texas.

https://www.phlexing.fun/ We have this for that. :)

A bit off topic, but whenever Rails and templating get brought up, I have to plug my absolute favorite project out there: Phlex https://beta.phlex.fun/. It's like ViewComponents, but swap out the ERB for pure Ruby. It has been a joy to develop with.

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.

It really depends on the use case. Right?

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?

This is the first site I've run in to that uses neumorphic design. Love the aesthetic -- just never seen in it the wild before.

This appears to be riding the [Solid Cache](https://dev.37signals.com/solid-cache/) idea that DHH has started espousing. At the core of this idea is that SSD's are sufficiently fast for caching. Sure, this may work for 37signals, but that is because they manage their own hardware. That is the exception and not the rule. And, per [this discussion two weeks ago](https://news.ycombinator.com/item?id=39443679). SSD's aren't as fast for most of us that leverage "the cloud".

Sure, you can do it, but why? I am all for removing complexities in my infrastructure. That said, Memcached and/or Redis are both rock solid and dead simple.

This just seems to be a waist of time 99.999% of use cases.

This is a win for the environment and for human rights. A lot of people on here are talking about how solar and wind are better alternatives. The problem with that is that they typically need to be stored in batteries made of cobalt. The vast majority of cobalt mines exist in the Congo where modern day slavery exists to extract it. This affects everything from your Tesla to your iPhone.

Because not tipping someone that makes their living off of tips is a jerk move.

The reason why everyone is upset is because Apollo works perfectly for the Reddit use case while the official client does not. Sure it is technically superior, but it is "better" from a product management perspective.

Reddit, Tumblr, TikTok, Instagram, etc, all attract a similar type of user but they are different products that engage people in different types of social interactions.

You can't port that.

At Amazon's scale, betting on M1 servers for a niche subset of their EC2 offering doesn't seem to be really risky.

What are some of the other exciting things happening in the Rails world these days?

This looks great. I'd love to remove Redis from my tech stack on applications with low throughput background jobs. Sadly, it doesn't appear to have a UI.

Resque and Sidekiq are both good enough solutions, but what makes them my defacto choice is the robust web UIs that comes with them.

You can implement background processing with less operational complexity. This allows you to leverage activejob to get something up and running quickly and easily.

Granted, if you start having higher throughput, you want to move on from using postgres as your message bus.

1) Setup a status page for what you want to monitor (/health/queuelength) 2) Point statuscake at that url 3) Connect statuscake to pagerduty.

This approach is easy to implement and scale

I hired the best Engineering leader I have ever worked with early in his career from posting on an HN "who's hiring thread".