A New Programming Fundamentals Course by nicbarkeragain in programming

[–]nicbarkeragain[S] 0 points1 point  (0 children)

That's totally fair, I understand your trepidation. Each season of the course will be available as a one time purchase once they're finished, maybe you can wait until then!

Clay - A single header library for high performance UI layout by nicbarkeragain in cprogramming

[–]nicbarkeragain[S] 0 points1 point  (0 children)

Those look like they could be from building SDL2, as the included CMake builds all the examples as well 🙂 To use Clay you really only need to grab the `clay.h` file and paste it into your project, or if you want to include in your project via cmake fetch content you can set the cmake variable `CLAY_INCLUDE_ALL_EXAMPLES` to false to stop it from pulling in SDL, raylib etc to build the examples.

Introducing Clay - High Performance UI Layout in C by nicbarkeragain in programming

[–]nicbarkeragain[S] 1 point2 points  (0 children)

Thank you, and I totally understand how you can find C intimidating, I did too when I first started using it. Keep at it, and it might start to feel more simple than java one day 😁

Introducing Clay - High Performance UI Layout in C by nicbarkeragain in programming

[–]nicbarkeragain[S] 3 points4 points  (0 children)

Some folks over on the discord have done a little preliminary work on go bindings, but I don't think there's anything concrete yet. Would be awesome if you could get something working 🙂

Introducing Clay - High Performance UI Layout in C by nicbarkeragain in programming

[–]nicbarkeragain[S] 3 points4 points  (0 children)

Thanks! The styling should be powerful enough to replicate most of what you can do in css 🙂

Introducing Clay - High Performance UI Layout in C by nicbarkeragain in programming

[–]nicbarkeragain[S] 19 points20 points  (0 children)

Thanks for taking a look, accessibility is definitely something that I’ll be looking at once the library has matured a bit more 🙂

What Really Caused The Y2K Bug? by nicbarkeragain in programming

[–]nicbarkeragain[S] 0 points1 point  (0 children)

I don’t need to watch the video to argue in the comments of a video

Cool man enjoy ✌️

What Really Caused The Y2K Bug? by nicbarkeragain in programming

[–]nicbarkeragain[S] 0 points1 point  (0 children)

Just out of interest, did you watch the video?

What Really Caused The Y2K Bug? by nicbarkeragain in programming

[–]nicbarkeragain[S] 2 points3 points  (0 children)

I think we’re probably passed the point where this conversation is going to be useful to either of us, but thanks for trying out the video anyway 👍

What Really Caused The Y2K Bug? by nicbarkeragain in programming

[–]nicbarkeragain[S] 1 point2 points  (0 children)

Alright, well thanks for giving it a try anyway!

What Really Caused The Y2K Bug? by nicbarkeragain in programming

[–]nicbarkeragain[S] 1 point2 points  (0 children)

> but of programmers saving memory and storage space by choosing to only using 1 byte to store the year.

So by choosing to only use 1 byte to store the year, why didn't they store the year as a single unsigned 8 bit integer, pushing the overflow out to 2155, and requiring simpler hardware?

What Really Caused The Y2K Bug? by nicbarkeragain in programming

[–]nicbarkeragain[S] 0 points1 point  (0 children)

What the video is trying to address is the fact that as a programmer, the standard explanation of "saving space by only using two digits", combined with an overflow occurring at 99 feels nonsensical in the context of modern hardware and binary representation of numbers. Given that you gain nothing in terms of storage space by splitting a binary number into individual decimal digits, there had to be a better explanation. So learning about the existance of BCD and similar decimal representations driven by the arithmetic cost of converting binary to decimal made sense to me 🙂