# Updates YOU want to see in Makecode

**URL:** https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713
**Category:** Forum Feedback
**Tags:** music, make, demo, extension, game
**Created:** [May 16, 2025, 7:39pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713 "2025-05-16T19:39:14Z")
**Posts on this page:** 1
**Showing post:** 186

<div class="post-metadata">

### Author: ![WoofWoof](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/woofwoof/32/32523_2.png) [@WoofWoof](https://forum.makecode.com/u/WoofWoof)
#### Post date: [November 17, 2025, 9:33pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/186 "2025-11-17T21:33:13Z")

</div>

> [@The Quest for More Colors](https://forum.makecode.com/t/the-quest-for-more-colors/35551/7):
>
> the reason we do 4 bits per pixel is 100% because of memory; packing and unpacking bytes every time we change a pixel is pretty significantly slower than just using one byte per pixel.
> 
> but the memory saving makes it worth it. each screen is 160\*120 pixels which comes out to roughly 10kb per screen. we have two screens in memory at given time (i.e. we double buffer the screen) so that’s 20kb total. the processor in the meowbit, the STM32F401RET6, has a whopping 96kb of RAM, so that’s not much left over for the user program!

---

_[View the full topic](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713)._