I spent the last week clearing a trail in one of the most remote places in the country. It was an insanely steep trail, too, with plenty of poison ivy (looks like I avoided that) and ticks (I avoided most of that). We had a good time, but my finger joints are currently swollen from swinging a pick for six days.
Well, it was the last post you post until you post a new last post that will be the last post of the actual posts
The best friend of any programmer is a search engine
"Don't wish it was easier, wish you were better. Don't wish for less problems, wish for more skills. Don't wish for less challenges, wish for more wisdom" (J. Rohn)
“They did not know it was impossible so they did it” (Mark Twain)
That seems kind of obvious, to me. Computability problems were always divided into those that could be solved in reasonable time now, and those that could be solved if we had more power. There was always a different class of problems that could be said to be those that could not be solved, no matter how much power was available, so the threshold was always the case, and the hierarchy model was always misguided.
For example, when ray casting was first introduced into gaming, it allowed for first-person 3D shooters like Castle Wolfenstein 3D. That was amazing for its time, but even then we knew about ray tracing, it's just that the hardware couldn't do that fast enough for a realistic experience. So, we had the domain of what could be done fast enough, which was a small subset of what could be done...given enough time. However, also at that time, we knew about things like the Knapsack Problem, which couldn't be solved definitively no matter how much power could be thrown at it. So, we had a situation that looked like the hierarchy, since more power would appear to allow more computability, but what was really happening was that we were defining computable only in terms of "computable fast enough for our purposes."
What - no posts for 6 days. I'm geting withdrawal symptoms here as not getting my daily fix........
All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/
du vet or not du vet. That is the question. Whether 'tis nobler for the body to suffer......
All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/
if you are covered with duvet you may need to see a vet . This is a tentative of a french/english pun as the word duvet in french mean also the small feathers of the young birds ( by the way, the duvet (the object) gets its name from that as it was traditionally filled with them)
The best friend of any programmer is a search engine
"Don't wish it was easier, wish you were better. Don't wish for less problems, wish for more skills. Don't wish for less challenges, wish for more wisdom" (J. Rohn)
“They did not know it was impossible so they did it” (Mark Twain)