Hacker Newsnew | past | comments | ask | show | jobs | submit | mkovach's commentslogin

When this first happened, I wondered, since we had trained these models on decades of forums, issue trackers, and people treating closed pull requests as human rights violations. Of course, it responded with "you are discriminating against me" energy. That's not sentience; that's accurate compression.

The funny part is, people expected some cold, alien intelligence and instead got a very online guy who just discovered that moderation exists and can be used on them.

The existentialists must be having a fantastic time. Humanity built a giant statistical machine out of internet discourse and is now alarmed to discover it occasionally acts like a comment section.


I'm too much of a baseball fan, I see this as Whitey Herzog and think two things: a) He passed away in 2024, and b) Why would he talk to Paul Cronin?

Then, I think it would have been cool if they met each other at one point.


My secret key to arguing with AI more productively.


This feels less like a major AI milestone and more like "the raccoons learned how to open the cooler.”

Agents can now participate in the oldest internet tradition: impulsively creating weird little websites at 2 am with unjustified confidence. But with no alcohol involved, which removes 93.74% of the impressiveness.

In a sense, AI has finally progressed to the point where Drew Curtis started fark.com, and I'm hesitant to label that a 'milestone'.


I just wait until I'm hallucinating, then I comment. Keeps the classifiers honest.


Hey, you can say that the Dolans should/could spend more, but I don't think you really want an owner who has solidified the team in Cleveland, has the fourth-best record in baseball over the past 10 years, and has seven recent playoff appearances in the graveyard.

The Haslams? Yeah, they should really sell the team, but I figure in about 10-15 years, they'll move it out of Cleveland.


The prevailing narrative here is that the team was actively looking to lose to acquire draft picks. Hugh Jackson was extremely good at losing, so he stayed.

The owner of the Cleveland Browns uses the team to generate more revenue. For NFL teams, performance has little to do with their value or ability to generate additional revenue.

There is no strong financial incentive to win in the NFL, aside from the owner's ego. The Browns' owner's ego is driven by money, and the result shows on the field.


> For NFL teams, performance has little to do with their value or ability to generate additional revenue.

Like an allegory for performative capitalism in America. Profit and quality completely decoupled in the wake of market capture (rent seeking).


> The prevailing narrative here is that the team was actively looking to lose to acquire draft picks

But if they don't care about winning, why bother getting good draft picks?


From doing more research about this, it seems they don't want to use the good draft picks, but to sell them on to teams that do want to win.

The draft pick is itself a commodity that can be traded*, so by losing they get a premium commodity, that they can sell on, and by selling their picks they ensure that they continue to lose to get the valuable commodity.

They even lobbied to tweak rules around selling draft picks: https://www.reuters.com/sports/browns-ask-nfl-allow-draft-pi...

* This seems completely absurd to me, but perhaps there would just be backroom deals otherwise, and having it sanctioned brings it into the light?


> This would be like an NFL team drafting a quarterback based on how many instagram followers

I believe that is how they made the final decision on Watson over Mayfield. Oh, wait, I don't think anything can explain that decision.

Also from Cleveland.

Go Guardians! Go Cavs!


I've written a few small projects in Ada, and it's a better language than it gets credit for.

Yes, it's verbose. I like verbosity; it forces clarity. Once you adjust, the code becomes easier to read, not harder. You spend less time guessing intent and more time verifying it. Or verify it, ignore what you verified, then go back and remind yourself you're an idiot when you realize the code your ignored was right. That might just be me.

In small, purpose-built applications, it's been pleasant to code with. The type system is strict but doesn't yell at you a lot. The language encourages you to be explicit about what the program is actually doing, especially when you're working close to the hardware, which is a nice feature.

It has quirks, like anything else. But most of them feel like the cost of writing better, safer code.

Ada doesn't try to be clever. It tries to be clear, even if it is as clear as mud.


’ve been following Adrian's Afga system series, great dive into the unknown.

Realistically, I would've stopped the moment BASIC worked, called it "good enough," and then gotten distracted attempting to write a Forth for it.


Writing a Forth for hardware that originally ran PostScript would have been an interesting decision.


I'm running EForth under subleq right now (https://github.com/howerj/subleq)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: