Hacker News new | past | comments | ask | show | jobs | submit | FalcorTheDog's comments login

How useful would that information be? Seems like a good way to "punish" surgeons that take more difficult cases.


I suspect you're overthinking it. I'm pretty sure he just took the "le" from Google (Reddit + Google = Redditle).


Def overthinking. Googit probably would have a quick shutdown notice.


A quick glance at: https://www.reddit.com/r/AteTheOnion may be enlightening/horrifying.


Laughing over these examples I had an epiphany: we need more of this, all the time.

If half the articles someone looked at were clear satire, people would have to think about what they are reading and who the source is. (Analogous to how we are being trained to recognize phishing)

For those that can’t figure out what satire is, A/B test content until we discover empirically how stupid something has to be before even they realize it is satire.


One major issue is that the "standard" favicon size has historically been 16x16 pixels... which, in the age of high density displays will render either comically small or comically blurry. There are other meta tags like Apple's "apple-touch-icon" which has some higher resolution options. But already you can see the logic here isn't trivial.


It still seems trivial to me. Parse all meta icon tags, prefer one that matches exact client resolution of current display (don't even have to download the icons - the sizes are defined as part of the meta tag), else use the largest-resolution one, else in desperate bid try site/favicon.ico, otherwise give up.

Really shouldn't be complicated enough to need a special service to handle "edge cases".

Another comment mentions web manifest - I guess try those first before meta tags, or whatever order the standard says to use. I mean, we're talking a web browser here, it's designed to do these kind of tasks.


I guess the problem is when you want to quickly provide a favicon with the search result (beit in the omnibar or actual search page), as you're typing and results are being displayed you cannot send off a request to the site, wait for HTML html to finish up downloading, send off a request to the manifest if its defined for multiple sites at once.

On a technical level of course its doable but in reality it's a complete waste of data and processing, not to mention it could take a long time to show up. I imagine they have these favicons all cached on their side so they can quickly send the right file down and/or do this processing if needed.

That being said maybe they should just not use a favicon if it's that big of a deal.


Oh, this is for putting an icon next to search results? Yeah, that changes the calculus considerably. I thought this was about showing the favicon in the browser for a site the user visits (per the issue title).

In that case, yeah, I don't think the icons are necessary to show at all...


Even if you wanted to implement this, the logic of the service could be directly embedded in the browser as an extension or similar. There’s no reason to depend on a network service for this functionality.


I feel like the only user benefit is to see the favicons of sites you are familiar with, so caching those locally after you visit sites is probably good enough.


This is literally the first tip he describes in the article.


Do you have a source for that? Whether he popularized them or not, that's not where the expression comes from.


It's not though. There are ~75 24-year windows you can use between 1913 and today. I suspect you will find similar results with almost all of those windows. Obviously past performance is not an indicator of the future, but 75 data points is a pretty decent amount of data.


Following up, I plugged in the data from here into Excel: http://www.multpl.com/s-p-500-historical-prices/table/by-yea...

Some observations:

  -there are 122 24-year windows in the dataset
  -not a single 24-year period had a negative return
  -the lowest average return for a 24-year window was 0.15% in the window from 1874-1897
  -there have been only two 24-year windows since 1876 with average annualized returns less than 2%
  -every window since 1912 has been at least 3%
  -every window since 1968 has been at least 7.1% (the author's assumption)
  -every window since 1971 has been at least 8%
Note that this doesn't take inflation into account, but also does not factor in the returns from reinvested dividends. Those effects would probably approximately cancel each other out, but hard to say.


Those 75 data points are not independent observations, because the windows overlap so much. Remember that using "year" as the granularity is arbitrary anyway; if we had daily, hourly or by-the-minute data going back to 1913, then we could have more "data points" but we would not have any better insight or statistical significance into the original question.

My point is that having 100 years of investment data is much more like having 4 data points than it is like having 75 or 75 *12 (if you cut the years into months). Even though you literally have 75 data points, they are pretty close to a copy-paste of each other; not statistically independent.


I know right? I can't believe poor people don't just ask for more money. Then they wouldn't have to be poor! It's so simple!


You can totally scroll the month view in OS X Calendar in Yosemite and center it on whatever week you want (might require a trackpad / magic mouse).


"they won’t be able to communicate again until the game is over."

Clearly, this would be a form of communication between the prisoners.



Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: