Magic Lantern was created by reverse engineering an undocumented system that controls hardware.
So feel free to ask about upcoming features, but the when question only really serves to slightly irritate devs.
Despite this tight integration, Magic Lantern software does not contain any Canon code.It is an open (GPL) framework for developing extensions to the official software.DO NOT use a bootable card without a working n on it!Things changed when Magic Lantern was ported to smaller (APS-C) cameras, like 550D, 60D, 600D and 500D, which attracted developers interested in both still photography and dslr video.Then put a formatted card in the camera and try to boot without, magic Lantern.Check this forum thread: p?topic5705.0 This method gives much better results, compared to the old implementation.As soon as some new feature / bug fix becomes good enough for us, it will be included in the nightly builds.
There are two known exceptions though: EyeFi cards will not work, and startup time may be a little slower, even on non-ML cards.
A single issue might be fixed in five minutes, or it may take six months to solve.
With few exceptions, these settings can also be changed from Canon menus or controls.
Besides the bootflag (which is required for auto-boot there are a couple of other changes to Canon settings, which are saved into flash ROM by Canon firmware.
In plain photo mode with display off, the power draw is a bit higher, because Magic Lantern disables CPU powersaving features (otherwise, intervalometer and other ML functions would stop running).Magic Lantern is not approved nor endorsed by Canon in any way, and using it will probably void your warranty.Therefore, we can't be certain that it's 100 safe.The same risk is present if you use third party software for USB remote control.See features for a feature comparison table.Alternative: format the card and do a fresh install.We have measured 6 / hour on 60D (compared to 4 / hour with Canon firmware and 10 / hour on 5D Mark II (compared to 5 / hour with Canon firmware).All persistent changes can be seen in ML source code by examining the calls daily business mileage and expense log to prop_request_change.