If you have a guarantee for the worst case of generating a pixel (which you indicate by saying that you never drop frames), couldn't you get rid of the framebuffer? Schedule pixel generation so that they complete just in time for when they're needed for output.
This would save up RAM for other things (and be a fun exercice to get right).
Yes, that would give some peace of mind, right? Unfortunately for us, that's not the case. The only platform specific code is the 8 instructions on top of "Code of framework" on http://www.sizecoding.org/wiki/Memories
First to set the video mode, and then to set up a timer used to progress time.
Not sure if this app supports it or not, but it would be very useful with a 5 second warning before being thrown into a video call. I could see all kinds of embarrassing moments happening otherwise.
Since propagation of information is limited to one cell per step, it's possible to speed this up by splitting the image into smaller subimages and solving those first, and then solve the borders between such subimages.
This technique can be used to solve multiple steps as well, the only change is that the border between subimages becomes thicker.
Could progressive mode be used to serve thumbnails by just truncating the image at a suitable point, or does the spec (and so, decoders) expect the whole image to eventually arrive?
Surprised by the negativity in the comments. This is an extremely impressive presentation of ability to put together current technologies and get the thing working front start to finish.
Interestingly (or perhaps annoyingly) enough, the placement of the 0 was different in different countries. At least in Sweden the first digit was 0, and not 1 as in this implementation. This was reflected in the emergency number which was 90000 at the time, which is easy to dial without mistakes even in a stressful situation.
Yes, I think it's frustrating that this is not widely adopted. The upsides are really obvious and the only downside (I guess?) is that it feels a bit awkward to do it before society has gotten used to it.
Another thing with obvious benefits I wish we would adopt from east Asia is wearing a face mask when having a cold to prevent infection those around you.
Cool! -betterC looks well worth exploring. Also, pure and safe are fantastic features, I just wish the default was the other way around, so you need to specify impure and unsafe.
I've heard before that "NAT is not intended as security", but isn't the effect still the same, that an external device can't connect to a device behind NAT without explicit configuration allowing it?
I'm probably missing something, but I think that, for home networks at least, NAT is wonderful because of how it requires some effort to make devices exposed on the external network. If we were given an unlimited supply of IP addresses from the ISP and all devices were accessible externally, it seems security issues in would be a much larger problem.
This article may be interesting as trivia, but the nuance of many of the words mentioned is so different from the literal translation that it doesn't make much sense.
I have used them to prove equivalence between pseudo code and optimized production code. Several rounding-related tricks and a too large search space made it very difficult to prove with traditional testing.
This would save up RAM for other things (and be a fun exercice to get right).