Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "swift package"
-
Wow, my girlfriend has been really efficient wrapping and organising the presents under the tree... You could say she’s a Swift Package Manager!!3
-
If programming languages had honest slogans, what would they be?
-C : Because fuck you.
-C++ : Fuck this.(- Dan Allen )
-Visual Basic : 10 times as big but only 5 times as stupid.
-Lisp : You’re all idiots.
-JavaScript : You guys know I’m holding up the internet, right ?
-Scala : That was a waste of 4 weeks.
-Go : Tell me about it, Scala.
-Python : All we are saying, is give un-typed a chance.
-R : Whoa, I was supposed to be a statistics package!
-Java : Like a Roomba, you guess it’s OK but none of your friends use it.
-PHP : Do Not Resuscitate.
-Perl : PHP, take me with you.
-Swift : Nobody knows.
-HTML : No.
-CSS : I said no.
-XML : Stop.
Source:@Quora: https://quora.com/If-programming-la...6 -
Dear xcode,
you fckn bitch did it again. I really wanted to do some iOS development, I swear. But you are like an abusive relationship, I have this weird habit of coming back to you even though I am getting fucked in the ass in parallel.
I love Swift but I despise you xcode. Randomly fucking up my workflow, and then it is clean build folder, reset package cache, restart xcode. Again and again and again you fuck things up out of nowhere. And from time to time, you just have to install the newest version of xcode because its so fucked up its easier to download this MASSIVE asshole than to even try to fix anything if you know its just xcode again.
Yeah, fuck extensions and formatting. Just fuck humanly tolerable build time. Fuck you xcode.
I am not an experienced dev with iOS nor am I a common Mac user but this is just wrong. I feel violated and the joy of development sucked out of my soul while I try to navigate through the overloaded interface.
I am not even going into details about iOS development, its just that xcode is the gatekeeper to get me the fuck out of this miserable place that is native iOS development.
Arrivederci, suckers.4 -
Use Swift Package Manager, they said.
I'll be great, they said.
"Note that at this time the Package Manager has no support for iOS, watchOS, or tvOS platforms." - https://github.com/apple/... -
why can't apple even provide a consistent interface to load swift package? "add package dependency" interface allows you to add remote package, but doesn't allow you add local in development swift package. to do that, you will have to "drag and drop"... why can't apple just add a button on the same interface for navigate local package? is this suppose to be some hidden up up down down left right left right konami secret thing?
-
when xcode fails to load swift package dependency, it just fail silently, it removes targets from my build menu quietly and say nothing about why that fail, leaving me stranded and confused and spent hours to figure out why the target defined in the package.swift file just doesn't show up. I remember "UX" used to be the buzz word Steve Jobs bragging about?1
-
Added vapor core swift package to my project so that I can use some of the extensions, had to `rm -rf ~/Library/Developer/Xcode/DerivedData/` to make xcode realise the repo is actually exist.
Then I set the Core package as dependency of one of the targets, XCode complaints "unknown package Core", ok fine then I remove Core dependency, Core complaints "dependency Core is not used by any target".
How can xcode comes to this contradicting conclusion is out of my imagination, it just never gonna be happy about however i write.1 -
in apple's blog they explained why they don't want a `protected` in swift:
https://developer.apple.com/swift/...
> It doesn’t actually offer any real protection, since a subclass can always expose “protected” API through a new public method or property."
Isn't the same thinking applies to `internal` keyword as well? Yet they allow `internal` to be there as default modifier for `class` in a package. Also I don't think `protected` is for the sole purpose of "protection", but for the cleanliness of externally visible interface, some methods are just useless to be exposed and will confuse the consumer if they don't understand internally how the class works. So it doesn't have to be 100% securely `protected` (arguably the term `protected` is a poor choice tho).
but hey, it is apple, being opinionated doesn't surprise me.6