In terms of process migration I still think Google has missed a trick by not marrying Android and light-weight containers. If I could flick my wrist to send a phone process to my Chromebook, Android tablet, Andromeda device or smart TV life would be pretty interesting. Maybe one gesture for screen mirroring and another to move rather than mirror or copy the process.
This would also open up new channels for malware sure but also cool things like trusted processes / data for authentication. You have an invitation to my party, you say? Dock it with my Google Home device which signed your invitation to prove it, then...
Our next hardware generation will have a dedicated FPGA handling the communication with the GPS, IMU, servos. The compute platform will communicate with the FPGA over Ethernet. This means that all hardware drivers can be written against a network based interface, resulting in a loose coupling between the compute and IO. This means that both the IO hardware and compute hardware can be replaced individually without breaking the setup, and without having to rewrite any drivers. It also results in high transparency for debugging IO, with the possibility of easily recording and playing back a scenario. You can also test the full flight software on a developer's desktop machine during development without the embedded compute platform.
As embedded compute platforms get better all the time, while the IO stays more stable, this will make it easy to replace the compute every 2-3 years.
You're applying the same mental model to hardware which can be seen in the similarity of tools that can be enabled on top of such abstraction. Way to go!
The flexibility that emerges from decoupling our software and hardware solutions is a [recent] trend that will only gain on traction as more people become aware of it's implications to how we create solutions to technological problems.
How can we evangelize this better? From my experience it's complicated to communicate this idea well.
not sure if true, may be recency bias or the fact that I'm still young and inexperienced in many ways and lack historical background knowledge in tech
Our opinion is that Ethernet is easier to analyze using tools such as Wireshark, in addition to being easier to run in a cable between different PCAs. It also allows the IO board to be easily networked for communicating with development tools to reprogram the FPGA memory, debug issues, do testing from a developer machine etc without concern for driver issues on various host operating systems.
https://www.youtube.com/watch?v=kUfp87cDaE0 (2016)
https://www.youtube.com/watch?v=Prz7yc1i4ac (2014)
Another of their summer projects this year was the "CoastalShark" autonomous jetski where they constructed a sophisticated autonomous surface vessel. For their demonstration they used it to pull a guy on water skis:
Then you realize why nobody shows up to your parties. :P
>Then you realize why nobody shows up to your parties. :P
Sure they do, but they're all hackers or cypherpunks. Listen all three of us had a great time. :-) :-)
But seriously, wouldn't it be fun to host a party where everyone had to hack an invitation?
It has two major downsides right now. There's no win32 support, so there's not much to run on the desktop, which MS is going to address by bringing x86 emulation to arm. Secondly, the hardware isn't quite powerful enough, which limits the max. resolution and the ability to multitask, which the new qualcomm 835 based phones with 4+ gb of ram should address.
It is impressive, but I haven't found a use for it. After all, when you have a laptop, why use it to run apps from your phone?
This is exactly why x86-emulation-on-ARM (http://arstechnica.com/information-technology/2016/11/x86-em...) is a very exciting project from Microsoft.
As mobile chips continue to improve, emulating x86 becomes a viable way of tapping into the huge Windows ecosystem of applications when not running on battery power.
I think this is Microsoft's last shot of becoming relevant in the mobile space.
You could combine it with something like a nexdock to also turn it into a laptop. Would be cheaper than getting a phone, and a desktop pc and a laptop, and it would avoid all those nasty issues with keeping devices in sync.
The qualcomm 820 already performed at core m levels, and the 835 is 25% faster, so it should be fine if paired with enough ram and storage.
The problem isn't power. Phones have been powerful enough for about 5 years (since around iPhone 4s, as a means of dating it).
Android was out at that point, but could barely do video out by blanking the phone screen. Forget about operating it via other means. And i don't think iPhone was doing much better.
One reason why i feel the focus on those platforms reset mobile device progress by a decade.
Speaking to retailers recently, demand is for office apps usable on touch. i.e. if it can possibly done without a keyboard, people will do that. From listening to users, they will moan and complain about touch "productivity" apps... but will choose it.
Personally, I switched entirely to a phone a year ago... though with a bluetooth keyboard.
Where Intel can win is if a standard x86 Linux distribution could boot off of this with little modification. Right now in the ARM world, unless your device supports device tree configuration, kernels are highly customized per device.
actually it's PCMCIA connectors (which have nothing to do with PCI express)
USB-C is a really cool solution, but a solution for the needs of laptops/other personal devices, not servers.
* Dead simple design. * Easily hot-swappable without expensive proprietary connectors. * Low cost solution that provides adequate bandwidth.
This isn't something that will perform better than a proper server with actual PCIe lanes, but it will perform better than a blade from two generations ago that didn't have that kind of backplane bandwidth and it will cost less to manufacture.
A nice side-effect might be that interfaces become more open, and you can run e.g. whatever OS you like inside your smart cheese grater.
I feel like USB-C gives much more flexibility: it has a well-defined configuration enumeration protocol that's already supported everywhere. There's a lot more options for extensibility and future-proofing with USB-C.
With the onboard storage this is one step closer to my dream: the ability to plug a phone's compute module into a desktop to give me access to a more powerful GPU, extra storage, etc.
My big question: will this card format be an open standard, or will Intel be locking it down?