The Official Status Thread
-
What the hell is up with images and Discourse lately?
Edit: there, uploaded, should work now... I hope?
-
It will be Avery tonight, so it should be fun.
-
status: chrome just crashed the discourse tab.... the memory leak's getting worse. it usually made it the whole day before, that was only about 5 hours...
-
It wasn't Discourse, it was probably my work filter.
Crystal Pepsi is definitely clear. No caffeine, nothing to make it a cola.
It might as well have been 7up.
-
What the hell is up with images and Discourse lately?
What's funny (to me) is it worked for me.
-
status: chrome just crashed the discourse tab.
I guess I shouldn't point out that I left Discourse open at work overnight, and all I had this morning was a toaster that I should refresh.
i was using IE, though, so maybe that's why it didn't crash. :)
-
What's funny (to me) is it worked for me.
It wasn't Discourse, it was probably my work filter.
empty
-
Yeah, for me, after 3 hours, it's up to ~1.5GB.
Leak is probably not the right term for how much memory it is using.
-
i was using IE, though, so maybe that's why it didn't crash. :)
if the memory leak is browser dependent i'm going to be pissed.
-
if the memory leak is browser dependent i'm going to be pissed.
The machine may or may not have been asleep over night. Probably not, though.
-
I leave 2 Dicsores tabs open in Chrome (38.0, Win 7) on my laptop constantly. It uses a lot of memory, eventually (currently <200MB, and I've had it open for something like 2 days), but nothing that causes problems. If it does have problems, it's usually because some other Chrome window is making Chrome incontinent (I'm looking at you, YouTube).
-
Status: after a business update. 30 minutes of listening about how your company makes millions of dollars, funds charity events, does team dinners, et al.
And back to getting $5 per hour.
-
Where's your AA.
I can't complain, at least you got specular working correctly :/
-
status: chrome just crashed the discourse tab.... the memory leak's getting worse. it usually made it the whole day before, that was only about 5 hours...
Yikes. I just noticed my tab is up to 1.4GB (discorounded). Time to start a new one, I guess.
-
New tab is 120MB (discorounded).
-
Where's your AA.
Well, that would explain a lot of @ben_lubar's posts... Also his fondness for Go.
-
The AA is done by sampling each pixel multiple times at slightly different positions, just like every other ray tracer ever.
-
Current status: regretting the chili cheese fries that I had with lunch.
-
Current status:
-
installing..... what?
status: surrounded by plague carriers, also known as middleschoolers
-
-
I already...wait, where's my reply? ... oh, he posted this picture in another thread, too.
Shakes cane at Ben You kids get off my lawn!
-
You've been Sergio'd!
-
Is that a thing now? Have we added that to the FAQ?
-
I just made it up.......so it can be, but not yet.
-
Is that a thing now? Have we added that to the
FAQDiscopædia?FTFY
Filed Under: Do you know where your data's been?
-
Current status:
When I create new software, there is a stage where stuff is functional enough where it looks ok, but it can corrupt data, not fully work, etc.
With the new help desk software system, which IS IN PRODUCTION, I don't even know how it even got to that state. It's not partially-working. I updated a ticket, and it brought me to an unrelated record of an unrelated type. I don't even know how that's possible.
-
I don't even know how that's possible.
It's not. You must be hallucinating. The orderly will be along shortly with your
ClozapineClonazepam. (Sorry, had to throw in a TWD reference.)
-
Never seen that show.
-
-
Maybe it was the video's tiny aspect but it didn't look very smooth to me. :(
-
Status: Going through the whole project to replace
printf
s and friends with calls to a custom logger (which really is a thin wrapper aroundsyslog(2)
).
It gives me the opportunity to fix broken error handling code. I‘ve already found dozens of calls topthread_create
, and they all useerrno
to report the error
Filed under: Unable to create thread: Success
-
Yes, that does say 17.22% ABV.
-
-
Pretty much tasted like it.
-
Yes, that does say 17.22% ABV.
Bourbon barrel-aged pumpkin porter, spiced with nutmeg, cinnamon, allspice, and cloves, and aged in fresh Bourbon barrels for 6 months.
I think they forgot to take the bourbon out before the aging.
-
They should have just called it "Everything but the kitchen sink" because they put everything they could in it.
-
Status: tech interview where the interviewer didn't know the difference between "char" and "byte" in C#. (Specifically, he had leftover C++ information that they were the same thing.)
So I had to go into a little hopefully extremely polite discussion as to how it's not a great idea in a strongly-typed language to compare a character type to an integer type (even if by some quirk of the language it's technically possible to do.)
I actually looked this up:
A char can be implicitly converted to ushort, int, uint, long, ulong, float, double, or decimal.
Hey C#, I love ya buddy, but you shouldn't be implicitly converting character types to ints and confusing the bejeesus out of iffy programmers.
I think I did well though.
-
-
Believe it or not, the company I'm actually applying to hires a third-party consultant to do their tech screening.
I'm actually more worried he'll get uppity ("that interviewer acted like he knew more than ME!") and make a bad recommendation based on that. I've lost potential jobs in the past due to that.
-
Sounds like you screened that company out of contention.
no offense intended dude, but i think @chubertdev said it best.
-
Status: tech interview where the interviewer didn't know the difference between "char" and "byte" in C#. (Specifically, he had leftover C++ information that they were the same thing.)
Yeah, isn't C#
char
the same as C++char16_t
, or do they actually pull off a variable-width character type in the .NET world these days?Sidenote: I wonder what'd happen if you ported the CLR to a machine where
CHAR_BIT == 8
was false (i.e. there is no native octet type). Would you wind up with abyte
with padding bits in it?So I had to go into a little hopefully extremely polite discussion as to how it's not a great idea in a strongly-typed language to compare a character type to an integer type (even if by some quirk of the language it's technically possible to do.)
Yeah, never mind what'd happen if somehow, your char got the first half of a surrogate pair slipped in -- going off the BMP is a fantastic way to trip up dumb Java/C# programmers who assume "1 char = 1 character". Never mind all the other fun you can have with Unicode ;)Hey C#, I love ya buddy, but you shouldn't be implicitly converting character types to ints and confusing the bejeesus out of iffy programmers.
Agreed for the most part -- the notion of an atomic character type is a bit of an aberration in Unicode-land, even, and should not exist to begin with. Better to follow in Python's footsteps and make 1-character strings, well, strings -- it causes far fewer surprises that way.
-
A string is just a char array, anyways...
-
Yeah, isn't C# char the same as C++ char16_t, or do they actually pull off a variable-width character type in the .NET world these days?
Looks like it:
The char keyword is used to declare an instance of the System.Char structure that the .NET Framework uses to represent a Unicode character. The value of a Char object is a 16-bit numeric (ordinal) value.
-
Easy enough to use.
char test = "9"c;
-
The value of a Char object is a 16-bit numeric (ordinal) value.
See that strikes me as bad design. C# is strongly typed. The fact that each UTF-16 character has a integer representation is implementation detail (and "accident of history") that shouldn't be exposed to the programmer in a strongly-typed environment.
-
But a lot of people made the same mistake at the same time. It worked for a while even, but then the Unicode consortium decided that 64k characters was not enough for everything. Blame
CanadaUnicode!It'd be better if the C# (and Java) language designers just said “a
char
holds a character” but the meaning of that is really slippery, and they'd break tons of existing code in all likelihood. I can totally understand not wanting to force through a massive breakage to vast amounts of code when current actual use of non-BMP Unicode characters is rare and can be serviced with UTF-16 on the few occasions it is really needed (except for some self-contained subsystems, such as the font renderer).
-
See that strikes me as bad design. C# is strongly typed. The fact that each UTF-16 character has a integer representation is implementation detail (and "accident of history") that shouldn't be exposed to the programmer in a strongly-typed environment.
I'm in your boat already -- is there anything wrong with deprecating
char
in favor of a one-character string?It'd be better if the C# (and Java) language designers just said “a char holds a character” but the meaning of that is really slippery, and they'd break tons of existing code in all likelihood. I can totally understand not wanting to force through a massive breakage to vast amounts of code when current actual use of non-BMP Unicode characters is rare and can be serviced with UTF-16 on the few occasions it is really needed (except for some self-contained subsystems, such as the font renderer).
The best part about the "use a one-character string instead ofchar
" approach is that imposing it breaks far less code -- mainly code that actually deals with the numeric values of codepoints. ;)
-
Current Status: High winds + trash day = my round, garage trash can is MIA. It is probably a county or two over by now.
-
I'm in your boat already -- is there anything wrong with deprecating char in favor of a one-character string?
But how would you do that? In C#, string is the same as char[]. It would take a major re-write to make that kind of change.