krychu

VS Code must have been lucky then.

I’m glad this doesn’t go unnoticed, and share the observation. There seem to be quite some effort going into creating illusions of truth about C. Just a personal observation.

This is how dithering tool should work. Congrats. Many popular pixel art tools have cumbersome workflows when it comes to dithering. Grafx2 is another tool that gets it right, with the sieve tool.

I recently wrote a single-file library in C for Wave Function Collapse: https://github.com/krychu/wfc

It’s a procgen algorithm that takes small image as input and generates a larger one with similar local features. I hope to add tiled method to the library some time.

Hi everyone,

Just a bit of a context: Wave Collapse Function is a method for procedural generation of images that are locally similar to the (much smaller) input image. It’s been used, for example, in roguelikes to support level generation.

> The implementation is mostly concerned with creating the correct series of data-structures, which are essentially arrays of objects. Because if we can make the game table-based we simplify the coding that needs to be done - we don't need to write per-object handlers anywhere, we can just add pointers to tables/structures.

Interesting model, could you share how this worked out for you? Good and bad?

Do you think lower levels should be dependent on higher levels as well?

I always lacked a good discussion on the subject of allocation/deallocation strategies. Is there some recommended good read?

I thought his honesty was heartwarming, and also the ability to accurately retrospect on his emotions.

Technically, we’re all stuck in the solar system.

I’m not sure the same developers would produce much better software given more time and less pressures. It may very well end up more complex and over-generalized. I think jewels are more the outcome of passion and relentless iteration.

Would search for local communities and go back to disk swapping.

I haven't been following this too closely, but is this whole thing some kind of generalization of the milliondollarpage idea?

I’m a MBP owner. But I’m sad to see that Apple makes strong statements about privacy, on stage, while sending hashes of open apps.

But it also amounted to gradient descent without any mention of information geometry.

I’d add that deciding on the subset is a high cost operation. Design of such a smaller subset-language will likely not be on par with language that is small by design.

Integer type representation is part of C.

See §6.2.6.2 in http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf

Unsigned integers are binary, while signed integers are allowed one of three well-defined representations.

Just to be clear, heap and stack are not part of C.

The proper way to learn C is to get a good book, read it, and do exercises along the way.

Here’s an excellent book: C Programming: A Modern Approach, by King.

Avoid online tutorials, and know that there are many poor books on C, including the recommended here “Learn C the Hard Way”. It has factual problems; see under “Stuff that should be avoided” here: http://iso-9899.info/wiki/Main_Page

Note also, that unlike some other languages, C is not a language that you should learn by “trying things out”, due to the nature of “undefined behavior”.

Another recommendation would be to ask for CR on IRC.

Good luck!

Looking at what was once a football pitch with regular 11 vs 11 games now you see void space, hardly recognizable as a football pitch, with nature slowly taking over, grass growing tall. Occasionally someone will take their dog out there for a run. But the pitch long forgot what it feels like to have kids run over and scream.

Thank you so much for sharing.

I remember the buckets yes! Another thing was to buy like a hundred kilos of potatoes and store them in the cellar (especially around the winter time), in wooden containers. Zero waste as potato bags were emptied and collected back by the seller. Again, you’d take another bucket and refill with potatoes when needed. Ah! And these were potatoes from local farms. Owners would bring them over in 25kg / 50kg bags on a horse carriage.

One thing I’m missing from that period is how close people were together. Yes, partially because there was not much else to do. The neighbor would just walk in to chat or borrow salt, sometimes not even knock at the door, that’s fine. On your name day anyone could show up without an invitation to the party. We, kids, played all day long outside, and you’d have 10-20 close colleagues/friends. Uncountable, captivating games, invented from things like bottle caps, ropes, knifes. You talked and interacted with other human beings all the time. On a day with no school the first thing after breakfast was to go out, and see what everyone else was up to...

These are fascinating facts. Thanks for digging this up. Does anyone know what the max rate of change around ~150m and ~500m years ago was? I reckon this information might not be available.

Such a great site! Love the simple design and lack of ornamentation.

From reading a bit more on the issue those zones are defined as free of LGBT _ideology_. Poles seem to make distinction between homosexuality and LGBT movement, which is valuable insight. But media portrays it as zones where homosexual people are not welcome. That’s not right. It’s concerning how much pressure there is to accept LGBT ideals.

Duplicating some code in the executable of this size might not be that much of a deal. I wonder if there are examples where such practice resulted in improved performance due to locality of the code. Of course you could also toy with inlines.

Great exercise indeed. Why the choice of LL over LR parsing? I thought the latter one was a more common choice for implementing languages?

Did you try search “rx pixel”? Rx is a cool name, and easy to remember. I always have troubles remembering the exact spelling of aseprite and pyxel edit, for example.

This is very helpful, especially the example at the end, thanks. I think the difficult part to understand is that dividing by n leads to an estimate that is somehow too small. The intuition tells you that dividing by n would just give you the true average.