On Wednesday, January 2, 2019 at 7:23:49 PM UTC-5, Wim Lewis wrote: > > Go's GC pauses and Linux's preemptions make them bad choices for this if > occasional random failures are unacceptable, but in practice, for tinkering > purposes, I think they're both fine ---
That is my current thinking, do it in go, learn and if when I get smarter, I find it doesn't work, I can adjust. I've already learned to use 20 or 30 languages, so learning a couple more is not a big deal. I know that python has a lot of fans, but go meets my theology far better than python Plus Rob Pike keeps saying that the GC is getting better every release and I believe in Rob Pike > 2) what hardware should I use? RaspberryPI, or some super Arduino? or a > more specific microcontroller, perhaps controlled by a R-PI? > > RasPIs are cheap and have a large community, but are a little weak at I/O. > I'm a big fan of the Beaglebone, which is not quite at RasPI's level I'm going to start with an R-Pi, and see. Weak at IO matches up nicely with Linux's refusal to really do real time. I half expected everyone to yell "you have to use a RTOS" but that hasn't happened. Maybe all the RTOS folks have already rejected go. I've done far too much professional C, I have no interest in doing it for fun. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
