user8501

I personally believe that people just answer the question “do you visualize?” differently. I used to think I had “aphantasia” but like you said, you see it without seeing it. If your eyes and brain are functioning at all, your brain is perfectly capable of creating colorful images. Just look around. Those colors you see? That’s your brain.

It is absolutely not bait. Declarative programming for the web is certainly more pleasant, but direct DOM manipulation will always and forever have a performance upper hand over rendering frameworks that sit atop the DOM. Now this performance difference is usually negligible, but for projects like VSCode or this, there’s a very good reason they aren’t written using frameworks.

Thank you for informing me. I feel dumb for having chuckled.

Testes? Do you mean tests?

Aw crap! What are we gonna do now?

That’s a very good point. I feel, however, that the main idea is that bad philosophy is what ultimately fuels complexity.

The grug brain philosophy is simplicity at all costs, unless absolutely unavoidable.

The big brain philosophy as grug sees it is reusability at all costs, unless absolutely unavoidable.

The issue with this philosophy is that it tends to lock in first generation design choices and makes iteration more difficult.

It’s true that simplicity is difficult to find, but iteration is the key to finding simplicity.

1. initialize all your variables - you will trip over this one, and it's always nasty

2. I typically throw a _ptr at then end for global pointers

3. use a unity build - create a build.c file and directly #include all .c files, and then just compile your build.c file. This will speed up compilation by many orders of magnitude, as well as allow the compiler to make better optimizations. Don't think too hard about how to separate your C files. I typically start in one file and I begin separating as themes or modules start to emerge. And even then, I wait a while, because I may change my mind. This allows my designs to become quite refined.

4. Make as few allocations as possible.

5. no comment

6. I get a personal kick out of sticking to C89, to my own detriment probably.

7. Errors are handled differently on a per function basis. But when an error requires a lot of cleanup, don't be afraid to use a GOTO.

8. Throw -fsanitize=undefined in there as well.

I think for many people, there’s an increasing feeling of dread that comes from using “modern” tools. There’s a heaviness to them that is difficult to put into words. And I think anyone who shares this sentiment feels joy when a tool feels light and airy and totally under their control.

If we didn’t reinvent the wheel we would all be riding on stone wheels.

Do people think we’re going to run out of space or something for these languages?

I’ll never understand how a persons personal triumph can be perceived negatively by another person.

Are you equally as upset when somebody paints a picture of a mountain, simply because other people have done that before?

Cool name

I can't tell if this is sarcasm. I think it's pretty groovy to pay a one time fee for software.

You need millions right off the bat unfortunately.