Programming thread

[mnt_ms]

When you're decent at assembly, it comes off as wizardry to most mere mortals.

Which is funny because at its core it's quite easy. No super complicated concepts, very simple tools. It just takes more time.

 

[canalCrab]

There’s a relatively recently added compiler intrinsic in GCC you might find interesting, but I wouldn’t trust nested functions much because of trampolining

Forced to use c99, at the most, sadly. (and such compiler intrinsics aren't permitted in the context I am going for). But good to know anyways.

Still, I wanna do all that stuff myself, for the fun of it.

 

[Sneed's Feed n Seed]

Learning C and ASM before object oriented languages makes me have perma data brain and it makes me want to do things like have everything use something like ECS under the hood.

What's hilarious is a codegen and a better AI can literally just do that. I had claude do that with Opus. C# and Java.

Java: used the motherfucking Guava test suite and... it works. But I'll never get a CTO to fucking try it and fuck being a maintenance dev for this.
C#: didn't need it nearly as much because C# already does shit like Array of Struct etc. Also it has Span<T> etc.

It's still hilarious to me that we throw object references around and pointer chase when we've known cache locality is the most fucking important thing, ever, and MUH INDICES are easily fixed with Handles (with generations). Sigh.

You can even do fucking trees etc with them. Just make another fucking component that has indices for parent/child.

I'm on the fence about open soresing this shit but loldoxing myself for a programming spat on KF.

 

[Rango Dango]

Learning C and ASM before object oriented languages makes me have perma data brain and it makes me want to do things like have everything use something like ECS under the hood.

What's hilarious is a codegen and a better AI can literally just do that. I had claude do that with Opus. C# and Java.

Java: used the motherfucking Guava test suite and... it works. But I'll never get a CTO to fucking try it and fuck being a maintenance dev for this.
C#: didn't need it nearly as much because C# already does shit like Array of Struct etc. Also it has Span<T> etc.

It's still hilarious to me that we throw object references around and pointer chase when we've known cache locality is the most fucking important thing, ever, and MUH INDICES are easily fixed with Handles (with generations). Sigh.

You can even do fucking trees etc with them. Just make another fucking component that has indices for parent/child.

I'm on the fence about open soresing this shit but loldoxing myself for a programming spat on KF.

you can make a new account on gitgud.io and post it there

for extra OPSEC change variable names and naming convention

 

[DavidS877]

Every time I see a rust/javascript/golang/flavor of the week program I'm always impressed that they've managed to use more dependencies than there are packages on my entire system.

Then I go back to my embedded C program, one of which has 2 libraries(4 if you count TinyUSB and LWIP embedded in the Pico SDK). and one which has 5, although I'm not using the I2C one right now.

It is funny as even the AI is confused sometimes, I asked it for some debugging help and it's like: Maybe instead of yielding to the main loop you should just do the sleep here and waste those precious milliseconds while we wait for the 1-Wire bus to respond. I mean I have TWO cores, but I don't want to waste time in sleep() when I might have other tasks piling up. Turns out I never actually tested my 1-Wire code and instead of yielding properly I was entering the main loop repeatedly instead of a proper yield to do one loop of the main loop and return to the 1-Wire timing code.

 

[Rango Dango]

do you guys pronounce i2c as i-two-c or i-squared-c?
i personally say i2c because faster

 

[DavidS877]

do you guys pronounce i2c as i-two-c or i-squared-c?
i personally say i2c because faster

I don't pronounce it as I don't have anyone to talk to.

 

[Rango Dango]

I don't pronounce it as I don't have anyone to talk to.

bro doesnt have internal monologue SAD

 

[Anti Snigger]

Forced to use c99, at the most, sadly. (and such compiler intrinsics aren't permitted in the context I am going for). But good to know anyways.

Newer standard GCC C is a lot of fun, but the portability stuff does hold it back.
I've been using C2Y lately, and I quite like it. The nice thing about C as opposed to C++ is that you can avoid newer features you don't like.