In the past three months, as I’ve said before, I’ve come to realize that it’s very important to have a good, practical, and logical way to ask questions and that’s why I’ve tried to give you a few examples. In the past three months, I’ve come to realize that I’m not entirely a complete thinker. The way I think and feel is different.
This is something that a lot of computer science students learn, but not many people are actually taught how to do it! Im glad that you’re noticing this, because it’s really important! We do a lot of stuff that is “dumb”, but doesn’t really take into account the practicality of things. For example, one of our interview questions was “What’s the most efficient way to copy a file from one computer to another computer?”.
This is something that Im glad you’re noticing because it highlights a good way to think about what a file is. The file you’re copying is a “virtual file” that is really just a representation of some other data. It is data that has been “mapped” into a certain place in memory. This is what people sometimes call “virtual memory.” This is also what people sometimes call “hard memory.
One of the reasons that we love virtual memory so much is that it allows you to just “write to” any place in memory, like the address space of your computer. If you have a large, complex data set, you can actually “write” it to any place in memory. This is a very efficient use of space.
Virtual memory is still very much in its infancy, though. There are a lot of problems and features that still need to be worked out, like data sharing and memory mappings. One of the most exciting projects I’ve seen recently is the introduction of embedded systems at Google. Embedded systems are the new equivalent of big computer systems with a tiny, low-cost processor, and the goal is to make it simple to create and run those.
I think this is a good thing, but I also think it’s a bad thing. While the embedded systems are extremely low-power and low-cost, they are still very high-security. How so? Well, as I understand it, the embedded system has a very high level of security because it can be accessed only by the company that owns the chip. This means the chip has to be completely isolated from the rest of the world in order to prevent anyone from seeing it.
If you want to get a really high degree of security (ie, you want to be able to see the embedded system’s contents), the embedded systems are going to be a lot more expensive. The reason why is that the chip has to be built with a bunch of very expensive, high-security components to make the chip undetectable. This means that the chip has to be built with very expensive materials, and then be made to transmit its contents over a huge variety of networks.
This is where the technology really shines. By letting the embedded systems perform their own security, they are able to do it in a much more efficient way (and thus at lower cost). So why are embedded systems so expensive? For one, the more expensive computer you purchase, the more it has to be built to meet security rules. The chip itself is also typically a more expensive part of the system. So, the embedded systems will cost more, but will be more efficient.
I think the main reason is that embedded systems can’t really perform as well as the CPU (Central Processing Unit) on the motherboard, as they are usually under-performing, so they are usually over-priced. The embedded system also typically has a longer development time frame than the motherboard, and takes longer to get into production. So, I think it’s a cost issue, rather than a performance issue.
That being said, embedded systems are fairly inexpensive. And, once you’ve figured out how to code them, they get even more so. I love the way embedded systems work, and I think they can change the way we do business. It’s amazing to think about how much more efficient the world would be if we used embedded systems instead of CPU Central Processing Units.
