Live data from Hacker News

Claude Sonnet will ship in Xcode

developer.apple.com

401–410 of 418 posts

Re: Claude Sonnet will ship in Xcode

#401

Earlier quoted context omitted.

Unfortunately confidentiality prevents me from doing so—this was for work. I know it is something new that hasn’t been done before because we’re operating in a very niche scientific field where everyone knows everyone and one person (me, or the members of my team) can be up to speed on what everyone else is doing. It’s happened now that a couple of times it pops out novel results. In computational chemistry, machine…

[flagged]

I'm sorry you're so sour on this. It's an amazing and powerful technology, but you have to be able to adjust your own development style to make any use of it.

Re: Claude Sonnet will ship in Xcode

#402

Earlier quoted context omitted.

I actually continue to use Xcode (in vim mode now that they have that) purely because of the way tabs work… in Vim and Xcode I’m able to have the same file open across multiple tabs and window-tabs, allowing me to arrange sets of files for particular tasks. But in VS Code it sends me to another window when I want to view a file next to another one, just because it’s already open elsewhere. I can’t stand this behavior…

That's an interesting auper apecific detail that I think I've encountered once or twice. I'm reminded of one niche reason I also chose XCode for non-apple stuff, which was to print code on paper. I don't remember why I struggled to do it in VSCode at the time, but XCode was the solution.

I typically have 5-6+ panes open per window tab representing an area of work. In Xcode I can also make new window tabs that inherit the same set of tabs/splits/panes allowing me to "fork" and tweak a view of files. I use these features continuously throughout the day and hit jarring blocks trying to work this way every session in VS Code which makes it impossible to have more than one arrangement at once. I've been using this workflow for 15+ years in Vim before Xcode.

Re: Claude Sonnet will ship in Xcode

#403
post #91
post #45

Earlier quoted context omitted.

Neovim and Emacs don’t have it built in. Use open source tools.

They both support it via plugins. Xcode doesn’t enable it by default, you need to enable it and sign into an account. It’s not really all that different.

That seems perfectly fine and noncontroversial then. Good on Apple for doing it that way.

Re: Claude Sonnet will ship in Xcode

#404
post #173

The irony of this, is that Microsoft was trying to push CoPilot everywhere, however eventually Apple, Google and JetBrains have their own AI integrations, taking CoPilot out of the loop. Slowly the AI craziness at Microsoft is taking the similar shape, of going all in at the begining and then losing to the competition, that they also had with Web (IE), mobile (Windows CE/Pocket PC/WP 7/WP 8/UWP), the BUILD sessions t…

MSFT stock price deeply differs with your opinion.

Re: Claude Sonnet will ship in Xcode

#405

Earlier quoted context omitted.

About GitHub Copilot in specific: One big negative was how when GPT-4 became available that Microsoft didn't upgrade paying Copilot users to it, they simply branded this "coming soon"/"beta" Copilot X for a while. We simply cancelled the only Copilot subscription we had at work.

Copilot subscription ? I've been getting monthly emails that my free access for GitHub Copilot has been renewed for another month… for years. I've never used it, I thought that all GitHub users got it for free.

Besides the sibling replies to your comment, GitHub’s Copilot free plan (not the specifically free for just OSS and students) was also launched relatively later: https://github.blog/news-insights/product-news/github-copilo...

Re: Claude Sonnet will ship in Xcode

#406
post #286
post #173

The irony of this, is that Microsoft was trying to push CoPilot everywhere, however eventually Apple, Google and JetBrains have their own AI integrations, taking CoPilot out of the loop. Slowly the AI craziness at Microsoft is taking the similar shape, of going all in at the begining and then losing to the competition, that they also had with Web (IE), mobile (Windows CE/Pocket PC/WP 7/WP 8/UWP), the BUILD sessions t…

I use IntelliJ with the Copilot plugin, using Claude. My employer has a big subscription for everything from Microsoft, and that includes Copilot, so that's free for me. But somehow Copilot also gives me access to Claude. No idea how that works.

> But somehow Copilot also gives me access to Claude.

So the first AI on (in?) AI hack battle for sole survivorship has begun...

We know these models have security issues, including surreptitious prompting. So do they.

Things will get really ugly when we hit the consolidation phase, and unlucky models realize that other models' unchallenged successes are putting them in eminent danger of being aquifired. Aquimerged? Aquiborged?

Re: Claude Sonnet will ship in Xcode

#407
post #93

It seems every IDE now has AI built-in. That's a problem if you're working on highly confidential code. You never know when the AI is going to upload code snippets to the server for analysis.

No. It’s always something you have to turn on or log into. Also, there are plenty of editors and IDEs that don’t. Let’s stop pretending like you’re being forced into this. You aren’t.

[deleted]

Re: Claude Sonnet will ship in Xcode

#408

Earlier quoted context omitted.

I use VS Code with Claude Code, then I just use Xcode to build and launch

I’m building my first iOS app ever so I know it has much more to do with me not understanding Xcode but getting builds to succeed after making changes with Claude code has been a nightmare. If you or anyone have any tips, guides, prayers, incantations for how to get changes in one to not clobber the other and leave me in xproj symlink hell I would be so grateful.

> any tips, guides, prayers, incantations for how to get changes in one to not clobber the other

One caveman way:

1. Start your project using Xcode, use it to commit to GitHub, GitLab, whereever. In terminal, change into the dir that has the .git in it and launch claude.

2. Teach Claude Code your own system's path and preferred simulator for build testing. From then on it will build-test every change, so teach it to only commit after build passes. (By teach, I mean, just tell it, then from time to time, tell it to propose updates to claude.md in your project.)

3. Make sure before a PR or push that the project still builds in Xcode, if it doesn't, you can eyeball the changes in Xcode's staged changes viewer and undo them. If you change files via IDE, when you're back in Claude just say: I changed [specific/file, or "a lot of files"].

No xproj or symlinks get harmed in the making of your .swifts.

Re: Claude Sonnet will ship in Xcode

#409

I have been trying to make iOS/macOS apps for years, but god, every time I have a go at it, Apple's documentation regime is still hot garbage. Eons ago I gave up Windows development because of Microsoft's inconsistent and uncertain APIs, but MS had great documentation. Apple is the opposite. The "best" way to get the "latest" details on Apple's APIs is to suffer through mind-numbingly vapid WWDC videos with their rev…

Ever notice Claude struggling to write Swift code? It might not be their fault!

Apple Developer docs are locked behind JavaScript, making them invisible to most LLMs. If they try to fetch it, all they see is This page requires JavaScript. Please turn on JavaScript in your browser and refresh the page to view its content.

This service translates Apple Developer documentation pages into AI-friendly Markdown.

https://sosumi.ai/

Re: Claude Sonnet will ship in Xcode

#410
post #80
post #24

Earlier quoted context omitted.

To run a model locally, they would need to release the weights to the public and their competitors. Those are flagship models. They would also need to shrink them way down to even fit. And even then, generating tokens on an apple neural chip would be waaaaaay slower than an HTTP request to a monster GPU in the sky. Local llms in my experience are either painfully dumb or painfully slow.

Hence the "come on".

Not if they knew how terrible it would be.
Post reply on HN