Ah, well, nothing is foolproof. Yes, if you don't update your dependency list when dependencies are removed, they might get stale. But I keep up on that stuff and haven't ran into that problem yet. Even if I did, I'd rather have that problem than an app where all the dependencies are global.
Interesting. Why would the requires go stale? And how would you use a dependency you don't require? It wouldn't be possible to use it unless you required it. This of course assumes you're testing your classes in isolation.
I think a lot of this unfortunately comes from Rails. Rails hides a lot of complexity which creates "magic". And since most Rubyists come to Ruby from Rails, a lot of Rubyists have the bad habit of hiding complexity wherever possible. I was guilty of that myself. But I've noticed it slowly starting to change.
Oh, interesting. Did they give a reason? Was it legal? MacRumors has been doing this for some time, I can't imagine that there's anything illegal about it.
Actually, the entire reason I made this site was because I thought the way MacRumors visualized the data wasn't very good. If they had done a better job, I wouldn't have needed to make this.
As for credit... what should I be crediting them for? I'm just collecting a list of dates and then visualizing the data.
I guess it depends on how you quantify usefulness. There's less info, but I think I visualized the information that I do show much better than MacRumors.
They probably meant whether or not I "took" the information from somewhere else. But yeah, actually scraping the information would have been ridiculous. It's all just in a static YAML file.
I built my own because their design, and I mean literally the way they visualize the data, isn't very good. Or rather, it's not as good as it could be. They even updated the design a year or two ago and all they did was give it a coat of paint, rather than rethinking how to best visualize the data.