| Latest revision |
Your text |
| Line 27: |
Line 27: |
| | | | |
| | Or just give Google a little less than two years, and they'll make [https://cloud.google.com/vision/ Google Cloud Vision API] for you [[User:Gpk|Gpk]] ([[User talk:Gpk|talk]]) 20:39, 13 June 2016 (UTC) | | Or just give Google a little less than two years, and they'll make [https://cloud.google.com/vision/ Google Cloud Vision API] for you [[User:Gpk|Gpk]] ([[User talk:Gpk|talk]]) 20:39, 13 June 2016 (UTC) |
| − |
| |
| − | I read somewhere that when you ask CS/IT specialist for a probable ETA for solving an interesting problem, you need to multiply the given time to the ETA by 4 and take the next larger unit (a minute becomes 4 hours, an hour becomes 4 days etc.). Can't find the source of that though. [[Special:Contributions/141.101.70.229|141.101.70.229]] 15:47, 12 September 2016 (UTC)
| |
| − |
| |
| − | == GIS being "easy" ==
| |
| − |
| |
| − | All these years later, I still struggle with the classification of "are we in a national park" as "easy"..
| |
| − |
| |
| − | It 'only' requires a functioning GPS-system. A military super-project, whose [https://nation.time.com/2012/05/21/how-much-does-gps-cost/ initial setup cost 12 billion], still costs ~2 million a day, and whose principles of operation depend on [https://skeptics.stackexchange.com/questions/20230/does-gps-use-general-relativity both special '''and''' general relativity] for correctness.
| |
| − | And that's ''before'' we add the record-keeping and (internet?)logistics involved with providing each phone an accurate GIS-database. The OpenStreetMap (most likely free/gratis source of this type of data, for a cheap app) is a massive undertaking!
| |
| − |
| |
| − | (sarcasm on) GIS-lookup sure is easy! Only took a minor Manhattan-project, a literal Einstein, and an army of internet volunteers to solve!(sarcasm off)
| |
| − |
| |
| − | (I'm leaving out mobile internet access while in said National Parks (Telecom operators are among the wealthiest companies in the world, and those phone-towers-disguised-like-trees don't come cheap...), because the App would probably be shipped with a hardcoded park-database, not do live queries.)
| |
| − |
| |
| − | -- Jules @ [[Special:Contributions/162.158.91.77|162.158.91.77]] 08:13, 18 May 2020 (UTC)
| |
| − |
| |
| − | :This is about implementation of something existing, not inventing it from scratch. The use of the word "app" implies, that this comic is happening in the smartphone area, so GPS on phones should be a regular thing. --[[User:Lupo|Lupo]] ([[User talk:Lupo|talk]]) 09:57, 18 May 2020 (UTC)
| |
| − |
| |
| − | :: "app" sets the real-world context, but the punchline is about the comparative hardness '''in CS'''.
| |
| − | :: For the pragmatic app-developer, "previously solved" equals "easy"; for a doctorate in computational theory, it doesn't :-)
| |
| − | :: -- Jules @ [[Special:Contributions/162.158.91.77|162.158.91.77]] 12:16, 18 May 2020 (UTC)
| |
| − | :::That might be true, but this comic is definitely about developing an app, so it doesn't matter if GPS involves complicated hard- and software setups outside of the app or not. And unless you focus on the theoretical work also for a computer scientist, it is easy to use established GPS methods. --[[User:Lupo|Lupo]] ([[User talk:Lupo|talk]]) 12:45, 18 May 2020 (UTC)
| |
| − |
| |
| − | now deep learning is common you not need research team and five years anymore
| |
| − |
| |
| − | :And it took about five years since the comic was posted to get to that point...
| |
| − |
| |
| − | This comic is referring to doing a GIS lookup which is a glorified sql Query which has nothing to do with GPS and the the USGS spatial data a GIS database is commonly populated with is not derived from GPS information anyway. A GIS Lookup IS easy. Gathering the spatial data is difficult, though as previously mentioned its already widely and freely available for use. --[[User:PlatterMonkous|PlatterMonkous]]
| |
| − | :The GIS data is being looked at to determine if GPS-derived metadata lies within one of its boundaries, surely? Without GPS, the query has no sensible question to ask.
| |
| − | :(Then again, none of my own pictures have that sort of EXIF information. Either they're taken on a 'dumb' digital camera, that doesn't have inbuilt GPS, or even ''if'' they're done via my GPS+Camera-equipped tablet (rare) I've likely not allowed the one to be fed data that the other one knows. If it's even turned on. But the comic scenario clearly assumes otherwise.) [[Special:Contributions/172.70.86.62|172.70.86.62]] 20:21, 10 November 2022 (UTC)
| |
| − |
| |
| − | I think that, like in a number of other comic explanations, the explanation of the humour has given way to the technical exposition of the situation. What made me chuckle about this comic is the old adage in the software industry that: ''It takes 5% of the time to implement the first 95%, but 95% of time to complete the last 5%''. Even when experienced programmers correctly identify the difficult element of a problem and attempt to compensate for that difficulty in their implementation schedules, they can still be ''wildly'' off the mark. In this case, 60 years and counting... [[Special:Contributions/172.71.94.28|172.71.94.28]] 10:55, 9 August 2023 (UTC)
| |
| − |
| |
| − | The year is 2024, and there is an ArsTechnica article about the problem in this comic now being solved. https://arstechnica.com/information-technology/2024/01/famous-xkcd-comic-comes-full-circle-with-ai-bird-identifying-binoculars/ [[Special:Contributions/172.70.210.41|172.70.210.41]] 22:24, 17 January 2024 (UTC)
| |
| − | :Updated to add credit where credit is due, the research team in our reality that created the technology is the Cornell Lab of Ornithology in the Center for Avian Population Studies and Macaulay Library: https://ebird.org/about/staff -- No doubt if Ponytail was the lead the staff could've done it in half the time! [[Special:Contributions/162.158.90.24|162.158.90.24]] 22:32, 17 January 2024 (UTC)
| |
| − |
| |
| − | The rewrite of the explanation is really long overdue! If it's hard to start from scratch, someone could request GPT-4 to make a plan on how to update the article, and then use the ideas for inspiration {{unsigned ip|162.158.151.152|20:44, 13 March 2024}}
| |
| − | :If you think it could do with a rewrite, rewrite it yourself. (Stay away from GPT, though, still likely to give an unsatisfactory explanation. If not downright hallucinating.) [[Special:Contributions/172.70.86.179|172.70.86.179]] 21:01, 13 March 2024 (UTC)
| |
