I have no use for the source code (nor all this fuss about it), so I'll just wait for the next normal firmware update and update as normal. I don't see the point of updating the firmware when there is no functional difference between the last firmware version and this new open source one.

I have no use for the source code (nor all this fuss about it), so I'll just wait for the next normal firmware update and update as normal. I don't see the point of updating the firmware when there is no functional difference between the last firmware version and this new open source one.

The point is to see if you can compile it yourself, as a starting point for your own fixes and improvementes, or just out of curiosity.

I have no use for the source code (nor all this fuss about it), so I'll just wait for the next normal firmware update and update as normal. I don't see the point of updating the firmware when there is no functional difference between the last firmware version and this new open source one.

One reason you may consider updating to this new version is to help verify that this new version truly is functionally identical to the prior version. As you already use the DM42 for some set of uses, running those same programs and/or calculations on the new build and verifying same results will contribute to the new DM42's known stability.

One of the reasons that Free42 and the DM42 are the fine tools that they are is because of the extensive feedback provided by the community. The new build, which obviously had a lot of 'under the hood' changes, is intended to be functionally identical, but only extensive use by a wide variety of programs and calculations will verify this is truly the case.