Among the auto manufacturers offerings, some 'lane assist' systems can only handle the most simple of turns (taking you out of the lane, _very scary_). These systems are too simple IMHO with single cameras and or no mix of additional systems.
Tesla seems to want a system that is more complex. Things like "have the car come meet you from where it was parked", lane _crossing_ (let alone lane keep assist), and eventually on-off ramp driving. All with live updates rather than going into the dealer.
What makes this offering (potentially) different is the ambitious intended use of the system, something which would make even a Daimler-Benz lawyer cringe.
When I first saw the Google barges, the first thing I thought to myself was that It was a testing ground for Robotics. Multi-pedal, wheeled, and arial robots. I still hold to it until they show pictures from the inside. :-)
My CPU intensive work is wrapped around services. This can be direct native calls to libs (c or openmp), actors via akka, finagle, storm, Hadoop, spark or mesos for that matter. The beauty of node is it's single threaded-ness. Doesn't mean I cannot orchestrate these single threaded apps as services, asynchronously. Freeing me up from thinking too much about locks and low level context switching.
Now not to say you can't have it "just because", a worthy exercise I'm sure. But in the coming years we will all be asked to use multicores, multiple machines, and multiple data centers. For these scenarios, it may make more sense to think high order.
Hopefully I made some sense, I happen to be on my mobile device.
"...for compatibility reasons, we still support the entire ARMv7 machine in the new ARMv8 architecture, but when running 64-bit software, this part of the machine is not being used, and the area of complex legacy it had built up does not need to be active when running in the 64-bit ISA, unlike other architectures where 64-bit extension was simply added to the historical complexity and legacy of their 32-bit mode. The new ISA drew upon the years of experience of building different micro architecture implementations, so again it was defined so that these new processors can be more easily optimized for low power operation — an opportunity not really offered since the first ARMv4 machine that resulted in the now legendary low power ARM7 processors."
Personally I hear "someday it will turn into a project" all the time. More times than not it never does.
I'm actually ok if someone doesn't have an extensive github (or any for that matter) on an interview, because I will spend the time and talk with them. I totally understand however that more or less many firms try to filter out some of the mass piles of resumes by using github. But most people aren't like me who want to dig in and _work_ with `you`.
Having said that I very much still like to see a github link. Here is why (and they are biased toward synergy in a coop manner, which is how I culturally work; you may be different):
- You spent the time to do something you thought was cool (dedication)
- You did the above regardless of how it looked which amongst many things to me means you have thick skin and are willing to learn (it's a two way street mind you).
- you've learned to communicate with other developers => _on their terms_
- you are not living in a cave and open source doesn't come to you from only one foss org or your one fav info site.
- you are willing to dive into code (forking) and making the changes necessary even if it means doing it yourself
- good ole adding to the knowledge of society (you just don't do it for the money, you have more than one dimension which drives you)
At least these are my opinions and I hope that at least you might be able to see one take of many on why some might want to see a github link.
Btw, If anyone else feels the same way, feel free to ping me! Always nice to meet other devs that share some of my views!
Really now? As if these guys get paid to do create and fix scalaz all day right? Like Oracle yeah? This is the story about every single open source project. You can choose something else, wait it out for documentation, or contribute it. Lucky you even have the source!