Live data from Hacker News

Swift Package Index joins Apple

swiftpackageindex.com

31–40 of 85 posts

Re: Swift Package Index joins Apple

#31
post #5

Earlier quoted context omitted.

Or send in a PR for gitlab/… support?

They did not want that and discouraged it.

This is a genuinely interesting topic, and as we say in the blog post:

> Together, we’re building a comprehensive package registry to serve the Swift community’s evolving needs.

The great thing about a registry is that it doesn't care where the original source is hosted. We will be moving away from that model completely as we work towards this.

Re: Swift Package Index joins Apple

#33
post #25

Earlier quoted context omitted.

Swift on Linux has changed since a few years ago. A lot. I prefer Swift over rust as it has the same memory-safety guarantees with a much more approachable syntax, and is generally easier to work with.

The same condition is still true as the first time I was told "Swift on Linux" is somehow a first class experience: > Documentation for the standard library is presently hosted on the Apple Developer website. Sure enough, by Apple policy, the documentation pretends no non-Apple platforms exist. What happens for an API which could be different if your system isn't fruit-flavoured? They don't care and won't talk about…

> Is the feature I need available for this Linux device?

If it’s in Foundation, yes. Swift 6 on Apple OSes now (since a while ago actually) uses the same open-source foundation as Linux. If it’s a proprietary framework (e.g. TabularData), no. It’s simple.

For the rest, almost all Swift packages developed by Apple are fully compatible with Linux, and the documentation of said packages is usually explicit wrt. platform specifics, AFAIK.

Re: Swift Package Index joins Apple

#34
post #2

Not optimistic here. While I'm glad the SPI guys are getting paid (that is, a full time job), Apple is pretty bad at open source and developer services both, and they explicitly call out developer identity as a future direction, which doesn't fill me with hope.

I tried to get a personal developer account (I'm already a developer through an organisation). The app required a Driver's license as the only accepted ID. I don't drive because I'm blind. They did a screen share and talked me through applying on the web site. It failed. They never gave a reason and ignored me when I asked for one. They just said

"Hello Robert, Thank you for your patience while I awaited a response from our operations team.

Upon review, we have found that we can’t verify your identity with the Apple Developer app or provide further assistance with the Apple Account for Apple developer programs.

You can still take advantage of great content using your Apple Account in Xcode to develop and test apps on your own device. Learn more about Xcode development.

I do apologise that I was not of more help to you in this situation but wish you the best of luck for the future. "

They will destroy the developer experience when they add identity and signing.

Re: Swift Package Index joins Apple

#35
post #14

Earlier quoted context omitted.

It's a reference to Sherlock (and later Spotlight) being added to macOS, rendering the previous third-party search-launcher tools obsolete.

Thank you, I learned it today. On the other side, some users replaced Sherlock (Spotlight) with Alfred.

I think the Sherlock thing was in the OS 8 or OS 9 days whereas Spotlight didn’t come around until sometime in macOS X, maybe 10.4 or so?

Re: Swift Package Index joins Apple

#36
post #25

Earlier quoted context omitted.

Swift on Linux has changed since a few years ago. A lot. I prefer Swift over rust as it has the same memory-safety guarantees with a much more approachable syntax, and is generally easier to work with.

Easy and approachable sound pretty subjective to say the least; feature and syntax wise, Swift has become an absolute monster of a language. Rust's tooling and ecosystem are ahead and these points matter to me more than the raw syntax in the age of LLMs.

As per my experience, the learning curve of Swift is easier than rust’s. Yes, obviously, it’s subjective. Yes, if you want to do complex things in Swift (e.g. generic packs), the syntax is more complex, but that’s not needed every day.

As per the tooling, idk enough to report on that.

As per the LLMs remark, I do not use that at all, still, and hopefully never will, though I already know I won’t have the choice at some point, sadly.

Re: Swift Package Index joins Apple

#37
post #9
post #4

Earlier quoted context omitted.

This acquisition sounds like a sign that Apple wants to get better on that front.

That's a pretty low bar, and doesn't necessarily mean "good".

That’s right. Whenever a company does something that seems good let’s just start being mean.

If they’ve ever done something we don’t like we’re not allowed to celebrate anything.

Might send the wrong message.

Re: Swift Package Index joins Apple

#38
post #13

Earlier quoted context omitted.

What does Sherlocked mean?

It means Apple (or big tech) has adopted/cloned your product basically killing your products ability to succeed In reference to when Apple created a project called Sherlock that was a direct copy of a popular Mac app Watson

But here Apple seems like they avoided that by buying the project instead of creating their own clone. Doesn't that make it nothing lime the Sherlock/Watson situation?

Re: Swift Package Index joins Apple

#39
post #25

Apple has something with Swift similar to what Google has with Go. The language has a lot of desirable features for server development very much like Go and Rust. Especially when compared to Java and C#. It makes sense for them to build their services using Swift instead of something like Go and the Swift-on-server team has been doing a lot of work to get swift in a usable state on Linux. Having a thriving opensource…

Swift on Linux has changed since a few years ago. A lot. I prefer Swift over rust as it has the same memory-safety guarantees with a much more approachable syntax, and is generally easier to work with.

Isn’t there a performance cost though with runtime binding of functions? (I’ve not looked too closely at Swift since the first couple of years when Objective C compatibility was essential, so maybe that’s less of a default than it was in the early days).

Re: Swift Package Index joins Apple

#40

Earlier quoted context omitted.

It means Apple (or big tech) has adopted/cloned your product basically killing your products ability to succeed In reference to when Apple created a project called Sherlock that was a direct copy of a popular Mac app Watson

But here Apple seems like they avoided that by buying the project instead of creating their own clone. Doesn't that make it nothing lime the Sherlock/Watson situation?

Indeed, it seems like the honorable approach.
Post reply on HN