21–30 of 55 posts
Hardcoding the validation of the reply is an unfortunate obstacle to scaling this - the server would very quickly become CPU bound. They should really have made a TwitterSortValidationService which sends the answer out to the Twitter API, and then listens for a response confirming whether or not the original sort was correct.
Hardcoding the validation of the reply is an unfortunate obstacle to scaling this - the server would very quickly become CPU bound. They should really have made a TwitterSortValidationService which sends the answer out to the Twitter API, and then listens for a response confirming whether or not the original sort was correct.
Easy, just use TwitterSort to validate TwitterSort. People can't be wrong twice!
https://duckduckgo.com/?q=!twitter+Those+numbers+aren%27t+so... Still no uses of this in the wild.
https://twitter.com/harrisonpage/status/555180585384046592
I think you want this query:
Hi, I'm with Google Corporate Development and I'd love to talk about your algorithm.
What about the locale of the user producing a different sort order?
They do specify that it's for sorting numbers, as opposed to say, text. Do some locales sort numbers differently?
For example, a decimal mark difference[1] between locales (like comma instead of a period in floating point numbers) could yield bad results.
While potentially more efficient than bogosort for larger input size, this sorting algorithm has a serious limitation. I am of course talking about being limited to 140 characters per tweet. This seriously restricts maximum input size you can sort, which in turn severely cuts down on potential applications of this technology. Moreover, without deployed SAAS (sorting as a service) bot, algorithm is not deterministic w…