We're getting off topic, but ... On Thursday, February 25, 2016 at 3:11:19 PM UTC-6, William Hermans wrote: > > *Frankly all this /sys/class/ file read/write and device-tree overlay >> stuff is a nightmare and nobody seems to care if changes break anything >> (it especially breaks the documentation such as it is). To expect/demand >> that a non-programmer jump into it to be able to do anything is absurd.* >> > > I do not know . . . I guess I will always view "solutions" that include > labview, or node-red( this type of thing ) as an excuse to not have to > learn how to write code. Which I view as an incredibly lame excuse . . . > because. This gives people who do not understand a system the ability to > build that system. Further, it keeps them from understanding the system > it's running on, unless they push themselves. Which I doubt most will do. >
I bet you drive a car, but could you build one, fix the transmission, etc? Do you need to know how to build a computer to program one? Are the guys at TI designing the SOCs programming experts? -- I'd wager not, given how bizarre some of the device driver code ends up being -- I'd bet the attitude is: "if it saves a micro-cent per chip, fix it later in software!" What will your friend do when he runs into a problem that is not easily > solved with, or is not solvable with this current solution ? > Odds are he'd do the same as you'd likely do when your car breaks down or your A/C unit dies -- call in someone with the expertise that you lack to come help you out. In my friend's case, that'd be me, in which case I'd would likely be jumping quickly into the nodeJS C/C++ add-ons mentioned above, and build him a few node-red function nodes to deal with it. > Anyway, with the above aside, I get why you are interested in node-red > now. I've a friend here who is a very good EE too, but does not like to > code. So perhaps this is something he would do too. If I did not write code > for his hardware projects that need it. > I'd suggesting watching a few of the node-red youTube vidoes out there, If I were building appliances and wanted to add some "smarts" to them and jump on the current Internet Of Things bandwagon, something like node-red and open source SOC boards like the BB could be a game changer. If my friend lived close by I'd probably have just offered to code for him too, but he wanted/expected to need to learn at least some programming and initially asked me to help decide what would be a better starting point -- Arduino, PIC, Beaglebone, Raspberry Pi -- small systems he'd heard about. After talking to him, once A/D and networking were in the mix the Beaglebone choice seemed clear and I stumbled across node-red pretty much by accident, but bells went off once I ran the second demo! My initial out of the box experiences with Cloud9 and Bonescript on a shinny new BBG were less than stellar, but that's another story :) --wally. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
