News for hackers. Stuff that matters.

trevorhinesley

If Tony and Steve were friends, that's not Apple being cutthroat. Cue: the chapter about poaching from friends in Ben Horowitz's The Hard Thing About Hard Things. If you cross that line and poach from your friends, expect to hear about it. Another example: https://www.reddit.com/r/EntrepreneurRideAlong/comments/1jgz...
Re:Mitchellh starts a new company: Superlogical on Wednesday July 29, 2026 @02:22PM (#49101121)
Scrollbar is fine for me? Just styled
Re:Minions – Stripe's Coding Agents Part 2 on Friday February 20, 2026 @07:07AM (#47087001)
The glass-half-full here is it’s an incredible signal that one of the largest financial gateways in the world is _able_ to do this with current capabilities.

Personally, this is exciting.

Re:Finding and Fixing Ghostty's Largest Memory Leak on Saturday January 10, 2026 @10:08PM (#46572357)
Over-engineered in what way?
Re:Steam Machine on Thursday November 13, 2025 @08:20AM (#45914580)
Signed in just to upvote this. Amen homie
Re:A.I. Researchers Are Negotiating $250M Pay Packages on Saturday August 02, 2025 @09:43PM (#44773410)
He said he’d forego glory, not values.
Re:Vanilla JavaScript support for Tailwind Plus on Friday July 25, 2025 @04:27PM (#44688019)
Where he encouraged people to lean into intentionality and finding purpose rather than using therapy as a replacement?

I have a diagnosed anxiety disorder and I’ve benefited GREATLY from talk therapy in numerous ways. I’m an advocate for therapy. I simultaneously stand behind his post as a healthy nudge for many.

Re:A Deep Dive into Solid Queue for Ruby on Rails on Monday June 23, 2025 @08:25PM (#44361626)
It does have a GIL. You’re not wrong, but by that same logic, there’s pitfalls when using multi-threading as well, even in languages where it’s native (e.g., Elixir).

Regardless, in my experience, when you run into scenarios that need queueing, multi-threading, etc., you need to know what you’re doing.

Re:A Deep Dive into Solid Queue for Ruby on Rails on Monday June 23, 2025 @08:05PM (#44361501)
I’ve never felt like “throw everything into a queue” was a mindset within the Ruby community, nor have we done that at my companies. And multi-region is a business decision.
Re:A Deep Dive into Solid Queue for Ruby on Rails on Monday June 23, 2025 @07:43PM (#44361374)
Neither sticking everything into a queue nor going multi-region are Ruby’s fault.
Re:Zed: The Fastest AI Code Editor on Wednesday May 07, 2025 @11:26AM (#43916949)
I didn't insist that. Understood, but specifically, I was talking to the comment I replied to, which was about 1440p monitors in particular.
Re:Zed: The Fastest AI Code Editor on Wednesday May 07, 2025 @09:09AM (#43915157)
Are you using enlarged text or native 1440p? If the latter, have you used 4k or retina displays in the past? It’s hard to go back after that.
Oh interesting, good to know.
Ahhh got it, this is focusing primarily on load balancing at a lower layer of routing then than what I'm referring to. While not wrong, "global load balancing" threw me off a bit.

EDIT: see the other reply, appears that it handles both given it leverages Fly's Anycast setup.

This is excellent, but I'm not following how the multi-region deployments work. Is Anycast involved in this somehow?
And Godot
Re:RubyLLM: A delightful Ruby way to work with AI on Saturday March 15, 2025 @08:25PM (#43376090)
Respectfully, your response further qualifies what I meant by your take being an always/never. I’m aware you’re the one who put “almost” in there, and I didn’t meant to imply you were being stubborn with that take, that’s why I said (and genuinely meant) that I respect it.

But I’m also aware that you’re comparing using global state to amputating a human limb. I don’t think it’s nearly that extreme. I certainly wouldn’t say global state “almost always leads to bad architecture,” as evidenced by my aligning with a framework which has a whole construct for globals baked into it (Rails’ Current singleton) that I happen to enjoy using.

Sure, global state is a sharp knife, which I already said. It can inflict pain, but it’s also a very useful tool in certain scenarios (more than would equate to “almost [never]” IMO).

So your response aligns with how I took your original post, and what I inferred “almost” really meant: basically never. My point is that I don’t agree with your take being a “rule.” While I understand your perspective, instead of saying basically never, I would say, “it depends.”

Re:RubyLLM: A delightful Ruby way to work with AI on Saturday March 15, 2025 @11:40AM (#43373213)
“Almost” is key there. I respect your position, but it’s an always/never take, and the longer I am in this industry, the more I find myself leaning into “it depends.” Here’s a take that articulates this being done well on a large codebase better than I can in a short comment: https://dev.37signals.com/globals-callbacks-and-other-sacril...
Re:RubyLLM: A delightful Ruby way to work with AI on Saturday March 15, 2025 @10:01AM (#43372593)
You’re describing the pain of poor architecture rather than the pain of global state. The tool itself is neutral. Sharp knives and all that.
Re:Macrodata Refinement on Sunday February 02, 2025 @01:21PM (#42910514)
Seconded
Re:Show HN: Browse Anime from the Terminal on Tuesday January 28, 2025 @08:16AM (#42851947)
Wow, this is an incredibly robust CLI. One of the more feature complete (and aesthetically pleasing) terminal UIs I’ve seen. Well done!
It sounds like that term (“H1Bs”) is simply shorthand for foreign citizens that are potential candidates for U.S. work via an H1B visa. Why is that bothersome?
Re:Rails for Everything on Thursday January 02, 2025 @12:14AM (#42571844)
Genuinely, I don't understand this take. 2024 brought huge additions like Solid Cache, Solid Queue, and Solid Cable, the stable version of Strada (Hotwire Native) which completed the current vision for the Hotwire stack, in addition to Kamal (let's not sell that short, because whether you personally like it or not, it's a fairly robust tool for what it's meant for) and other niceties. Even if you don't like one/all of these, I don't understand seeing these as small advancements of the framework, particularly in a single year.
Re:Building Game Prototypes with LÖVE on Wednesday January 01, 2025 @04:37PM (#42569519)
Yes, but most other engines are much larger scope and fundamentally different purpose than LÖVE. DragonRuby, however, is in the same camp: code-first, scripting language (Ruby vs Lua), beginner-to-expert friendly. So my point was there are (at least one) project(s) very similar in purpose and size/scope to LÖVE that did solve for cross platform.
Re:Building Game Prototypes with LÖVE on Wednesday January 01, 2025 @09:42AM (#42566261)
DragonRuby did it: https://dragonruby.org/
Re:Building Game Prototypes with LÖVE on Wednesday January 01, 2025 @12:12AM (#42564117)
Preach! Similar experience here. Agreed on Lua too. Love that some people dig Lua; to each their own, it’s just not for me.
Re:Building Game Prototypes with LÖVE on Wednesday January 01, 2025 @12:10AM (#42564109)
> DragonRuby seems to be a closed source proprietary game engine

Yes, but check out: https://docs.dragonruby.org/#/misc/faq?id=dragonruby-is-not-...

And

https://docs.dragonruby.org/#/misc/faq?id=what-if-i-build-so...

> If you get stuck in DragonRuby there’s probably not a huge amount of docs/tutorials around it.

You’d be surprised. The docs are extensive and there are sample games galore in the distro. https://docs.dragonruby.org/#/

Also the Discord is incredibly helpful and the creators chime in regularly.

It’s a pretty special engine and community IMO

Older »