apple broke a lot of its developer reference links... again

-
Was just reading a link on the apple developer reference, and sent a link to someone to read...

Then I noticed that the link no longer worked... and instead was redirected by the apple website to the generic front page of their developer reference.

I wish someone would point them to Cool urls don't change, and help them understand the web.

This isn't the first time they've broken their reference urls... the web is full of old, bad links to their documentation.

They've updated their online documentation... however they haven't kept the old urls around.

stab. un-cool.

Comments

Unknown said…
Wow, condescend much? Yeah it sucks, but sometimes in the real world you have a million things to get done and your boss de-priorizes broken URLs and that's that.

I wish people would learn the difference between "its" and "it's," especially when they're acting superior. Maybe someday we'll get our wishes.
2:17 AM
Pete Warden said…
"Sometimes in the real world you have a million things to get done and your boss de-prioritizes broken URLs and that's that"

The point is, it's a really really bad trade-off for developer documentation. Apple spends millions of dollars and man years of effort producing it as an investment in their platform. After all that effort, they then lose a lot of eyeballs by breaking URLs, something which could be avoided by putting in a comparatively small amount of effort.
2:27 AM
Unknown said…
It's not about priorities, it's about designing the system so that these things won't happen. They've screwed up.
6:48 AM
Unknown said…
Wow, you think Apple screw up their websites, try IBM. I have a software subscription service with them, and it took 3 months of complaining before I was ever able to get their website to let me download my software. Two years later, and their web app is so screwed-up, it won't let me find or download the things for which I've paid.
11:53 AM
Post a Comment

Popular posts from this blog

Draft 3 of, ^Let's write a unit test!^

-
Image
So, I started writing this for people who want to 'contribute' to Community projects, and also Free Libre or Open source projects. Maybe you'd like to get involved, but are unsure of where to begin? Follow along with this tutorial, and peek at the end in the "what is a git for?" section for explanations of what some of the words mean. Draft 1, 2018/07/18 - initial draft. Draft 2, 2019/11/04 - two full unit test examples, assertions, making a pull request, use python 3 unittest substring search, "good first issue" is a thing now. Started "What is a git for? Jargon" section. Draft 3, 2020/12/12 - default branch name is main. What's first? A test is first. A unit test is a piece of code which tests one thing works well in isolation from other parts of software. In this guide, I'm going to explain how to write one using the standard python unittest module, for the pygame game library. You can apply this advice to most python pr...
Read more

Is PostgreSQL good enough?

-
Image
tldr; you can do jobs, queues, real time change feeds, time series, object store, document store, full text search with PostgreSQL. How to, pros/cons, rough performance and complexity levels are all discussed. Many sources and relevant documentation is linked to. Your database is first. But can PostgreSQL be second? Web/app projects these days often have many distributed parts. It's not uncommon for groups to use the right tool for the job. The right tools are often something like the choice below. Redis for queuing, and caching. Elastic Search for searching, and log stash. Influxdb or RRD for timeseries. S3 for an object store. PostgreSQL for relational data with constraints, and validation via schemas. Celery for job queues. Kafka for a buffer of queues or stream processing. Exception logging with PostgreSQL (perhaps using Sentry) KDB for low latency analytics on your column oriented data. Mongo/ZODB for storing documents JSON (or mangodb for /dev/null replacemen...
Read more

post modern C tooling - draft 6

-
Image
Contemporary C tooling for making higher quality C, faster or more safely. DRAFT 0 - 10/11/18,  DRAFT 1 - 9/16/19, 7:19 PM, I'm still working on this, but it's already useful and I'd like some feedback - so I decided to share it early. DRAFT 2 - 10/1/19, mostly additions to static analysis tools. DRAFT 3 - 10/4/19, updates on build systems, package management, and complexity analysis.  DRAFT 4 - 10/6/19, run time dynamic verification and instrumentation, sanitizers (asan/ubsan/etc), performance tools, static analyzers. DRAFT 5 - C interpreter(s).  DRAFT 6 - 11/6/19 , mention TermDebug vim,  more windows debugging tools, C drawing for intro. In 2001 or so people started using the phrase "Modern C++". So now that it's 2019, I guess we're in the post modern era? Anyway, this isn't a post about C++ code, but some of this information applies there too. No logo, but it's used everywhere. Welcome to the post modern era. S...
Read more