- Wed Jun 07, 2017 4:21 pm
electronicsguy wrote:<...>Still doesn't change the fact the RC is just that: "RC". There hasn't been a release for almost a year now and no word from developers on this issue. For part-time hobbyists, that means it's frozen.
So, I went up to your blog\ to get an impression of your mind-set; nice blog by the way. Obviously, your concern over the RC is not a mindless rant; your blog shows an informed, articulate individual. So...
I am just going to disagree about the RC being "frozen" and agree with you that things just are moving slower than you or I (and likely many others) would prefer. On the other end of tbe world, ArduinoIDE is moving faster than I would prefer.
I once managed a group of 10 JAVA programmers many years ago and the tools and libraries often changed more than once per week. As the product was commercial, strict change controls were in place: I and other managers wasted lot of time reading, analyzing, testing, and doing critical analysis and risk management on every single patch. There is much truth in the programming equivalence of the expression, "The Devil you know..." At some point, one must freeze the development environment (and bugs) and move forward with the real work.
As an enthusiast, a programmer, and a writer
I feel that there is simply no need to have a "constantly evolving" product in the educational or hobby space... "RC" is good 'nuff in my opinion. The key is to identify and comment all work-around methods in the source and also to provide the reader with the IDE version, 3rd party library versions, and ESP8266 core date/version. I even move many libraries into the sketch folder to protect from vendor library updates. Then, I publish and move on. Some of my published projects require Arduino IDE version 1.0.6 of they will fail to compile. And no, I do not go back and edit/fix things that do not work on newer tools! That would just make me too busy to do anything new.