I don't think we should be teaching our kids exponential running time O(n^2) algorithms. Randomized partitioned merge sort theta(n lg n). Sure, bubble sorts seem harmless today, it leads to criminal token rings.
Slashdot videos: Now with more Slashdot!
Ok ok. I always thought Angular was dependent on node because I always saw them together. I apologize for that one singular inaccuracy. The rest is true.
The point remains. To pick up
I've been a cross-platform coder for about a decade now. I liked the ideas of Java and
And there in I think the real danger is realized. If you use
With the very good developments in Linux and the Apple premium is gone, only organizations with legacy applications need consider any Microsoft technology.
PS. I use Qt for everything on Mobile and desktop, Node for server and Knockout/Angular for web client. There is a slight possibility that Qt's QML will work on the web. Python for anything else. This is crossplatform, and not one drop of MS. It is my speculation that MS is a wounded animal, realizing they are like Cadillac. Cadillac realized the average age of their customers were getting older, and over 60 and that market would be no longer driving in a few years. There's an exodus from MS platforms. Their new focus aims to fix this. Buyer beware. Where is the money in it for them?
I dug through the actual legislation (FAA charter) and that's what I found. I urge you to do the same. While controlled and uncontrolled ate the vernacular, the statutes that govern the FAA jurisdiction use "navigable". Therefore when speaking of legal matters and the FAA legal authority, we must use the same terms to prevent confusion.
FAA only has jurisdiction over navigable and restricted airspace. Which means that unless you are in restricted airspace, up to 500 ft is still faie game. 500ft is the limit on kites.
Wouldn't a VPN on your mobile device block this?
I've been following this reactive programming "movement" and it's all traced back to one guy who has a consultancy in "reactive programming" This is the 4th such reactive programming post that I am aware of on
In addition, the
I call on slashdot to identify what articles are slashvertisements and or are carried on special grounds.
Google's NaCL only works with x86 the majority of apps use native libraries that are ARM. Only pure Android SDK apps (Java and java dependencies) will work. So say if you use libZbar (bar code decoding library) which is supplied in x86 and ARM, will work, is that app packaged the x86 version... which they didn't do becuase no one runs android on x86....
So that's the main technical reason.
With that device in that contraption and strapped to my head?
Now they have removed the only thing that ties drama to reality. Having to deak with existing Deux Ex Machina in modern drama was bad enough. Now we have a whole new genre, which will resemble cop dramas. We will have "robocop dramas". I for one do not welcome robocop dramas.
I'm not sure where you misunderstood me. I said "virtual frame buffer" and VNC. The virtual frame buffer is a software-only framebuffer, separate from the one that drives the screen. It can have anything on it - simplified UI controls, or rather, with android, you would add settings to the app manifest to specify it uses that VFB and people would lay out for in-car use accordingly.
The automobile is a challenging acoustic environment for sure, but there are several improvements that can be made to improve this:
A unidirectional mic in the steering wheel, with noise cancelling. A prompt button that turns down the stereo system for a brief time.
I'm not surprised it is as bad as it is with current equipment. In fact I'm surprised it is as good as it is.
The tactile controls are there for cost. Very cheap, but very limiting. I have proper climate control that maintains a set point, and I never have to touch anything more than a defroster button. In fact the only button I touch frequently is the stereo knob.
I don't see why it shouldn't.
How complicated of gestures do you need on a screen while driving? As far as I am concerned it should all be voice interface anyway. As someone who uses a docked phone while driving (or rather attempts to) the bumps in the road combined with the reach distance conspire against virtual buttons due to lack of tactile feedback. You can't feel for the 3rd button down, or if you landed your finger on the gap between two buttons.
Each mobile platform (iOS, Android, WP?) should just have a virtual frame buffer which is connected to via VNC. There's not any reason to make it more integrated than that, unless they try to differentiate themselves, and in that case we all lose because of fractured standards. I really cringe when Google and Apple don;t back the same standard.
If you need audio, use Bluetooth, of course.