Hacker News new | past | comments | ask | show | jobs | submit login

The worst part about using Go for embedded systems is that there's no way to disable dynamic memory allocation (which can be unreliable and/or hard to reason about) - at least last I checked. This is brought up in the essay "Go is Not Good".

Memory-mapped I/O is possible, but there's no way to separate such unsafe constructs from "safe" ones, as that essay points out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: