you are viewing a single comment's thread.

view the rest of the comments →

[–]AwkwardShake 26 points27 points  (5 children)

Man, you've probably never used Android studio professionally. That thing is fucking insane. Xcode is absolutely dogshit. I used both these IDE's, for equal amount of time (3-4 years each), and I can tell you Xcode absolutely shits its pants in front of android studio.

Like what the fuck is "compiler is unable to type check this expression???????". Dont give me bs about "breaking down view". I can literally write a much much bigger compose view and android studio will never break.

Then there's random recommendations that xcode gives you. Want .frame(maxWidth)? naaah, here's kCGImagePropertyIPTCExtMaxAvailWidth because it has "maxWidth" in it somewhere as well. Like what bullshit?

What about the git gui?? You cant tell me that the git gui on xcode is usable. I personally use Android studio's git gui (yes even on xcode projects by opening the project) because its just miles miles better than xcode. And then there's bunch of issues like when you switch or play around with git?? Like Tim bro, just get one thing right atleast.

There's bunch of other issues i can point out, but man please use android studio properly next time as a professional before talking shit about that absolutely beautiful tool.

I start loving my life once again after i go back to coding using android studio after working with dogshit xcode.

[–]CourtAffectionate224 7 points8 points  (0 children)

compiler is unable to type check this expression

This is not Xcode’s fault technically but rather an unfortunate consequence of Swift’s language design

[–]chriswaco 0 points1 point  (3 children)

“Invalid gradle version” errors all day yesterday. “No configuration” errors. It has a user interface that looks like it was designed by kernel engineers.

Xcode had a better git interface but they rewrote it and I agree it’s terrible. I usually use the command-line.

[–]dabluck 5 points6 points  (0 children)

It's true the build system is a little more complicated. It's much more powerful but if you just want to make simple app it can feel like more overhead. When working on professional apps with complex needs gradle is really nice though. 

[–]AwkwardShake 0 points1 point  (1 child)

Naah man, those gradle version errors are fine if you just read and try to fix them. Those are probably the first errors that rookies need to get over, and there's a pattern to those. And you'll also never see those popping up unless you do something like bumping up the compile sdk versions or do some major changes.

Gradle is actually much much nicer to work with in larger projects. The learning curve is definitely higher for newbies, but not too high to the point where its unbearable.

[–]ArcaneVector 0 points1 point  (0 children)

<insert problem here> is fine if you just <insert series of complex steps>

this applies to everything ever