gcirino42

5 ms·

1.
by gcirino42 9y ago
It hurts to let it go.. but I love the cause ;)
2.
by gcirino42 10y ago
Google included a complete example of how to (de)serialize data with them, as well as generating the accessor functions for JS. See https://google.github.io/flatbuffers/flatbuffers_guide_use_j... No, I don't try
3.
by gcirino42 10y ago
Yup, I'm a fan of protobufs and the more recent flatbufs. Definitely like the tooling around being able to seamlessly switch for readability. I'll check out ion.
4.
by gcirino42 10y ago
I thought my point was clear - don't get involved parsing JSON; I agree with the OP, parsing JSON is a minefield. I went further by implying that it is also unnecessary when ease of reading isn't needed, and called out some alter
5.
by gcirino42 10y ago
The correct answer to parsing JSON is... don't. We experimented last hackday with building Netflix on TVs without using JSON serialization (Netflix is very heavy on JSON payloads) by packing the bytes by hand to get a sense of how muc
6.
by gcirino42 12y ago
The data used there is cached. We were basically building around having a daughter card handle decoding the video and handling the communication with Netflix servers since there just isn't the memory (and probably not the real time ho
7.
by gcirino42 12y ago
It's definitely not fake.
8.
by gcirino42 12y ago
and I'm Guy, the other guy ;) Forgive me, it was a Monday morning when we reshot this. I think the final cart was the original PRGROM + MMC3 / 32 CHRROM banks, so it was probably more like 270k total. The video playback I was co
9.
by gcirino42 12y ago
Thanks! Alex had been studying getting better compression by repacking the tiles based on a scheme I still haven't quite figured out, but we were getting CPU --> PPU bound in what we could do during vblank. The MMC3 solution let u