6 ms·
I suspect Apple's culture of not really caring about backwards compatibility and otherwise technological churn is mostly responsible for this; e.g. if I wanted
by userbinator 8y ago
I suspect Apple's culture of not really caring about backwards compatibility and otherwise technological churn is mostly responsible for this; e.g. if I wanted to write Windows GUI app that'll run on everything from Win95 to Win10 and probably for the forseeable future, I'd choose Win32 because it's stable and well-documented. On Linux, a combination of POSIX and Xlib would probably have similar stability. But I'm not sure what the equivalent would be for the Mac...
That said, I've noticed MS's documentation quality also take a nosedive in recent years, notably around the time it moved away from MSDN (and introduced a huge amount of formatting errors.) A lot of useful "KB" articles and downloads also mysteriously disappeared. Fortunately I still use "WIN32.HLP" which basically covers the core part of Win32.
- jarjoura 8y agoI love how they go to great lengths to describe and recommend that for Win8 and above you should use Pointer API instead of the "legacy" mouse and touch events, because it'll also handle Pen too. Yet when you actually go to click on WM_POINTER*, they are, just like Apple, in an archived section. Tapping on the "see latest doc" just takes you to the home screen. Yet, WM_LBUTTONDOWN takes you to the latest updated version. Talk about a confusing mess.
- dend 8y agodocs.microsoft.com PM here. Thanks for the feedback - I am routing this to the content team so that we can see what we can do to improve this situation.
- ghego1 8y agoThis comment alone, and the lack of any comment by any Apple rep so far down the comments, makes me think that I did the right thing ditching macOS as my main web development workstation in favor of Windows.
- saagarjha 8y agoWhat makes you think that you should expect that someone working at Apple, who can fix your issue, will materialize in the comment section of Hacker News and solve your problems (and then reply to you saying that they will do so)? It's nice when relevant people step in and help, but there's a proper channel for this feedback (even if you don't think it's going to be heard).
- sundvor 8y ago"Proper channel"... :) That vastly more critical Facetime/facepalm issue certainly went straight to /dev/null , so ... thanks for the laugh, I guess.
- Klonoar 8y agoThis isn't a great answer, because there _is_ some literature to point to concerning how feedback (bugs and otherwise, regarding engineering) is handled at Apple: https://www.corbinstreehouse.com/blog/2019/03/the-sad-state-of-logging-bugs-for-apple/?cat_id=86&order=DESC https://www.corbinstreehouse.com/blog/2019/03/the-sad-state-... The game that Apple's dev evangelism needs to play is the same one that MSFT/Google/etc play. Apple gets a free pass because they've had a largely devoted (almost cult-ish) fanbase of software developers (of which I count myself). They're starting to piss them off, though, and that has cascading effects. Lobbing things over the wall doesn't work anymore.
- saagarjha 8y agoIf you read the article (I'm generally aware of the issues mentioned, FWIW), there isn't really much it tells you to do other than file bugs.
- Klonoar 8y agoI did read the article, considering I linked it in the first place. The snark isn't necessary. The ending of that article is a very resigned "this is all you can do. This is why it's this way, though.". The article is absolutely a criticism of how the bug process works. The entire point of all of this is that Apple needs to play the game better. You have a weird habit of popping up in every single thread to defend them, and I've noted your past associations with them in other threads, so I'll probably not bother responding to this further.
- Crinus 8y agoWell, since you are here... can we have something like the old MSDN CD CHM files and/or WIN32.HLP files (ie. a simple offline version of the documentation that includes everything)? Almost every other mention of Win32 documentation here and on Reddit has someone mention that they use some archived version of WIN32.HLP (or less often, CHM) instead of the sites because it is simpler and faster. But this documentation only covers the circa late 90s APIs and doesn't have any newer stuff and to view .HLP files on Windows 10 requires some hacking around (honestly it is absurd to break the help for several thousands applications and make several ebooks unreadable, but i guess it isn't something you can do anything about even if you wanted). Considering everything is static (and really, some of the documentation entries read the same as they do in WIN32.HLP from the mid-90s) it should be possible to make a CHM (or several of them) with the content available for download (but please not yet another custom help viewer, CHM is fine). TBH i do not have many hopes for this (i think this is something people ask for more than a decade), but it costs nothing to ask, so there you go :-P
- userbinator 8y agoThe latest you can download offline might be this: http://www.microsoft.com/en-us/download/details.aspx?id=20955 http://www.microsoft.com/en-us/download/details.aspx?id=2095... (Best to get a copy while you still can...)
- Crinus 8y agoThanks, i didn't knew about that :-).
- matwood 8y agoI don't know what the current MS doc situation is, but years ago when I left Windows dev to move to iOS I really missed the MS docs. The big reason was that they had tons of examples. I used the XPath MS docs for many years because they had so many clear examples.
- peteri 8y agoWhile you're here the rename of the URLs has caused me pain. For example (here on Task.Unwrap) https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.taskextensions.unwrap?view=netframework-4.8 https://docs.microsoft.com/en-us/dotnet/api/system.threading... The code sample has broken links, the correct pfxteam blog is: https://devblogs.microsoft.com/pfxteam/whats-new-in-beta-2-for-the-task-parallel-library-part-33/ https://devblogs.microsoft.com/pfxteam/whats-new-in-beta-2-f... It would be great if 404 page could show the posts for that day for the 4-Nov-2009 time period
- jonhendry18 8y agoI feel like maybe hyperlinks in developer docs were a bad idea. Writing technical documentation as if it would be published in thousand page tomes (because it would also be published that way) may have encouraged better writing and organization.
- jldugger 8y ago> I suspect Apple's culture of not really caring about backwards compatibility Not only that, but there's a famous article in Apple University about how no documentation is a good thing and a key part of Apple culture.