News for hackers. Stuff that matters.
Re:IINA – A modern video player for macOS by eridius on Monday January 09, 2017 @01:25PM (#13358469)
If you developed the libraries yourself, then you have a point. But if you're using someone else's library, which they maintain, then it seems reasonable to say your application is pure Swift.

Note that there's a difference between saying "my application is pure Swift" and "everything is pure Swift". If you're trying to make an argument about safety (as happens when people talk about writing things in Rust), then having the libraries written in that language is important. If you're just trying to say "this is a modern codebase using the latest tooling and APIs", then all that matters is the code you wrote, and not the pre-existing libraries that you link to.

Re:IINA – A modern video player for macOS by themihai on Tuesday January 10, 2017 @12:36PM (#13366808)
You turn this into a blame game. If it's pure Swift then 100% of its source code should be Swift. This particular repository is mixed with C libs.

From the dictionary:

Pure - not mixed or adulterated with any other substance or material.

Re:IINA – A modern video player for macOS by eridius on Tuesday January 10, 2017 @02:01PM (#13367801)
So, everything has to be Swift, except for the libraries that you personally have decided don't matter (such as libc)? That's not a very useful definition.