Yeah, I guess the CORS problem would have been fixed by now (by feeding CORS examples codes of course) by at least the dev targetted brands.

giraffe of course :P

Hmm. Well, I guess they are not using the Qt Widgets TableView then.
Perhaps I’ll take a look too, next time I feel like.

Oof that’s a lot of reports. And even a survey

It took me seeing it free a mosquito from its web…

I thought a ‘+’ sign was doubly symmetric.

Maybe their god wanted some peace and quite and thought that if they were to annihilate each other, that might lead to fulfilling the requirement.

Hehe, that was an unintentional Nokia reference on my side.

I don’t really remember enough about Excel anymore, but considering that I don’t remember having that problem despite how many years I used it, I guess that is the case with it.

And yes, a toggle would be nice. In fact, a few months ago, I was thinking of putting up a request over to the LibreOffice team, when I was working on the table view of another OSS project, but then procrastinated until I forgot. Honestly, if there are enough people that have a problem with this little thingy, it’d be better off fixed. Specially in the Qt implementation at least, it really is just a boolean toggle even for the developer.

Would you like to put up a bug report to them?

So, “jod” is hilarious, but “jift” is disingenuous?
I don’t get it, but I guess it’s fine.

Also, I was trying to go by the fact that “gift” has the same 2 letters after the ‘g’ as “gif”, which tends to be an often stated thing when people try to make a semblance of logic^[1], explaining why something is pronounced the way it is, in English (and then also used in comedies, where all of that logic fails due to exceptions everywhere).

For pronunciation in the English language, I consider that there is often not a logic behind it, but a history. And from that POV, “jif” would be the correct one (∵ the creators). But I still pronounce it “gif”, because:

• it’s an acronym, so I consider the pronunciation to not be very important and it is better to go with what clicks in my mind faster ^[2]
• I first read .gif in a file name and there was noone to tell me how it was pronounced. I went with G.I.F. until I felt like calling it “gif” with the logic of “gift”. Then again, I heard quite a few people call it “gif” and it set in.

are simply unfit

are simply not America.

one of the principle three programmer foods

American consumer foods

Yeah, “human spider” wouldn’t have caught up well either.

Give it a few days and people will be pronouncing it yod.

So, no jifts from above?

For some reason, very few people seem to care about this.
An even though I do care, I don’t do so enough to try and undo my bad pronunciation.

I did the same for a while.
But then I recently found out a spider (which was getting pretty big) ignoring bloodless mosquitoes and letting them fill up on me before eating them. I cleaned it up.

3310 Atomic Deer

Well guess what?

#include <string.h>
#include <iostream>

int main (int argc, char *argv[])
{
	const int which = strcmp ("zsh", "bash");
	std::cout << which << std::endl;
	return 0;
}

Output
1

There recently was a project that did UEFI on a phone.
Perhaps we can consider doing so with all ARM and RISC V stuff?
Or maybe come up with another common interface more suited to the platform?

Considering Qualcomm went and 1TKO’d Arduino, I’d say we are better off not waiting for it to get onboard.

What happened to your eyes?

So I don’t find coding challenge sites/events fun, but a few years ago, I thought it might be nice to try out ChatGPT on it.
Although I exited after the first question itself, I did get to evaluate ChatGPT at the point (3, I suppose).

I simply pasted the whole question into ChatGPT and it spewed out code which was a pretty good match for what was required.
But no matter how many types of prompts I tried (even giving the solution logic to the part that was wrong), that specific part of the output was always wrong.

On the other hand, when I manually corrected the C code and gave it to convert to C++, it ended up working on the first try (I didn’t even read that output).
I then tried converting the correct code to Rust and I don’t remember what I did with the output, but it surely didn’t pass the assessment.