Re:The compiler flag that time forgot
by userbinator on Monday May 04, 2015 @08:48PM
(#9490272)
It's made worse by the fact that such information is getting increasingly difficult to find when someone actually does want to figure out the "why". Maybe it's just me, but I've found Google's search results to be much worse now than they used to be in terms of detail and specificity, for the same queries.
[ Parent
| on HN ]
Re:The compiler flag that time forgot
by lelandbatey on Monday May 04, 2015 @09:09PM
(#9490339)
I feel like this is a side effect of so many people writing random blog posts and other things in an attempt to help others, but in the large it makes it less clear because there's such a long tail of documents that are useful (for some things), that people like, but that cannot answer underlying questions or point to where underlying questions can be answered.
I've found the best solution is to try to find someone with whom you can have a discussion about what you don't understand and where you can find learning resources. Also, being able to find and read specifications can be very helpful.
Re:The compiler flag that time forgot
by userbinator on Tuesday May 05, 2015 @09:37AM
(#9492374)
The worst part is that lots of historical but valuable information is "falling through the gaps" as a result of being overwhelmed by the new and superficial.
If archive.org had a real search engine, I'd probably use it more than Google.