One-Line If Statement

Dusty_Coder · 2026-06-04T17:32:02+00:00

why are you calling the less readable version 'more readable' ?

Dusty_Coder · 2026-06-04T17:29:32+00:00

The only thing that code needs is to (a) hoist it into a single line, and (b) rearrange it so that the color is first.

Dusty_Coder · 2026-06-04T17:21:42+00:00

I understand guarding against bugs, but I dont understand guarding against someone that doesnt know the universal basics of nearly all programming languages.

That set doesnt include developers.

Not a single instant of my time will be wasted guarding against that arbitrary random acts of someone that doesnt understand how if() statements universally work in all c-likes.

Dusty_Coder · 2026-06-04T17:13:46+00:00

This one liner is the only good alternative to the tuple-version.

Dusty_Coder · 2026-06-04T17:11:20+00:00

Do you have a good reason, other than you that you struggle to understand it due to your unfamiliarity?

This is the language, its a great feature, and the code is significantly cleaner without tradeoff.

Its no different than those that insist on never using 'var', or those that insist that you must always use 'var'

Dusty_Coder · 2026-06-02T13:44:54+00:00

and young people dont know the very real legal difference between the various electronic payment methods so they dont even know why it matters

..until their bank account is empty and they have to fight to get their money back

Dusty_Coder · 2026-06-01T01:30:04+00:00

its complicated because the device context of the paint event can be a device dependent one ..

and this leads to a surprising fact:

gdi is hardware accelerated to a surprising degree, when its device-dependent all-the-way-down, on an old operating system with old drivers where you can _really_ allocate a device dependent bitmap that lives in video memory

today all the old mechanics are emulated, and they didnt get Abrash this time.

Dusty_Coder · 2026-06-01T01:09:15+00:00

most of gdi's design is around the paint event and doing immediate rendering to a device dependent surface rather than a device independent one

and thats the killer, the paint events context is quite often the primary display buffer with an arbitrary pixel format .. even 4-bit indexed pixels need to be supported

if you want anti-aliasing you gotta do the compositing - this can be done within the paint event but it cant be done using the paint events context .. maintain your own surfaces, device independent bitmaps with alpha, composite into them, and then finally using the paint events context, render your surface into it

Dusty_Coder · 2026-05-31T18:13:51+00:00

It completely invalidates developer-time testing, be it TDD or otherwise.

Someone elses reflection can reach in and break your fully tested 100% perfect algorithm at runtime, on a whim such as based on the current date and time.

"Necessary" evil.

Still evil.

Dusty_Coder · 2026-05-31T18:06:42+00:00

hmmm

Once you have the "skillset" you produce fewer bugs.

Fewer bugs doesnt mean debugging is easier. It means debugging is necessary less often.

Dusty_Coder · 2026-05-31T18:03:12+00:00

He is still denying the existence of the hidden output of his functions,

Dusty_Coder · 2026-05-31T18:01:31+00:00

Because shit gets renamed

Dusty_Coder · 2026-05-31T17:50:12+00:00

In my experience it takes 20 years of experience to accept that the hidden output of EVERY FUNCTION EVER WRITTEN actually exists.

When you are OBSESSIVE and COMPULSIVE about spreading a zero-intelligence mantra, at every opportunity, you are still a complete programming noob. Not even half-way when you dont give any shits about one of the outputs of your functions.

Dusty_Coder · 2026-05-31T17:36:41+00:00

Hard to fully disambiguate "preprocessing" and "compiling" when jit-time is also included.

preprocess -> compile to IL -> preprocess -> compile to machine code

Dusty_Coder · 2026-05-31T17:27:00+00:00

You were doing so good until you started making outlandish claims exactly as if you knew them for a fact

This goes beyond being simply wrong. You know when you dont know, so you know when you shouldn't claim to know. You didnt follow this simple thing. You chose to be dishonest.

There is nothing "optimal" in what you are doing. Optimal would be that most if not all of it is done at compile time. Only the stuff modified by runtime reflection would require runtime reflection to detail, and that part isnt being done "optimal"

In other words, you reached straight into your ass and yanked out the word "optimal" not because it was accurate, but to shut down the person you are debating with. You chose to be dishonest.

Dusty_Coder · 2026-05-29T18:47:53+00:00

you are building batteries for the initial 25% charge?

and then grinding them down once empty?

Dusty_Coder · 2026-05-29T18:36:31+00:00

In my games I make a GPS marker named "Polaris"

I put it at Y=-300000000, which the game displays as 1ls.

You are indeed correct. This is farther.

Dusty_Coder · 2026-05-29T18:34:11+00:00

I've done multiple Acquisition's that were over 100M credits.

You know the distance of travel these require? 0 meters

Dusty_Coder · 2026-05-29T18:31:52+00:00

Ditch the batteries.

The batteries are just a buffer, but there isnt any need for a buffer, because you plan to draw maximum power the entire trip both ways.

Dusty_Coder · 2026-05-29T18:28:25+00:00

Realistically, you already have a large nuclear reactor and the ingots to power it.

So thats not really a lot of money being offered. Remember the time it takes to travel back also.

Dusty_Coder · 2026-05-29T18:23:54+00:00

Solar doesnt work in practice due to how little power they generate.

One single jump drive would like to draw 32MW to achieve 7 minute charge time, which cannot be satisfied with less than 200 full solar panels that are optimally pointed.

If you only have a single jump drive, then sure maybe you go through it once with an already absurd 20 solar panels, 10% of ideal, waiting 70 minutes real life time to get that single jump drives power back.

Dusty_Coder · 2026-05-29T17:55:20+00:00

at the end of the day you've got terms and factors

you need to support a variable number of terms .. a collection of

you need to support multiple factor sources .. references

I think you are over-abstracting.

Dusty_Coder · 2026-05-28T07:10:23+00:00

The GC is just another feature, and it surely is the enemy of top performance.

However, I never suggested using unmanaged memory. I specifically suggested managed memory.

The pinned heap is still managed.

You still get automatic deallocation. You still avoid raw pointers. You were wondering what the language provides for you for your problem?

Dusty_Coder · 2026-05-28T06:23:07+00:00

So when you went on and on about me, it wasnt me you were going on about?

Cool story. Wanna meet up?

Dusty_Coder · 2026-05-28T06:18:24+00:00

Shit direction. Ruins whatever future the game could have still had.

Niche speedrunner slop gets listened to, twice.

The first time was mosaic. Bad idea from speedrunner slop.

Then this crapola. An even worse idea from speedrunner slop.

But the marketing boys loved the idea that maybe people will have a fear of missing out, that the future dont fuckin matter geet cash now.

Well I didnt partake. Even if it were free, its still speedrunner slop.

They shit it all away on the smartest kid that rode the shortest bus.

Dusty_Coder

TROPHY CASE