Hacker News .hnnew | past | comments | ask | show | jobs | submit | alwillis's commentslogin

From the docs:

CLAUDE_CODE_NEW_INIT

Set to 1 to make /init run an interactive setup flow. The flow asks which files to generate, including CLAUDE.md, skills, and hooks, before exploring the codebase and writing them. Without this variable, /init generates a CLAUDE.md automatically without prompting.


> Jokes aside I find it hard to trust in the amount of things Anthropic throws out. It can’t be a well thought out and stable product this way.

I've never seen any company iterate on a product as quickly as Anthropic has with Claude. When you drill down into the details, it is well thought out and stable and well documented.

It seems the feedback loop is so fast, they address issues before they can fester into major problems. The entire company uses Claude; there's not better dogfooding than that.

It reminds me of how, back in the day, when continuous integration and continuous deployment were new; it seemed nuts to push code to production every day. And now, it's the norm.


> Yeah I’m honestly not sure why macOS updates seem to be so huge.

An update to macOS 26.5 contains all the necessary code to update a Mac from 26.0 to 26.5 for both x86_64 and arm64 architectures.


But aren't they able to do incremental builds and separated x64/arm64?

They know which OS version is requesting an update, at least the version number part.


> But aren't they able to do incremental builds and separated x64/arm64?

During the PowerPC to Intel transition, they did stuff like that; perhaps at their current scale, there's reasons why they don't.

Supporting both architectures enables a macOS install to boot an Intel Mac or an Apple Silicon Mac, which is useful in a dual-architecture environment.

It's easy to check for dual architecture support; just use the file command:

    $ file /bin/ls
    /bin/ls: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e]
    /bin/ls (for architecture x86_64): Mach-O 64-bit executable x86_64
    /bin/ls (for architecture arm64e): Mach-O 64-bit executable arm64e

Is that an over the air update? Lol.

BBEdit has had support for Claude, OpenAI and Ollama (or any OpenAI-compatible LLM) in their AI Chat Sheets feature [1].

[1]: https://www.barebones.com/products/bbedit/bbedit15.html#:~:t...


I've been using BBEdit since the System 7 days or thereabouts. Then I discovered Vim and I was hooked. And then came Neovim, which is still my daily driver.

BBEdit has been my never-fail backup editor, especially for Mac-specific tasks. It's been a little awkward because of my Vim muscle memory. Glad to see they're adding Vi/Vim keybindings, which I've wanted for a long time.


> No, we should not praise software companies for hobbyist practices like selling $1 app on the App Store, which say, 30% goes to a digital distribution store, and then of your after distribution fees, about 20%+ percent goes to the federal and local government.

For hobbyists with revenue less than $1 million per year, the App Store commission is 15%.


You can use Language Server Protocol (LSP) in Claude Code; no more regexes [1].

[1]: https://code.claude.com/docs/en/discover-plugins


> I strongly suspect that the "coming soon" part of this means "after we integrate Google Gemini models into the system…"

I don’t think the Google's tech has anything to do with these features.

This would had to have been in the works long before the Google announcement. Also, these are enhancements of existing iOS and macOS features. They don’t require an LLM anyway; these features use Apple’s Machine Learning models.

For example, creating subtitles for videos? iOS 16 introduced Live Captions for FaceTime calls in 2022 [1].

[1]: https://www.apple.com/newsroom/2022/05/apple-previews-innova...


The "coming later this year" language is disappointing to some people, but that's just Apple propriety. Allow me to explain.

"Coming later this year" means it's part of a publicly committed release — iOS 27, macOS 27, etc. — not vaporware.

The annual pre-WWDC accessibility announcement is a tradition, and with the conference less than a month away, expect more detail then. New a11y features have a good chance of appearing in the 10am PT keynote or the Platforms State of the Union, the developer-focused follow-up at 1pm PT.

That said, things are still fluid with three weeks to go — features can be added or pulled at any time. If something gets bumped from the main presentations, there will almost certainly be a dedicated video session covering it.

As for availability: some of these features will land in the iOS 27 and macOS 27 betas, which drop during WWDC for Apple Developer Program members. The public beta follows in July, and there's a free tier of the developer program if you want early access.

Don't expect everything at once, though. Some features won't arrive until the September release candidates — and even then, a few may ship labeled "beta" or "experimental," or hold for a future dot release.


> This has to be somewhat anti-competitive.

I don’t think so. They were available to anyone with the money and Anthropic acted first.

I doubt attempting to hurt OpenAI was the primary reason for the acquisition.

Maybe it’s different now; Bill Gates “wanting to cutoff Netscape’s air supply” and threatening to cancel the Windows license of PC manufacturers who shipped Netscape’s browser on their PCs… now that’s anticompetitive. They had 95% market share.

Bill was like “That's a nice PC business you have there; would be a shame if something were to happen to it.”


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

Search: