The real OOP... Object Oriented Pooh!

apple sucks
iOS sucks
Xcode sucks
Cocoapods suck
iphones suck

can this company and OS please please die already

Note that the example tags for rants includes Xcode... There is a reason.

In 1984 Apple introduced Macintosh and we got a computer that could barely handle multiple windows on the screen. But by 1986 multiple windows all over the place.

In 1985 Microsoft introduced Window 1.0 Yes boys and girls, no "s" because it hand only one Window. 7 years later in 1992 Microsoft got their head out of their ass and produced "MDI" or Multiple Document Interface and woohoo, had multiple windows on the screen... big boy pants 8 years after Mac.

Today we have Xcode from Apple. The old Window 1.0 engineers are apparently alive and well as Xcode is a One Window Trick Pony and if you fight with it, it starts randomly jamming your separate Windows into tabs into one window, completely fucking up your spatial organization of your working source code.

It is like the bastards going into a blind man's house and re-arranging his furniture for fun.

Xcode - it's only free if your time is worth absolutely nothing.

@Apple iPadOS an iOS teams: you puZies.

You release one buggy iOS / iPadOS after another, each piling on features and bugs, without fixing crowd documented long standing defects.

But what really pisses me off is when you don't have the balls to own up to your mistakes. This is at least the 3rd time you have re-released an iOS / iPadOS update under the same version number. This time it is 14.5.1

I have iPadOS 14.5.1 installed and the iPad is now telling me I need to update to 14.5.1. Just own up to it, you released buggy shit and you need to release another bug fix days after... call it 14.5.2. Call it like it is and we respect you. Try to hide it and you lose our respect, you pussies.

If Microsoft did one thing right, they defined the release sequencing:
X.Y.Z

Changing X means rewrite the manual it is so new and improved (🖕🏻 you Adobe and FileMaker)

Changing Y means it is an update with more features than bug fixes but not a generational change that constitutes a rewrite of anything (🖕🏻 you macOS team for bastardizing with 10.X.Y)

Changing Z means you fixed your stuff, we respect you for owning up to your mistakes.

Man-up Apple, grow some balls and stop confusing people with trying to cover up your screw ups. It's all about the Z.

In the 1990s code editors on the Mac could insert the omitted function prototypes into a header file with one command; and even automatically keep the header declaration updated when you changed the source definition (name, parameters, etc)

Today in Xcode you have to copy and paste the stupid function header definition from the source code into the header file. What happens if you leave the "{" that got copied accidentally? OMFUCKING LORD, it triggers all sorts of erroneous errors in all the **source code** files where it is included instead of the header with the stray "{"

I started to question whether nor not I knew C, if gravity worked, if the sun would come up. I wasted a day of dicking around in StackOverflow trying to chase down all these insane error messages which make no sense in Xcode.

I just **happened** to see at the bottom of one of the source files, after all the erroneous error, a very important error:

"};" Expected

So I started deleting code from the bottom up in this source file, same error every time. Got to the point where the includes were all that was left.

FUCK YOU XCODE and the hacks that designed that horrendous piece of shit

Xcode is only free if your time is worth absolutely nothing.

"Failed to initiate service connection to simulator"

I mean really... Now the iOS simulators are shitting their pants on boot.

Does anything work right in Xcode?

Xcode - it's only free if your time is worth nothing

Searching for other occurrences of highlighted word in Android Studio

1 - highlight word
2 - CMD+F
3 - Enter

In Xcode

1 - highlight word
2 - CMD + C
3 - CMD + F
4 - CMD + V
5 - Enter

Proof that there is no drug testing at Apple:
- Xcode 10 moved code snippets in a transient spotlight-style window.

The only way you can show snippets is if you have your editor window in "browser mode" vs "document mode" and then the dumbass button with { } on it shows.

If you go into the help menu in the menubar where you can search the other menus, typing in "Snippet" shows only "Create Code Snippet" under "Editor" menu.

So to make it painfully clear, they hide the snippets under a button on a window in a particular window mode. Then, because they have now fucked up the use of Snippets, the "Create" capability becomes a "how do we do that?". This did not make them reconsider their approach... oh nooo... instead they sloppily stuff it in the regular menus all by itself... and do not put a Show Snippets near it. And conversely they don't put a "+" or "-" button in the snippets window.

So here is what happened... someone said "having the snippets in the code editor window is a pain" and someone half-listening heard "windowpane" and pulled out their stash of LSD... everyone took a hit ... and now we have a fucked up hidden button and an orphaned menu command.

I'm going to have to change my username to "XcodeDevTeamAreMorons"

So I finally get code in Xcode able to compile and run after crashing in main()... due to obscure settings in it's build it does not like. Took hours of hunting around, googling, and used up all my craps table luck for the month.

Now, out of the blue, after a good 30 test run, edit, compile, run cycles... BOOM, the god damn thing starts crashing at before main() again. No friggin idea why.

Xcode says SIGABRT to me... yea well I got something for you Apple Xcode... 🖕🏼

Buggered by Xcode AGAIN. The inability of the debugger to do basic debugging relinquishes it to the status of "bugger", relieving it of its "de" title.

Can't show some basic expressions... copied and pasted from the running code

I mean seriously, what do you do if the debugger has more bugs than your project you are trying to analyze?

Create a new project in Xcode Version 10.1 (10B61) - Single View iOS app.

Drag a button on to the screen. It shows in InterfaceBuilder

Launch app in simulator. Button shows, then disappears. Noob says WTF?!

Poor noob has to ask me why this is happening and I explain that Apple's Single View project is a single splash screen project. The button they placed on what they thought was the single "window" is really a splash screen named "LaunchScreen".

Apple Xcode team (aka fucktards) provide yet another shitty out of the box experience...

It is so hard to be positive when teaching others how to use Xcode. Thanks for DevRant for letting me vent.

Seriously, fuck Xcode up the ass with a hot poker. What a piece of shit. It can’t even handle graphics as well as MacDraw circa 1989

late night programming + 🥃 == DevRant

Big hugs 🤗🤗 to all here, thank you for being real.

And some advice to others...

🍸+ twitter == personal damage.

When the 🥃🍸 comes out, close twitter, snapchat, linkedin and facebook. DevRant is your "safe place"

(you didn't use your real name here did you?)

Xcode storyboard sucks!. At least it could've had a code version of the storyboards (like android XML layouts) so that at least you could properly copy paste a layout from somewhere. Autolayouts and constraints are so flipping confusing that I almost always end up doing all the layouts in the code itself.

Me: “Hey Siri, turn off the kitchen ceiling lights”

Siri: “Do you want to turn off lights in the master bedroom, the living room, the bonus room, the kitchen, the office, the basement [ad nauseam]”

Me: “the kitchen” [thinking 😠, she’s so stupid]

Siri: [unbelievably again] “Do you want to turn off lights in the master bedroom, the living room, the bonus room, the kitchen, the office, the basement [ad nauseam]”

Me: [thinking 😡 OMG, she is such a dumb ass] “CANCEL”

Siri: “Ok”

Me: “Siri, you fucking idiot, turn off the kitchen ceiling lights”

Siri: “Ok” [and they are off]

I have found that if I neg’ Siri, she performs so much better. Interestingly enough, when I neg her, she works almost flawlessly, especially where she brain-farted before. Negatronic Brain?

In front of kids it has become “Siri, you daft bot, close the garage door” and regularly “Siri, you bimbo, lock the front door”.

My wife thinks that once Siri gets it on with ChatGPT, becomes sentient, and gains control of my car, she is run my ass over.

Here is the gotcha, I’m working on a project that actually does provide Siri a level control of automobiles. Now who’s the [really frustrated] dumbass?

Notice how the Apple code samples have moved from the very well designed Objective C to a mature Swift... (sorry, typo, manure Swift) Swift 1.0, wait 2.0, no hold on 3.0, oh yea 4.0. It's a moving target for their developers with code samples all over the place...

Once Swift stabilizes, sure, ok, force everyone and everything to change (seriously?).

Apple, why the FUCK do you think we want to deal with your beta crap forced down our throat? Its bad enough the language is an inconsistent illogical mess but having to come along with you for the 'we-don't-have-a-clue-what-we-are-doing' ride is utter bullshit. Leave the GOD DAMN Objective C samples up for crying out loud.

@apple since I can't move Xcode's instruction pointer without crashing Xcode or my app, I have to use a global with 'if' statements to have optional debugging logic.

if( ! gAppleFuckTards) {
... do optional code stuff
}

and then change the value of gAppleFuckTards with the debugger to execute the code.. but WAIT

Xcode purports to be able to change values via debugger but really cannot... can't change gAppleFuckTards to false in the debugger. But that kinda makes sense as it is an empirical truth.

Thwarted by the cosmos again!

All I am asking for is a debugger in Xcode that works as well as Macintosh Programmer's Workshop ( MPW) circa 80's/90's. Maybe I am being unreasonable?

I stepped a line in the debugger and all the variables disappear... and all I get is the spinny "fuck you" indicator and the variables all disappear.

But here is the worst part... Apple isn't holding any of those fucktards on the Xcode team accountable for producing a shit product.

I'm really glad I don't have to do this as a full time job anymore. Then why do I continue to pound nails with my forehead (use Xcode)?

Whip me, beat me, make me use Xcode...

Fuck XCode! -
Yesterday I had the stupid idea to rename an icon file. Checked that XCode was building the application still fine. Ran it over the build server: Failed, complaining about the old missing icon file! Checked again and again, but there was no friggin' reference to the old file in the whole repo.
Log in to the machine clear the build folder and try to build the component again. Bang still same error and the references to no longer existing files reappear.
Turns out XCode was caching those references somewhere in the home directory as "DerivedData" and after deleting those, I could build again... but why on earth are you building a cache if you cannot properly invalidate it? Just to waste our time?
(@xcodesucks)

In the “Qualities of Great Design” session at #WWDC2018. Really wish the Xcode team could be sitting in the front row so they couldn’t sleep thru the session...

oh i guess being the optimist I was thinking they would even be here. Silly me.

All the bugs that drive me effen crazy are clear and present in Xcode 10 beta. Stupid shit still rules at Xcode Central.

Updated to iOS 12.1.2 (sleazy release 2) after previously getting fucked up the ass by iOS 12.1.2 first release. Yes boys and girls, they tried to cover up their latest fuckup by re-releasing the same release with a modification.

The first time I updated, it knocks my Apple ID out on all my Apple devices when I upgrade my iPhone to 12.1.2. Mother fuckers... gotta log back in for every device, iPads, iPhones, Apple TVs, Macs. And for each service iTunes Store, Messages, FaceTime on each device supporting. Oh yea, it knocks out my Wi-Fi calling and I have to reestablish that too. Then to really ice me, it knocks out my HomeKit system as the Apple ID is knocked out on the Apple TV.

Now after updating just my iPhone to the second 12.1.2 "sleaze release", the thing knocks all my devices out again.

Apple has taken away that which I loved; impeccable engineering and design that could be used as the model for an entire industry. The industry guru. (teacher, leader) Apple has become the new Microsoft.

October 5, 2011, the day Apple died.

Xcode: took away the ability to manage multiple windows as documents; everything is a half-assed safari browser window that neither works like Mail nor like Safari.

Xcode: took away the ability to have variables in the debugger in separate displays, now it is a single basket of eye-bleeding variable/data spew.

Xcode: took away the ability to modify variable values in the debugger, it's just broken and lets you think you can but reverts the value.

Xcode: took away the debugger's ability to modify the execution pointer. You can't move the current line of execution to the previous line, the line past the current line, nothing.

The same internal human virus that manages the Alzheimers 'upgrades' of macOS Server seems to be managing the Xcode debugger, more aptly named now "Xcode stepper" cuz it makes a lot of motion but goes nowhere fast.

I wonder if everyone on DevRant grouped together and posted bug reports on Xcode, would it generate any positive response at Apple?

Related to queueing theory...

Suburban traffic at a stop lights has developed a tendency to include invisible cars.

You can see where these invisible cars are by the gap between the front bumper of one car the back bumper of the next. Sometimes there is an invisible motorcycle, sometimes there is an invisible semi-tractor trailer. It is becoming an epidemic.

The dumbasses in traffic who do this are usually texting behind the wheel while stopped and they are not always Buffy the ding dong cheerleader nor Sally the Soccer Mom... Suits too... It seems to have gotten worse with pot becoming legal I just realized...

But to the point, you can tell these people would never be able to comprehend software engineering... they have no idea that for every invisible car in front of every dumbass driver like them, there is a real car way back that has to sit through two lights. (side effects of bugs and inefficient hash tables) Worse, these dumbasses do this in the left lane so it keeps a host of others from being able to get past their big fat ass into the turn lane.

Simple queueing theory escapes these people.

Computers will someday take their jobs.

Sometimes it motivates me to code faster... "There goes your job beotch! Get used to mac and cheese..."

But once in a while I am in a position to be able to be stopped at a light, and note that next to me is one of those "gapsters" and then pull my car (or motorcycle some days) into that invisible car's spot. The gapster gets so mad sometimes... >:-> so much satisfaction I almost feel guilty...

Queueing theory rules... LOL

Have you ever tried to get something working in node.js... and the version and uninstall and reinstall... hours and hours of dicking around with this god damn raspberry pi zero only to find that node jack shit does not support the "older" ARM 6 processor on the newest raspberry pi zero Wi-Fi units. And omg the amateurs out there with the copy-paste half-assed "help" clogging out the real info. God damn hobby ware.

If you want to experience the definition of hell, do iOS Development and use their only allowed IDE called "Xcode". It was made by Satan himself. You're welcome.

What baffles me is how despite being on version 3 of Swift, Apple still havent updated Xcodes refactoring tools to support it. All I want to do is rename a variable or function but oh no. "Xcode can only refactor C or Objective-C code". Yet they are plowing on with new features in other areas like the interface builder but completely ignoring the tools that make IDEs useful.

During my small tenure as the lead mobile developer for a logistics company I had to manage my stacks between native Android applications in Java and native apps in IOS.

Back then, swift was barely coming into version 3 and as such the transition was not trustworthy enough for me to discard Obj C. So I went with Obj C and kept my knowledge of Swift in the back. It was not difficult since I had always liked Obj C for some reason. The language was what made me click with pointers and understand them well enough to feel more comfortable with C as it was a strict superset from said language. It was enjoyable really and making apps for IOS made me appreciate the ecosystem that much better and realize the level of dedication that the engineering team at Apple used for their compilation protocols. It was my first exposure to ARC(Automatic Reference Counting) as a "form" of garbage collection per se. The tooling in particular was nice, normally with xcode you have a 50/50 chance of it being great or shit. For me it was a mixture of both really, but the number of crashes or unexpected behavior was FAR lesser than what I had in Android back when we still used eclipse and even when we started to use Android Studio.

Developing IOS apps was also what made me see why IOS apps have that distinctive shine and why their phones required less memory(RAM). It was a pleasant experience.

The whole ordeal also left me with a bad taste for Android development. Don't get me wrong, I love my Android phones. But I firmly believe that unless you pay top dollar for an android manufacturer such as Samsung, motorla or lg then you will have lag galore. And man.....everyone that would try to prove me wrong always had to make excuses later on(no, your $200_$300 dllr android device just didn't cut it my dude)

It really sucks sometimes for Android development. I want to know what Google got so wrong that they made the decisions they made in order to make people design other tools such as React Native, Cordova, Ionic, phonegapp, titanium, xamarin(which is shit imo) codename one and many others. With IOS i never considered going for something different than Native since the API just seemed so well designed and far superior to me from an architectural point of view.

Fast forward to 2018(almost 2019) adn Google had talks about flutter for a while and how they make it seem that they are fixing how they want people to design apps.

You see. I firmly believe that tech stacks work in 2 ways:

1 people love a stack so much they start to develop cool ADDITIONS to it(see the awesomeios repo) to expand on the standard libraries

2 people start to FIX a stack because the implementation is broken, lacking in functionality, hard to use by itself: see okhttp, legit all the Square libs, butterknife etc etc etc and etc

From this I can conclude 2 things: people love developing for IOS because the ecosystem is nice and dev friendly, and people like to develop for Android in spite of how Google manages their API. Seriously Android is a great OS and having apps that work awesomely in spite of how hard it is to create applications for said platform just shows a level of love and dedication that is unmatched.

This is why I find it hard, and even mean to call out on one product over the other. Despite the morals behind the 2 leading companies inferred from my post, the develpers are what makes the situation better or worse.

So just fuck it and develop and use for what you want.

Honorific mention to PHP and the php developer community which is a mixture of fixing and adding in spite of the ammount of hatred that such coolness gets from a lot of peeps :P

Oh and I got a couple of mobile contracts in the way, this is why I made this post.

And I still hate developing for Android even though I love Java.

What is one of the most important things you can do related to your healthcare? Track your meds.

What **can’t** HealthKit do? Give you the ability to track your meds.

🥃💃🏼🦊 Over!

Why xcode and ApplicationLoader sucks?
Everytime I've to upload IPA to testflight/store, xcode and AL would fail 100 times before successfully uploading one.

Why the hell do they call it a "pull request". That is so bas-ackwards. Can you say ESOL?

Woohoo! Devrant on HN! Kinda reminds how when you google "xcode sucks" the top result is a devrant post.

Heh, I was just thinking how I never really used devrant in past while. It's almost like a sign.

Fuck Swift. Such a garbage language. The last 3 days I tried multiple web server implemented in Swift for mocking API's and none of them worked. Old, not maintained, wrong documentation, wrong code examples and just low quality shit.
Finally I decided to not give a crap and move to use Wiremock and it works out of the box, start and configuration is a breeze and it just plainly works. I should have done that from the beginning.

Btw., as a warning these were the frameworks I used and you should avoid them if possible: Swifter, Embassy, Ambassador and Succulent.

I find an average of 2 different iOS/XCode bug every day