Comments URL: https://news.ycombinator.com/item?id=47818685

Points: 4

# Comments: 2

> We also suspect that the geographical and cultural factors may have influenced interaction patterns, given that all our participants were residing in Türkiye.

Andrej Karpathy — “We’re summoning ghosts, not building animals”

I've considered just leaving the comments in, considering maybe they provide some value to future LLMs working in the codebase, but the extra human overhead in dealing with them doesn't seem worth it.

https://x.com/thdxr/status/1933561254481666466 https://x.com/meowgorithm/status/1933593074820891062 https://www.youtube.com/watch?v=qCJBbVJ_wP0

Gemini summary of the above:

- Kujtim Hoxha creates a project named TermAI using open-source libraries from the company Charm.

- Two other developers, Dax (a well-known internet personality and developer) and Adam (a developer and co-founder of Chef, known for his work on open-source and developer tools), join the project.

- They rebrand it to OpenCode, with Dax buying the domain and both heavily promoting it and improving the UI/UX.

- The project rapidly gains popularity and GitHub stars, largely due to Dax and Adam's influence and contributions.

- Charm, the company behind the original libraries, offers Kujtim a full-time role to continue working on the project, effectively acqui-hiring him.

- Kujtim accepts the offer. As the original owner of the GitHub repository, he moves the project and its stars to Charm's organization. Dax and Adam object, not wanting the community project to be owned by a VC-backed company.

- Allegations surface that Charm rewrote git history to remove Dax's commits, banned Adam from the repo, and deleted comments that were critical of the move.

- Dax and Adam, who own the opencode.ai domain and claim ownership of the brand they created, fork the original repo and launch their own version under the OpenCode name.

- For a time, two competing projects named OpenCode exist, causing significant community confusion.

- Following the public backlash, Charm eventually renames its version to Crush, ceding the OpenCode name to the project now maintained by Dax and Adam.

I struggled to find benchmark data to support this hunch, best I could find was [1] which shows a performance of 81% with Python/Typescript vs 62% with Rust, but this fits with my intuition. I primarily code in Python for work and despite trying I didn't get that much use out of LLMs until the Claude 3.6 release, where it suddenly crossed over that invisible threshold and became dramatically more useful. I suspect for devs that are not using Python or JS, LLMs have just not yet crossed this threshold.

[1] https://terhech.de/posts/2025-01-31-llms-vs-programming-lang...

I just pasted the YouTube link into AI Studio and gave it this prompt if you want to replicate:

reformat this talk as an article. remove ums/ahs, but do not summarize, the context should be substantively the same. include content from the slides as well if possible.

I couldn't find any great sources for the 200 plane flights number (and as you point out the article doesn't source this either), but I asked o1 to crunch the numbers (4) and it came up with a similar figure (50-300 flights depending on the size of the plane). I was curious if the numbers would be different if you considered emissions instead of directly converting jet fuel energy to watt hours, but the end result was basically the same.

[1] https://www.numenta.com/blog/2023/08/10/ai-is-harming-our-pl...

[2] https://www.ri.se/en/news/blog/generative-ai-does-not-run-on...

[3] https://knowledge.wharton.upenn.edu/article/the-hidden-cost-...

[4] https://chatgpt.com/share/678b6178-d0e4-800d-a12b-c319e324d2...

https://www.youtube.com/watch?v=PScOZzzXnDA

> Drinking 1–5 cups/day of ground or instant coffee (but not decaffeinated coffee) was associated with a significant reduction in incident arrhythmia, including AF. The lowest risk was at 4–5 cups/day for ground coffee (HR 0.83; 95% CI [0.76–0.91]; P <0.0001) and 2–3 cups/day for instant coffee (HR, 0.88; 95% CI [0.85–0.92]; P <0.0001).

tl;dr Yes it has similar benefits, maybe slightly worse than "ground coffee" (I wish they had broken it down more granularly)

Example from a project I worked on: I needed to test that when a button is clicked that the app showed a spinner when loading and then the content when the API call completed successfully. The spinner component was just an SVG with no obvious way to select it without adding a test-id, so instead I refactored the app to use an aria-busy attribute [2] in the container where the content is loading. The test then becomes something like this:

  test('shows spinner while loading and content after API call', async () => {
    render();

    userEvent.click(screen.getByRole('button', { name: /load content/i }));

    expect(screen.getByRole('main')).toHaveAttribute('aria-busy', 'true');

    await waitFor(() => {
      expect(screen.getByRole('main')).toHaveAttribute('aria-busy', 'false');
      expect(screen.getByText(/content loaded/i)).toBeInTheDocument();
    });
  });

I haven't tried it myself yet, not sure how well it works in practice.

Good explanation here if this still doesn't make sense: https://twitter.com/npew/status/1525900849888866307, or check out Andrej Karpathy's latest video if you have 2 hours for a deep dive: https://www.youtube.com/watch?v=zduSFxRajkE

IMO questions about spelling or number sense are pretty tired as gotchas, because they are all basically just artifacts of this implementation detail. There are other language models available that don't have this issue. BTW this is also the reason DALL-E etc suck at generating text in images.

https://dynomight.net/humidifiers/

I will say, having learned Colemak early on has made me give up on learning vim more than once for the same reason you highlighted -- I want to have my navigation on the homerow but the burden of remapping all of the keys without knowing what I'm doing was too high. I've heard that many people just use hjkl in the standard Colemak positions and don't remap keys at all, but that seems crazy to me, since they are spread all over and J is in the worst possible spot on the keyboard.

Comments URL: https://news.ycombinator.com/item?id=35337066

Points: 1

# Comments: 1