News for hackers. Stuff that matters.
Re:The Next Chapter in Swift Build Technologies by gruuuk on Saturday February 01, 2025 @07:09PM (#42903995)
They should have been fully open source with full linux support and parity since day one.

That would actually help the language get traction. At this point it's a dying language.

Re:The Next Chapter in Swift Build Technologies by tombert on Saturday February 01, 2025 @07:38PM (#42904197)
Is it dying? I think it's still pretty popular for app development isn't it?

I was pretty excited to hear that Ladybird is doing a lot of stuff in Swift, because I think it's a pretty decent and fast language and I think it'd be pretty neat to see a browser written in it.

Re:The Next Chapter in Swift Build Technologies by flohofwoe on Sunday February 02, 2025 @06:20AM (#42907945)
It's essentially "Big in Japan" (eg on Apple platforms but nowhere else). Even on Apple platforms I winder if ObjC is actually still more popular ;)
Re:The Next Chapter in Swift Build Technologies by Longhanks on Sunday February 02, 2025 @08:33AM (#42908533)
Well if you wonder you should conduct some simple research, but be prepared to have your opinion challenged. Swift ist doing very fine and much more popular than ObjC (again, if you don't believe it, invest 5 minutes into research).
Re:The Next Chapter in Swift Build Technologies by ChrisMarshallNY on Saturday February 01, 2025 @08:04PM (#42904446)
> At this point it's a dying language.

I disagree.

Source: Someone who has been programming Apple since 1986, and have heard last rites being administered to Apple, many times.

Re:The Next Chapter in Swift Build Technologies by lawgimenez on Saturday February 01, 2025 @08:25PM (#42904610)
Come on now, iOS development is my livelihood.
Re:The Next Chapter in Swift Build Technologies by napierzaza on Saturday February 01, 2025 @08:27PM (#42904627)
No one uses Apple platforms - sent from my iPhone
Re:The Next Chapter in Swift Build Technologies by fastball on Saturday February 01, 2025 @09:56PM (#42905261)
What language are you using to develop native apps for macOS and iOS and visionOS and watchOS, since Swift is dying?
Re:The Next Chapter in Swift Build Technologies by jayd16 on Saturday February 01, 2025 @10:57PM (#42905671)
C#, Unity.
Re:The Next Chapter in Swift Build Technologies by pjmlp on Sunday February 02, 2025 @01:53AM (#42906637)
Which rely on a mix of Objective-C and Swift APIs to actually interact with the platform.
Re:The Next Chapter in Swift Build Technologies by jayd16 on Sunday February 02, 2025 @03:39AM (#42907184)
What's your point? That's what Apple makes available. I'd use the C# API if that's how they provided it.

If not dominating the games on those plarforms, Unity and C# have a strong footing to say the least. Swift doesn't seem to be making very much headway on platforms where APIs are available in anything else.

Maybe that can chance. It seems like a neat language but "it's popular because apple forces you to use it" is more damning than reassuring.

Re:The Next Chapter in Swift Build Technologies by pjmlp on Sunday February 02, 2025 @05:39AM (#42907799)
The point is that they are guest languages on Apple ecosystem and need Apple tooling and languages as means being available.

I may also add that I dislike Microsoft doesn't give to the .NET ecosystem the same care for games developers as Apple does for Swift and existing OS SDKs.

As far as DirectX team is concerned, only C++ exists, and .NET team lets third party folks do the needful.

Had it not been for MonoGame, Unity would never picked C# in first place, gone were the days of Managed DirectX and XNA, when the decision came to be as Unity did their cross-platform rewrite out of OS X.

Re:The Next Chapter in Swift Build Technologies by jayd16 on Sunday February 02, 2025 @01:05PM (#42910387)
The specifics of C# are fairly irrelevant. Point is that even if swift is forced, middleware can and will just plaster over that. Even if Metal is forced, tools can plaster over that.

Apple forcing an API is not enough to sustain a language's popularity.

Re:The Next Chapter in Swift Build Technologies by pjmlp on Sunday February 02, 2025 @01:45PM (#42910719)
When the language is required for one of two mobile ecosystems, and second major desktop ecosystem, popularity is relative.

For decades C# was only relevant on Windows, outside Unity never got wide adoption among AAA studios after Unreal became free, and after their license debacle less so, Godot favors C++ and GDScript even with C# support it isn't what most folks reach for, and Microsoft keeps having an adoption (popularity) problem on UNIX culture oriented startups.

While just like Swift on Apple's ecosystem, C# is doing just fine on Microsoft culture environments.

Popularity is relative.

Re:The Next Chapter in Swift Build Technologies by paulddraper on Saturday February 01, 2025 @10:03PM (#42905319)
Lol, as long as it’s the preferred programming language for the most lucrative consumer devices ever, it cannot die.

Impossible to argue otherwise.

Re:The Next Chapter in Swift Build Technologies by technol0gic on Saturday February 01, 2025 @10:42PM (#42905595)
trolling for reactions is trite and predictable
Re:The Next Chapter in Swift Build Technologies by sgt on Sunday February 02, 2025 @02:16AM (#42906769)
There's a lot more buzz and activity around Swift than many other languages. It's literally up there with Rust, in terms of excitement (perhaps not quite as high). But I think if they get excitement outside of the Apple ecosystem, things should start to get super interesting.

Some are already adopting it like Ladybird browser.

Re:The Next Chapter in Swift Build Technologies by dzikimarian on Sunday February 02, 2025 @04:27AM (#42907445)
Sorry to be mood killer, but I think that might be your bubble. That's a first news about Swift I've seen in a long time and I don't see a reason to try it, given alternatives. Nowhere near Rust level of presence in discussion.
Re:The Next Chapter in Swift Build Technologies by homebrewer on Sunday February 02, 2025 @06:13AM (#42907916)
If we're trading anecdotes, I'll share mine as someone's who's completely outside of Apple ecosystem and is not interested in it in the slightest: I only ever hear about Swift on HN, nowhere else. Most of my colleagues, friends and acquaintances (who is in IT, but none of whom are Apple users) don't even know it exist, while everyone has at least heard about Rust. We all live in bubbles, admit it.