3 ms·
Instead of lambasting it for a low number, perhaps you could tell us what you'd have a child do in 17KB that they couldn't do in 16KB? It's an educational devi
by OJFord 10y ago
Instead of lambasting it for a low number, perhaps you could tell us what you'd have a child do in 17KB that they couldn't do in 16KB?
It's an educational device, and that education involves learning to write pieces of code for which industry users may well prefer to pull in large libraries. I'd be surprised if the target audience - 12-13 year olds - use all that; those that have a passion for it will of course end up using more expensive devices with bigger numbers. Those that don't will continue doing only compulsory exercises that could probably manage with less than 16KB.
- mietek 10y agoQuoting from the fine article, which you clearly have not read: “Finally, the micro:bit’s 16 kB of RAM is quite limiting, at least when using the MicroPython runtime. While writing a moderate-size program I managed to repeatedly exhaust the SoC’s memory, resulting in difficult to debug MemoryExceptions. I can easily imagine intermediate users running up against and being confused by this limitation, and would welcome a version of the micro:bit with double the RAM.”
- OJFord 10y ago> the fine article, which you clearly have not read https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html > " ... easily imagine intermediate users running up against ... " Something tells me the author isn't imagining the 12-13 year-old target audience when writing 'intermediate users'. There's nothing wrong with reviewing it from a different audience's perspective of course, but it doesn't do to ignore it if you're going to complain about the device's specification.