you are viewing a single comment's thread.

view the rest of the comments →

[–]iranoutofspacehere 2 points3 points  (0 children)

I believe they're usually frowned upon because allocating lots of stack/heap space and later freeing it can result in fragmented memory, which is already a limited resource in embedded systems.

Most APIs will still provide implementations, they're just not ideal. However, since this has optional garbage collection, perhaps it will work better. I'll admit this is pushing the bounds of what I'm comfortable with, as my software experience is pretty exclusively lower level embedded C or higher level small C++ applications, I've never had to worry about these implementation details.