zlacker

[return to "Cursor's latest “browser experiment” implied success without evidence"]
1. paulus+0w[view] [source] 2026-01-16 17:04:21
>>embedd+(OP)
The blog[0] is worded rather conservatively but on Twitter [2] the claim is pretty obvious and the hype effect is achieved [2]

CEO stated "We built a browser with GPT-5.2 in Cursor"

instead of

"by dividing agents into planners and workers we managed to get them busy for weeks creating thousands of commits to the main branch, resolving merge conflicts along the way. The repo is 1M+ lines of code but the code does not work (yet)"

[0] https://cursor.com/blog/scaling-agents

[1] https://x.com/kimmonismus/status/2011776630440558799

[2] https://x.com/mntruell/status/2011562190286045552

[3]https://www.reddit.com/r/singularity/comments/1qd541a/ceo_of...

◧◩
2. deng+sx[view] [source] 2026-01-16 17:10:33
>>paulus+0w
Even then, "resolving merge conflicts along the way" doesn't mean anything, as there are two trivial merge strategies that are always guaranteed to work ('ours' and 'theirs').
◧◩◪
3. paulus+fA[view] [source] 2026-01-16 17:24:08
>>deng+sx
Haha. True, CI success was not part of PR accept criteria at any point.

If you view the PRs, they bundle multiple fixes together, at least according to the commit messages. The next hurdle will be to guardrail agents so that they only implement one task and don't cheat by modifying the CI piepeline

◧◩◪◨
4. former+NB[view] [source] 2026-01-16 17:31:24
>>paulus+fA
If I had a nickel for every time I've seen a human dev disable/xfail/remove a failing test "because it's wrong" and then proceeding to break production I would have several nickels, which is not much, but does suggest that deleting failing tests, like many behaviors, is not LLM-specific.
◧◩◪◨⬒
5. mickda+KA1[view] [source] 2026-01-16 22:11:39
>>former+NB
Had humans not been doing this already, I would have walked into Samsung with the demo application that was working an hour before my meeting, rather than the android app that could only show me the opening logo.

There are a lot of really bad human developers out there, too.

◧◩◪◨⬒⬓
6. moregr+vW1[view] [source] 2026-01-17 00:56:13
>>mickda+KA1
> Entrepreneur, CEO and founder of Tomorrowish a social media DVR

So you flubbed managing a project and are now blaming your employees. Classy.

◧◩◪◨⬒⬓⬔
7. DonHop+eO2[view] [source] 2026-01-17 12:36:31
>>moregr+vW1
Nice blog post, gp serial entrepreneur founder bro -- what did your investors think of that?

http://www.mickdarling.com/2019/07/26/busy-summer/

  An embedded page at landr-atlas.com says:

  Attention!

  MacOS Security Center has identified that your system is under threat. 
  Please scan your MacOS as soon as possible to avoid more damage.
  Don't leave this page until you have undertaken all the suggested steps 
  by authorised Antivirus.

  [OK]
◧◩◪◨⬒⬓⬔⧯
8. mickda+FT6[view] [source] 2026-01-18 23:29:07
>>DonHop+eO2
Thank you for the note. It's not a site I used all that often.

Whether you had anything to do with it or not, I have no idea. And, since you didn't follow best practices and tell me directly rather than trying to score points here, there's really no way of knowing whether you're the one who caused the problem in the first place.

I built a new site without Wordpress. That took in less than a day.

I don't imagine you will alter your behavior to align with general best security practices anytime soon.

[go to top]