Learn More
Resend Email
28
b2plane
362d

I love how i finish a project, dont touch ANYTHING for months, then a few months later i try to run it and NOTHING WORKS. I cant start. I cant compile. Now i have to update versions. Now developer mode has to be turned on and restarted phone. Now i have to configure something specific in xcode. Now i have to update xcode. Now it crashes. Now i have to modify something. AND IT NEVWR FUCKING ENDS. I DIDNT TOUCH SHIT SINCE THE LAST TIME I OPENED THIS PROJECT AND IT WORKED PERFECTLY FINE. I DIDNT EVEN CHANGE MY PHONE OR PC. I DIDNT EVEN DELETE THE REPOSITORY FROM MY PC. AND BY MAGIC EVERYTHING GOT FUCKED A FEW MONTHS LATER FOR NO REASON. NO. I WILL FUCK YOU. U WONT FUCK ME. FUCK U

rant
Favorite
Ranter
Comments
  • 3
    362d
    How does this happen? This is really wild. I would shit if this happened in my dev environment.
  • 14
    362d
    Yes the classic XKCD "lets install freebsd"
  • 3
    362d
    @Demolishun apparently apple policies mixed with xcode updates produces a huge horseshit worth of headache problems and random compilation bugs
  • 0
    362d
    What are you talking about?

    First, you don’t have to update. It can happen that you need to have a newer version of xcode if it is more than 2 years old in order to publish to the app store, but compiling will work with any old version.

    Second, updating xcode will never break any project. You have probably updated your project target to the latest sdk and that can break dependencies which haven’t been updated yet.

    Please stop spreading this myths about xcode and development on the mac.
  • 0
    362d
    If you have a mac with Apple Silicon chip like M1, xcode versions prior to 14 should be launched with rosetta. If you have updated to the latest 14, you need to pick a simulator with rosetta. Xcode itself can no longer be used with rosetta. Note that the swiftui previews won’t work if you have selected a real device. You need simulator rosetta.

    Maybe that’s where your compilation errors come from.
  • 0
    362d
    Another cause of error can also be a target device (like an iphone) that has a newer version than what xcode supports. Then you obviously need to update xcode or use a simulator, but you get an appropriate error message for this case, so it should be clear.
  • 1
    362d
    The only reason I don't finish my personal projest is because I know that after THIS long of inactivity ´ng serve´ will spit and barf at me random errors I haven't ever seen before.
  • 0
    362d
    @netikras this is a flutter app
  • 2
    362d
    @Lensflare but you have to agree, that it is pretty stupid, to need to update the friggin OS only to then update XCode, no? That's what i always hated, when rarely working with apple. You literally just sit there and waste time.

    i shit you not, the last time i did that on some macbook air it took me fucking hours. It took literally more time, then i was working that day.
  • 1
    362d
    @thebiochemic I agree that’s annoying.
    The reason is that Xcode contains everything that you need for development for any of Apple’s platforms, including macOS. So, if your macOS version is too low, Xcode wouldn’t be able to run your project on it.

    Of course, from a pure iOS development perspective, it doesn’t make sense.

    The real problem is that Xcode is not divisible into smaller parts or modules.

    The advantage is that you just download one single app and you are ready to go with everything.
  • 2
    361d
    It's not myth. I am mainly doing flutter nowadays and Mac does bully me like that. I don't even change dependencies or libraries, I only write some UI stuffs on dart files, but it happens: what compile just fine yesterday, no longer compile today!

    We have delete this and that, clean the project files, pub get the dependencies again. It's ridiculous and stupid. It doesn't happen when I target android, web and windows platform. This only happen when I try to compile for iOS and Mac.

    Fuck Apple development!
  • 0
    361d
    @daniel-wu well it’s a flutter problem then. They just fucked up their iOS stack.

    I’m developing on the mac since 2008 and never had that kind of problems. I’ve never tried flutter though.
  • 0
    361d
    @Lensflare that's might be the case. Targetting mac/ios app by flutter has very weird requirement where we have to install Ruby and a dependency manager named Cocoapod. It's not needed when you target other platforms however. I suspect they are unable to compile dart to apple's native codes directly, and they ended up using ruby as intermediary.
  • 0
    361d
    @daniel-wu no, Ruby is the language of cocoa pods config files. Cocoa pods is a 3rd party dependency manager that is also often used by native iOS projects. It’s very popular.

    It’s often the cause of problems but fortunately it is slowly being replaced by Apple’s SPM (swift package manager), which is superior.
  • 1
    358d
    @Lensflare I see. Since I don't do native mac development, I don't know that cocoapods is also required. If the problem doesn't occur there, then it's really Flutter maker who fucked up somewhere. And here I though they are all really smart people. I really enjoyed it for android development. It's consistent, stable, are rarely break compatibility. Unlike native android development, which best practice changes every several months!
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment