hn-acct

I personally don’t find it readable at all.

In my bubble I only see right winger influencers using it.

I tried clicking one of those just to see and it didn’t even go to the alleged product but instead a landing page with even more of those ads! Shocking, I know :)

It’s horrible on mobile. Sites like macobserver are bad. Two videos overlapping, popping in and out, shifting content.

swift --version is showing 6.2.4 for me

They said they made a "small swiftUI" app that leaks memory. From their shared link there is no SwiftUI at all. No clue....

The funny thing about the low effort parent comments is the truth - wikipedia lists that there are more release builds of swift of linux than for macOS. Granted they were bug fixes but still.

https://github.com/swiftlang/swift-evolution/blob/main/propo...

https://github.com/swiftlang/swift-evolution/blob/main/propo...

https://github.com/swiftlang/swift-evolution/blob/main/propo...

https://github.com/swiftlang/swift-evolution/blob/main/propo...

All of these changes improve the ergonomics of async/await. Fewer hops and a better alignment of when one would expect a hop to occur.

https://github.com/swiftlang/swift-evolution/blob/main/propo...

async defer is nice too but it's not in the 6.2 public release AFAICT.

First, op should mention which ones but they won't.

Just forget everything you've learned about it previously, use 6.2+, non isolated by default and every upcoming feature turned on. And your intuition will be spot on.

https://www.swift.org/blog/announcing-windows-workgroup/ https://www.swift.org/blog/exploring-the-swift-sdk-for-andro... ?

I'm also wondering how big their programs are that the compile times are an issue. I'm seeing fantastic build times with Xcode 16 and Xcode 26.2 with swift 6.2 it's even better. SPM is also better with the newer version. Most issues can be solved or exposed by closing the window and reopening or going to the package with issues and pressing cmd+s.

Agreed. People use any thread mentioning swift to dunk on Apple for X number of reasons with vague details and regurgitated dogma. I get Xcode has quirks I use it everyday believe me I know but it's not that bad that it's unusable.

Other IDEs do this too btw

Small views and the preview canvas are your friend

Do people actually believe that there are too many keywords? I’ve never met a dev irl that says this but I see it regurgitated on every post about Swift. Most of the new keywords are for library writers and not iOS devs.

Preventing deadlock wasn’t a goal of concurrency. Like all options - there are trade offs. You can still used gcd.

Actually though. We had one device that was over 10 years older without any MDM etc. and it outperformed a new laptop building the same product because of the corporate anti virus crap.

Why does this site work better on mobile than the real google suite. Funny stuff

Sure but PMs are billed lower than devs from my experience. You might have 1-3 on this project.

I wasn’t aware objc was considered “fast”.

Hyperbole

Same here. I rarely run into this problem. I write mostly SwiftUI too. I will admit there are some built in SwiftUI views that are problematic: tables, outline groups.

Most of the time it’s a syntax error or typo.

The developer experience is worse for an iOS developer.

How do you quantify or decide an acceptable failure rate for llm output?

If amateurs can use game porting and achieve decent results then I think the actual devs can achieve excellent results.

My guess is that Mac users simply don’t buy games for their macs

Thanos snap it if you’re using ios

It’s opt in. Very explicitly opted in. Did you read the post? Because it improves actors and makes it easier for app devs and general programming use cases. Honestly I don’t get the “sky is falling” mentality towards swift because a feature they won’t use or are affected by is added.

“Due to these insane changes” Which changes?

There is a two parameter onChange modifier btw

Everything probably already is or should be

Remind me in 6 months.