5 ms·

An alert is hardly the place to list detailed code warnings. I think the prompts are enough to have one open their app in Xcode and review the specific deprecia

by isodev 3y ago

An alert is hardly the place to list detailed code warnings. I think the prompts are enough to have one open their app in Xcode and review the specific depreciation warnings.

saagarjha 3y ago
They’re not. Pretty much every developer I’ve talked to has no idea what this warning means or what they should be doing in response to this. All of them are smart people who are longtime Mac developers. There are a bunch of ways to improve this: you could tell people to look in Console for logs, or name the deprecated API being used. What Apple did instead is they decided to shame apps by name but not tell them what they did wrong, and do so in a way that is quite broken because the warnings don’t even line up with deprecated API usage.
- Cycl0p 3y ago
  [flagged]
  - deleted 3y ago
    [deleted]
  - lapcat 3y ago
    [flagged]
    - Cycl0p 3y ago
      Don’t have to get so personal, I do not know saagarjha nor do I know of his various achievements writing software, and as a matter of fact, you do not know me either. I speak purely off experience, writing/porting software for macOS for more than 4 years, most of the time using Xcode.
      - lapcat 3y ago
        > Don’t have to get so personal "Nonsense" was a very dismissive reply. What saagarjha said is not only sensical, it's true. And you were presuming to explain Xcode to people who know Xcode intimately. > I speak purely off experience, writing/porting software for macOS for more than 4 years, most of the time using Xcode. And I've been a professional Mac developer for 17 years. It appears that you created your HN account less than an hour ago, for the purpose of talking down to someone who actually knows more than you do. I find this very sad.
      - coldtea 3y ago
        >I do not know saagarjha nor do I know of his various achievements writing software Nor should we care in this context. He either has a valid argument to respond to the parent's claim, or not. The parent made a claim. The other guy can respond something like "You're wrong, this information is not shown in XCode". Or he could let the comment slip, and stick to what he said above. Somebody else pointing out how he is an authority is not an argument.
    - joiqj 3y ago
      That is nothing but an appeal to authority.
      - lapcat 3y ago
        [flagged]
        arcticbull 3y ago
        So am I but it's still an appeal to authority, and not a valid argument.
        flangola7 3y ago
        No one is required to debate you. You think it's an appeal to authority... so what?
        dang 3y ago
        Could you please stop posting unsubstantive comments and flamebait? You've unfortunately been doing it a lot lately. It's not what this site is for, and destroys what it is for, so we eventually have to ban such accounts. If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
        lapcat 3y ago
        It wasn't intended to be an argument. It's simply a fact.
        coldtea 3y ago
        Authorities can also miss the obvious like the rest of us. So still needs a proper argument (even if it's just "No, it's not shown in XCode, go check and you'll agree").
        lapcat 3y ago
  - samtheprogram 3y ago
    If the deprecated API is used by a library you're using and not compiling within Xcode (for example, IIRC the Facebook SDK), you're SOL. Also, it appears not _all_ deprecated APIs are causing these alerts, making matters worse. If you are using several deprecated APIs but aren't sure which ones absolutely need fixing, it would be quite tedious -- especially because the error only appears once per app. And all of this is very easily improved with more diagnostics as the article suggests.
    - cmsj 3y ago
      You can also trivially suppress deprecation warnings with clang flags or pragmas, so even with Xcode there may not be a logged warning, because someone already decided "yes, I know this is deprecated, but there is no alternative, so we'll have cleaner build output thank you".
- joiqj 3y ago
  Looking at the Console is precisely what I thought of, at least coming from Windows, where I'd be looking at the Event Viewer to know more about such a message. Does the Console show more information?
  - saagarjha 3y ago
    Will have to check but I think I remember looking at the code to generate these and didn’t spot anything but the alert enabled by default.

by isodev 3y ago

An alert is hardly the place to list detailed code warnings. I think the prompts are enough to have one open their app in Xcode and review the specific depreciation warnings.

saagarjha 3y ago

They’re not. Pretty much every developer I’ve talked to has no idea what this warning means or what they should be doing in response to this. All of them are smart people who are longtime Mac developers. There are a bunch of ways to improve this: you could tell people to look in Console for logs, or name the deprecated API being used. What Apple did instead is they decided to shame apps by name but not tell them what they did wrong, and do so in a way that is quite broken because the warnings don’t even line up with deprecated API usage.

Cycl0p 3y ago
[flagged]
- deleted 3y ago
  [deleted]
- lapcat 3y ago
  [flagged]
  - Cycl0p 3y ago
    Don’t have to get so personal, I do not know saagarjha nor do I know of his various achievements writing software, and as a matter of fact, you do not know me either. I speak purely off experience, writing/porting software for macOS for more than 4 years, most of the time using Xcode.
    - lapcat 3y ago
      > Don’t have to get so personal "Nonsense" was a very dismissive reply. What saagarjha said is not only sensical, it's true. And you were presuming to explain Xcode to people who know Xcode intimately. > I speak purely off experience, writing/porting software for macOS for more than 4 years, most of the time using Xcode. And I've been a professional Mac developer for 17 years. It appears that you created your HN account less than an hour ago, for the purpose of talking down to someone who actually knows more than you do. I find this very sad.
    - coldtea 3y ago
      >I do not know saagarjha nor do I know of his various achievements writing software Nor should we care in this context. He either has a valid argument to respond to the parent's claim, or not. The parent made a claim. The other guy can respond something like "You're wrong, this information is not shown in XCode". Or he could let the comment slip, and stick to what he said above. Somebody else pointing out how he is an authority is not an argument.
  - joiqj 3y ago
    That is nothing but an appeal to authority.
    - lapcat 3y ago
      [flagged]
      - arcticbull 3y ago
        So am I but it's still an appeal to authority, and not a valid argument.
        flangola7 3y ago
        No one is required to debate you. You think it's an appeal to authority... so what?
        dang 3y ago
        Could you please stop posting unsubstantive comments and flamebait? You've unfortunately been doing it a lot lately. It's not what this site is for, and destroys what it is for, so we eventually have to ban such accounts. If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
        lapcat 3y ago
        It wasn't intended to be an argument. It's simply a fact.
      - coldtea 3y ago
        Authorities can also miss the obvious like the rest of us. So still needs a proper argument (even if it's just "No, it's not shown in XCode, go check and you'll agree").
        lapcat 3y ago
- samtheprogram 3y ago
  If the deprecated API is used by a library you're using and not compiling within Xcode (for example, IIRC the Facebook SDK), you're SOL. Also, it appears not _all_ deprecated APIs are causing these alerts, making matters worse. If you are using several deprecated APIs but aren't sure which ones absolutely need fixing, it would be quite tedious -- especially because the error only appears once per app. And all of this is very easily improved with more diagnostics as the article suggests.
  - cmsj 3y ago
    You can also trivially suppress deprecation warnings with clang flags or pragmas, so even with Xcode there may not be a logged warning, because someone already decided "yes, I know this is deprecated, but there is no alternative, so we'll have cleaner build output thank you".
joiqj 3y ago
Looking at the Console is precisely what I thought of, at least coming from Windows, where I'd be looking at the Event Viewer to know more about such a message. Does the Console show more information?
- saagarjha 3y ago
  Will have to check but I think I remember looking at the code to generate these and didn’t spot anything but the alert enabled by default.