I'm probably not able to make a real judgement on this because my C++ experience is in embedded systems. I'm not really crazy about the system of the capitalization of names determining their visibility, but it's not the end of the world. On the other hand, my projects in other languages have ended up being way too much code crammed into only a couple files, so maybe it's a good thing. The way to get namespaces is through packages, so I end up with a lot of files and folders in my projects. Unfortunately, I find that I very much miss some of the features that were left out in order to make it simplified, such as const and enum classes. It feels to me like somewhat of a simplified C++. The workaround for that is calling it golang, but that doesn't always happen. A significant problem with Go is that it makes a horrible search keyword, which is ironic since it was created by Google. I remember a similar comment on there from, I believe, Massimo Banzi, specifically addressing a question about why Arduino chose Golang for either arduino-builder or Arduino CLI, but I can't find it now. Maybe you want to give a try to golang that can easily cross-compile forĪlmost all OS and produce a single executable binary with almost-zero So in order for me to participate in the development of the Arduino tools, or even to document them, I need to know Go.īut I know that the real question now becomes: "Why did Arduino choose Go?" Perhaps this comment from Cristian Maglie on the Arduino Developer's Mailing List provides a clue:
#Goserial example pro#
The TypeScript-based Arduino Pro IDE is a major exception to this, but that's a result of the eclipse-theia framework it's based on.
The easy answer to "why" is because this is the primary language used to write official Arduino tools now.
0 kommentar(er)
