3 ms·
Just got told about tinygo on another thread where I was saying rust is the obvious only choice. But tinygo looks nice. I've written very little go professional
by galangalalgol 4y ago
Just got told about tinygo on another thread where I was saying rust is the obvious only choice. But tinygo looks nice. I've written very little go professionally, and rust only for a few months more. Go does seem super easy. But rust doesn't really seem hard either. And the fearless concurrency is really attractivento not have to think much about data races too much.
Either one is nicer than c++ which I have a quarter century of experience at.
- throwaway894345 4y agoTinyGo still has a GC, right?
- galangalalgol 4y agoIt does. https://aykevl.nl/2020/09/gc-tinygo https://aykevl.nl/2020/09/gc-tinygo Edit: but that said with sich constrained resources do people really use gc or even dynamic memory allocation often in embedded? I work embedded and it is usually standard practice to preallocate everything to avoid fragmentation. Unless it is a more performant device in which case I'll add the quotes to "embedded". But for those you could just use normal go, or python for that matter.