mdns-discovery
TinyGo
Our great sponsors
mdns-discovery | TinyGo | |
---|---|---|
1 | 95 | |
16 | 14,479 | |
- | 1.8% | |
5.3 | 9.3 | |
about 1 month ago | 4 days ago | |
Go | Go | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mdns-discovery
-
When will network boards be added to IDE 2.0
The repository of the mdns-discovery tool that provides discovery of these ports for Arduino IDE 2.x is here: https://github.com/arduino/mdns-discovery However, it does not contain any documentation about how that specific discovery works and I'm not aware of any documentation on this subject.There is documentation about how pluggable discovery works in general here (but I don't think that is what they are looking for): https://arduino.github.io/arduino-cli/latest/pluggable-discovery-specification/As for debugging, I normally instruct people to run the relevant discovery tool directly. This allows us to remove Arduino IDE and Arduino CLI from the equation entirely to determine whether the problem is occurring at the discovery level or lower. I provide instructions for doing that here: https://forum.arduino.cc/t/ide-2-0-ota-mdns-discovery-only-intermittently-finds-nodes/1036850/4
TinyGo
- Gokrazy – Go Appliances
-
A "Tiny" APISIX Plugin
Reading through the documentation, you will understand why this plugin is called "tiny," i.e., the SDK uses the TinyGo compiler instead of the official Go compiler. You can read more about why this is the case on the SDK\'s overview page, but the TLDR version is that the Go compiler can only produce Wasm binaries that run in the browser.
-
What's Zig got that C, Rust and Go don't have? [video]
Not only you can fit Go into a kernel, there is at least two products that do so.
TamaGo, used to write the firmware used in USB armory.
https://www.withsecure.com/en/solutions/innovative-security-...
TinyGo, which even has official Arduino and ARM support, and is sponsored by Google
https://tinygo.org/
Ah but that isn't proper Go! Well neither is the C code that is allowed to be used in typical kernel code, almost nothing from ISO C standard library is available, and usually plenty of compiler specific language extensions are used instead.
-
Show HN: A new stdlib for Golang focusing on platform native support
Reminds me of https://tinygo.org/ - a project that brings Golang to embedded devices, browser (wasm) contexts. Do you converge or diverge from that project?
- TinyGo release 0.29 is out
-
Pico with C
You should also consider TinyGo. It can compile Go for the Pico, and is starting to get good device support.
-
Rust 1.71.0
Thankfully some folks completly ignored whatever the rest of the world thinks system programming is all about and created:
- TinyGo (https://tinygo.org/), which is acknowledged by people in the industry[0][1]
- TamaGo unikernel on USB Armory secure key (https://www.withsecure.com/de/solutions/innovative-security-...)
And then there is the question if writing compilers, assemblers, linkers is systems programming or not.
[0]-https://www.cnx-software.com/2019/08/28/tinygo-go-compiler-f...
[1]-https://twitter.com/ArmSoftwareDev/status/131680481331796787...
-
When would you (not) recommend Go over Rust?
Have you seen TinyGo? In the case of embedded system I would probably still chose C over Rust if the system didn't support dynamic memory allocation, and most embedded systems do not.
-
“C is quirky, flawed, and an enormous success” – Dennis Ritchie
>I really hate how for microcontrollers the only two choices are either C++ or Micropython
There's TinyGo as well. https://tinygo.org/
-
WebAssembly System Interface (WASI) with sockets for Go
Gist link fixed, thanks. Compared to TinyGo, Go with GOOS=wasip1 will probably generate larger artifacts (at least, for now). This is because it bundles the entire Go runtime. The benefit is that it fully supports goroutine scheduling and non-blocking I/O. TinyGo (I believe) still uses a custom asyncify pass and does not support non-blocking I/O nor basic WASI networking (e.g. https://github.com/tinygo-org/tinygo/pull/2748 never landed, but GOOS=wasip1 supports it).
What are some alternatives?
MicroPython - MicroPython - a lean and efficient Python implementation for microcontrollers and constrained systems
go - The Go programming language
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
micropython-ulab - a numpy-like fast vector module for micropython, circuitpython, and their derivatives
awesome-micropython - A curated list of awesome MicroPython libraries, frameworks, software and resources.
PlatformIO - Your Gateway to Embedded Software Development Excellence :alien:
zephyr - Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
rqlite - The lightweight, distributed relational database built on SQLite.
dgraph - The high-performance database for modern applications
sql-migrate - SQL schema migration tool for Go.
wfb-ng - WFB-NG - the next generation of long-range packet radio link based on raw WiFi radio
Odin - Odin Programming Language