[1] http://defensetech.org/2012/06/22/pic-of-the-day-f-35b-shows...
292 karma · joined October 25, 2009
[1] http://defensetech.org/2012/06/22/pic-of-the-day-f-35b-shows...
Military avionics is developed in a waterfall fashion with functionality spread out over several increments.
Initial weapons capability is to be included in block 2B increment which /should/ be released to the fleet this year [1]. The fleet is currently using block 2A, the gatling gun seems to be block 3f by the release date cited in the article.
Secondly, even after the software development is done there are still /months/ of testing (including flight tests) required before it's released to the main force. As example, f35 block 2b was reportedly finished last summer but will be ready to be fielded this summer.
[1] http://www.janes.com/article/40733/farnborough-2014-block-2b...
However, don't dismiss SLIME due to emacs. It contains all the nice IDE functions - symbol completion, attaching (and editing!) long running processes, function tracing, stack tracing, find references etc.
Access to a REPL in a running system image is an amazing and productive experience.
Macros in general work by being a syntax tree -> syntax tree transformation. The neat trick is it's not a static pattern like C - you can leverage functions, conditions, etc to build that syntax tree.
As for comprehensions themselves, if you want to see the power of lisp look at the loop macro. It's a single macro yet gives you the power of normal control loops, list comprehensions, for-each all rolled into one package. [3]
[1] http://data-sorcery.org/2010/05/14/infix-math/
[2] http://www.gigamonkeys.com/book/loop-for-black-belts.html
[3] http://stackoverflow.com/questions/267862/what-makes-lisp-ma...
In older aircraft, you would've been staring at a wall of gauges, lamps, and buttons i.e., C130[1]. These, for the most part, have been consolidated into large multi-function displays (MFDs) like the C130 AMP [2] or C-5M [3] with the remaining analog controls are either there for emergency use or for the pilot's benefit like the yoke.
The MFDs generally reduce pilot workload by consolidating relevant data into task-oriented screens. However, the main driver was more likely the significant weight reductions and costs associated with manufacture and maintenance of the aircraft - fewer cockpit components and simpler wiring.
Ultimately, the types of controls are similar between the older and new aircraft. The notable exception is the keyboard(?!) in the A380s [4].
[1] http://commons.wikimedia.org/wiki/File:C-130_Hercules_cockpi... [2] C130 AMP http://www.edwards.af.mil/shared/media/photodb/photos/091109... [3] C5M http://upload.wikimedia.org/wikipedia/commons/9/9f/C-5M_Cock... [4] A380 http://www.aerospace-technology.com/uploads/newsarticle/6889...
It's not hard to dangle a micro off of i2c or some other bus, however, I can definitely see the the benefit of an easy prototyping solution combining an beefy (~100k RAM and 100Mhz CPU) real-time micro and a general purpose OS with wifi / bluetooth LE.
[1] http://www.crosstalkonline.org/storage/issue-archives/2006/2...
http://www.bloomberg.com/video/greenspan-on-bitcoin-i-guess-...
It ships with a dart2js compiler that you can use in VS. However, to really get the ease of development you're looking for you'd probably use VS to build/debug the backend, and additionally, the dart editor (special eclipse version) to debug the front-end. You'd have to enable your backend to support CORS calls for this type of setup. However, Once you are ready to deploy, the app builds to HTML/JS/CSS files that you can just embed normally in your solution.
I think what you're getting at is - is it better than JS or typescript + angular or backbone? It'd probably a matter of taste. The language is different from the "syntactic sugar" on top of JS that typescript is. Dart lets your bridge to standard JS libraries (i.e., Jquery etc), but, it also provides most of the functionality in the standard library. It provide a built-in unit test and logging framework and a nuget style repository of other libraries. Additionally, Dart's Polymer library provides an MVVM framework. You can define controls and combine into single-page webapps.
If one of these were to stick - it would first need to be supported be a somewhat larger organization (ala apache foundation for java components, or google for GWT/Closure).