5,567 karma · joined October 5, 2010
I want to write stuff to disk (SSD these days). I can issue a request, then have to wait tens to hundreds of milliseconds (in the average case, the worst case can be far longer) for that request to finish and let me know that my I/O request succeeded or failed. There's no getting around that with present-day technology.
The situation is worse and even less reliable with network I/O. If you are talking to a server in another continent, the speed of light determines the minimum of time I hear back from it, even if it (and all the intermediary network links) are lightly loaded and functioning perfectly.
That's a really asinine failure mechanism. At the very least, it should create "filename-FAILED_TO_RESTORE" or something like that.
Something that I was instructed to do nearly 30 years ago when at Motorola was: never overwrite the original files. Standard procedure was to make a directory called "BACKUP" (or "RESTORE"?) and put the files in there instead. The requesting person was then responsible for moving the files back to their original location, so any screwups were on them, not us (IT).
I'm sure it will be exciting. I just hope sufficient SH engines remain running long enough to try the staging event.
For example, on the wikidata help page, they talk about the height of Mount Everest:
https://www.wikidata.org/wiki/Help:About_data#Structuring_da...
Earth (Q2) (item) → highest point (P610) (property) → Mount Everest (Q513) (value)
and Mount Everest (Q513) (item) → instance of (P31) (property) → mountain (Q8502) (value)
So that's all fine, but it misses a lot of context. These facts might be true for the real world, right now, but they won't always be true. Even in the not-so-distant past, the height of Everest was lower, because of tectonic plate movement. And maybe in the future it will go even higher due to tectonics, or maybe it will go lower due to erosion.Context awareness gets even more important when talking about facts like "the iPhone is the best selling phone", for example. That might be true right now, but it certainly wasn't true back in 2006, before the phone was released.
Context also comes in many forms, which can be necessary for useful reasoning. For example, consider the question: "What would be the highest mountain in the world, if someone blew up the peak of Everest with a bomb?" This question isn't about the real world, right here and right now, it is about a hypothetical world that doesn't exist.
Going a little further afield, you may want to ask a question like "Who is the best captain of the Enterprise?". This might be about the actual US Navy CVN-64 ship named "Enterprise", the planned CVN-80, or the older ship CV-6 Enterprise which fought in WW2. Or maybe a relevant context to the question was "Star Trek", and we're in one of several fictional worlds instead, which would result in a completely different set of facts.
I think some ability to deal with uncertainly (as with Probabilistic Graphical Models) is also necessary to deal with practical applications of this technology. We may be dealing with a mix of "objective facts" (well, let's not get into a discussion about the philosophy of science) and other facts that we may not be so certain about.
It seems to me that successful symbolic reasoning system will be very, very large and complex. I'm not at all sure even how such knowledge should be represented, never mind the issue of trying to capture it all in digital form.
If you don't want to spend a lot on a phone, you can do that.
What does cost more is final testing, to make sure all the components work together. It is cheaper to do that well at the end of the assembly process before starting packaging, than to deal with a high rate of returns. The testing done throughout the manufacturing process is a significant cost.
So you'd use the NN to recognize that the thing in front of the camera is a cat, and that would be fed into the symbolic knowledge base for further reasoning.
The knowledge base will contain facts like the cat is likely to "meow" at some point, especially if it wants attention. Based on the relevant context, the knowledge base would also know that the cat is unlikely to be able to talk, unless it is a cat in a work of fiction, for example.
It feels quite icky to do this, but it is necessary when making policy decisions.
Every day, governments and corporations decide to spend (or not spend) X amount of dollars to save Y number of lives. Does it make sense to spend some money on infant mortality prevention, vs research on cancer types that only really old people get? What about seatbelt laws? Or pollution prevention?
Ideally, we would rationally spend our limited money on providing the best life for the most people. Not that this actually happens for a variety of reasons.
If we are to get the best value for our money, then we need to assign a value to human life in terms similar to disability-adjusted life years (DALY):
https://www.who.int/data/gho/indicator-metadata-registry/imr...
Here in the USA, yes. Some EU countries take this quite a bit more seriously, to good effect.
I did like seeing the live images captured during descent, I also hope those get made into a video and posted online.
Looking forward to the rover deployment too.
The goal is for these young people, naive and hopeful, to go out into the world and be rejected by it. The elders want these kids to repeatedly face rudeness and rejection. They want to instill the belief in the kids on mission the idea that the LDS Church alone is the moral beacon, the guiding light of the world. The only true and holy path.
The elders don't actually expect that the kids on mission are going to get a statistically significant number of converts just going door-to-door in some other part of the country. They see that the key to increasing their power, and increasing membership in the LDS Church is to retain within the religion as many kids as possible.
Sure, they'll lose some kids, but maybe those would have been disruptive anyway. If the church has done a good job of indoctrination on these kids since birth, then most of the kids will stay. And if the greater world rejects them, then the kids may think that the church is their only true home.
One of the interesting tradeoffs with AR/VR systems is that there is less emphasis on just frames-per-second, and more emphasis on consistent latency and low lag between user input and photons coming out of the screen. This may continue to drive a divergence between dedicated AR/VR systems and "normal" game consoles & PCs. The input requirements for AR/VR are also much higher than a game pad sampled at high frequency.
What forces are keeping the various implementations aligned and moving in the same direction? What is driving them apart? What does the future look like?