4 ms·

Can we give this HN post a better title? This is atrociously clickbaiting. Granted it just goes to GitHub, but I would like to have at least an _inkling_ of wha

Can we give this HN post a better title? This is atrociously clickbaiting. Granted it just goes to GitHub, but I would like to have at least an _inkling_ of what I'm about to read.

tedmiston 10y ago
Dear Apple - Xcode feature requests and bug reports (@dang)
- numbsafari 10y ago
  Yet, oddly, not a single reference to a radar report that people can try to support. Is this a manifesto, or an attempt to get a bunch of Apple developers to put their email addresses on a list as part of someone's marketing campaign for iOS-focused dev tools?
ryanSrich 10y ago
Especially given the length as well. It's a small, short list of issues that users of XCode/Apple Developer tools have. Why is this #1 on the front page?
- deleted 10y ago
  [deleted]
- infinisil 10y ago
  Because it's by far one of the most annoying issues every developer has with Apple now. It's so frustrating to see the syntax highlighting and auto completion engine crash continuously as you try to figure out what line causes it just so you can rewrite it the more verbose way for the engine not to choke. You may think this has to be a beta version or a newly introduced bug, but no, these issues have been there in the official release for at least 1 1/2 years now. It got better over time, yes, but it's still far from being where it should be.
  - majewsky 10y ago
    > it's by far one of the most annoying issues every developer has with Apple now Every developer on an Apple device who actually makes apps for Apple devices. There are a lot of devs on Macbooks who produce server applications that run on Linux, possibly more than create iOS or macOS apps.
    - infinisil 10y ago
      Whoops, yeah that's what I meant to say
  - 36bydesign 10y ago
    1 1/2 years? Uh since day 1 of swift at least. Granted it was beta then but you couldn't go 45 seconds without losing syntax highlighting.
richdougherty 10y ago
I wish Hacker News would display both the original title and an editorialised subtitle. The first is important to capture the linked author's intent but the second is necessary for actually knowing what the link is about. You can see how it works on the Economist where there are two "titles" for each article, a catchy one and a useful one. e.g. From http://www.economist.com/printedition/2017-02-18 http://www.economist.com/printedition/2017-02-18: Catchy / Useful - Taking the low road / Scotland's economy - Back to the desert / Britain in the Gulf - Still cleaning up the Co-op / Ethical banking - Errant Flynn / Turmoil in the administration - etc
- pmoriarty 10y ago
  I've always found HN's policy of no editorializing of titles, and their insistence on original titles to be counterproductive. Quite often an excellent article will have a really generic or vague title that few people will ever read, and a judiciously edited title will interest people enough to read it. At that point, upvotes should determine whether the article lives or dies, as usual. If readers don't think the article is worthwhile, they don't have to upvote it. I like your subtitle idea too. It's definitely better than insisting on keeping just the original title. Unfortunately, it will make for some practical difficulties with the layout of HN pages, which will be able to fit fewer articles in the same space, and it will also be problematic with RSS feeds and the like, which will often still display just one title, not a title and subtitle.
  - ethbro 10y ago
    HN needs a secondary upvoter system on the displayed title for an article. "Dear Apple" or "Requests regarding XCode and Swift/ObjC" or "Developer tooling in the Apple ecosystem" Uneditorialized titles also encourages marketing via title wording. But in general, isn't this the Facebook "link as it is" vs "how would be objectively and fairly make links better" debate?

Can we give this HN post a better title? This is atrociously clickbaiting. Granted it just goes to GitHub, but I would like to have at least an _inkling_ of what I'm about to read.

tedmiston 10y ago

Dear Apple - Xcode feature requests and bug reports (@dang)

numbsafari 10y ago
Yet, oddly, not a single reference to a radar report that people can try to support. Is this a manifesto, or an attempt to get a bunch of Apple developers to put their email addresses on a list as part of someone's marketing campaign for iOS-focused dev tools?

ryanSrich 10y ago

Especially given the length as well. It's a small, short list of issues that users of XCode/Apple Developer tools have. Why is this #1 on the front page?

deleted 10y ago
[deleted]
infinisil 10y ago
Because it's by far one of the most annoying issues every developer has with Apple now. It's so frustrating to see the syntax highlighting and auto completion engine crash continuously as you try to figure out what line causes it just so you can rewrite it the more verbose way for the engine not to choke. You may think this has to be a beta version or a newly introduced bug, but no, these issues have been there in the official release for at least 1 1/2 years now. It got better over time, yes, but it's still far from being where it should be.
- majewsky 10y ago
  > it's by far one of the most annoying issues every developer has with Apple now Every developer on an Apple device who actually makes apps for Apple devices. There are a lot of devs on Macbooks who produce server applications that run on Linux, possibly more than create iOS or macOS apps.
  - infinisil 10y ago
    Whoops, yeah that's what I meant to say
- 36bydesign 10y ago
  1 1/2 years? Uh since day 1 of swift at least. Granted it was beta then but you couldn't go 45 seconds without losing syntax highlighting.

richdougherty 10y ago

I wish Hacker News would display both the original title and an editorialised subtitle. The first is important to capture the linked author's intent but the second is necessary for actually knowing what the link is about. You can see how it works on the Economist where there are two "titles" for each article, a catchy one and a useful one. e.g. From http://www.economist.com/printedition/2017-02-18 http://www.economist.com/printedition/2017-02-18: Catchy / Useful - Taking the low road / Scotland's economy - Back to the desert / Britain in the Gulf - Still cleaning up the Co-op / Ethical banking - Errant Flynn / Turmoil in the administration - etc

pmoriarty 10y ago
I've always found HN's policy of no editorializing of titles, and their insistence on original titles to be counterproductive. Quite often an excellent article will have a really generic or vague title that few people will ever read, and a judiciously edited title will interest people enough to read it. At that point, upvotes should determine whether the article lives or dies, as usual. If readers don't think the article is worthwhile, they don't have to upvote it. I like your subtitle idea too. It's definitely better than insisting on keeping just the original title. Unfortunately, it will make for some practical difficulties with the layout of HN pages, which will be able to fit fewer articles in the same space, and it will also be problematic with RSS feeds and the like, which will often still display just one title, not a title and subtitle.
- ethbro 10y ago
  HN needs a secondary upvoter system on the displayed title for an article. "Dear Apple" or "Requests regarding XCode and Swift/ObjC" or "Developer tooling in the Apple ecosystem" Uneditorialized titles also encourages marketing via title wording. But in general, isn't this the Facebook "link as it is" vs "how would be objectively and fairly make links better" debate?