Live data from Hacker News

Google Will Eat Itself

googlewilleatitself.com

131–139 of 139 posts

Re: Google Will Eat Itself

#131
post #115
post #94

Earlier quoted context omitted.

> Which means that EVENTUALLY, these companies will either pay dividends or their stocks are worthless. Yes, And that is false. IT IS FALSE. There are companies that never pay dividends, but because of continuous growth, are regarded as attractive investments (Berkshire Hathaway is just one of many examples). To avoid any possible confusion, I posted a list of such companies. And I have just added another list below.…

Haha, let's you and I and everybody else start trading rocks. Whether or not the rocks have value don't matter, as long as the price of rocks continue to go up. Will you keep buying the rocks because of this upward growth? > Yes, which means you downvoted based on the fact that you disagreed with the views I expressed, not based on whether I contributed to the conversation, a violation of HN's voting guidelines. That…

Are you kidding? If I can buy the rocks at $4 per rock and I'm pretty sure I'll be able to sell them to somebody later at $6 per rock, absolutely I'll keep buying the rocks.

Re: Google Will Eat Itself

#132

Earlier quoted context omitted.

wait wait wait, a billion means two different things in Europe and America? I'm from Europe and I always used 1 billion to say 10^9. I hardly see how I would not have noticed figures being so different in say, news articles from America and Britain.

When I was growing up in Ireland, a billion was a million million in Britain and Ireland. Now, we have adopted the American thousand million. In Germany and Italy, a thousand million is a Milliard, and a billion is a trillion.

Slovak and Czech have it same as Germany/Italy.

Re: Google Will Eat Itself

#137

Earlier quoted context omitted.

Impossible to easily solve programatically. E.g. 400,123: what is it? You cannot know unambiguously. And using OS language settings won't help either. Im from Europe but would not want to require using "," for the decimal separator enforced by OS settings, or anything related to programming or communicating with people on the Internet would become difficult. I'd much rather have just everyone use the same convention…

Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently throughout applications. That would be a easy programmatic way to solve the problem, that wouldn't require the whole world to adopt a single standard. But of course it'll never happen, as it would require that all programmers know their shit and follow good pra…

>Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently throughout applications.

So if I open a file in Notepad and type 400,123 (using the comma on my keyboard), what character encoding should that be done with?

Re: Google Will Eat Itself

#138

Earlier quoted context omitted.

Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently throughout applications. That would be a easy programmatic way to solve the problem, that wouldn't require the whole world to adopt a single standard. But of course it'll never happen, as it would require that all programmers know their shit and follow good pra…

>Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently throughout applications. So if I open a file in Notepad and type 400,123 (using the comma on my keyboard), what character encoding should that be done with?

The one that Notepad has configured by default in your OS version, unless you choose a different encoding when saving the file.

Re: Google Will Eat Itself

#139

Earlier quoted context omitted.

Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently throughout applications. That would be a easy programmatic way to solve the problem, that wouldn't require the whole world to adopt a single standard. But of course it'll never happen, as it would require that all programmers know their shit and follow good pra…

It would require to adopt a single standard, that is, how to encode that in the character encoding and the files. And it would still not stop someone from in the same browser for example using sometimes one notation, sometimes the other notation, depending on e.g. if they're filling in a form for a European bank, or something related to programming.

You mean, exactly like you do with character encodings for different alphabets?
Post reply on HN