anotherusername
@anotherusername
Best posts made by anotherusername
-
RE: WTF Bites
@sloosecannon said in WTF Bites:
The best part of that is that it's remarkably easy to detect binary files. Like, just look for
NUL
s in the file, you'll get 99% of them! Then it doesn't matter how it's configured.I have a better way. Is it stored on a binary-based storage device? Yes? It's a binary file. There is literally no justification, ever, for modifying the contents of a file, because you ass-umpted that it was an ASCII file and it contained characters that you thought ASCII files shouldn't have. Unless you created the file, you don't know shit about it. Every file is a binary file. Done.
Latest posts made by anotherusername
-
RE: OOP is TRWTF
@TimeBandit One time in particular was right after I accidentally spilled something in the oven.
-
RE: OOP is TRWTF
@M_Adams said in OOP is TRWTF:
@dkf said in OOP is TRWTF:
@HardwareGeek said in OOP is TRWTF:
Not unless you use too much chili in the curry.
You know it is too much when the neighbours complain to the cops about the manufacture of what they believe is pepper spray…
I can’t find it credible that @anotherusername hasn't had this happen yet.
They definitely weren't standing right outside my window that one or two times when I had to air out the kitchen...
-
RE: In other news today...
@JBert You get used to it. I don't even feel the pain; all I feel is breakfast, lunch, dinner...
-
RE: In other news today...
@Cursorkeys said in In other news today...:
@mott555 said in In other news today...:
@Dragoon But does eating spicy food cause dementia, or is it a result of dementia? Because either my Carolina Reaper powder is harming my brain, or it's already too late for me.
It definitely causes it. A few weeks ago I made Reaper dry rub that gave me stomach cramps, on Sunday I made dry rub chicken with the same amount again (I'll have tolerance now!) ...I was up most of the night with stomach cramps again
Don't worry; you'll get there eventually.
-
RE: The Cooking Thread
@HardwareGeek I still had the munchies, so I warmed up some nacho cheese and added 2 tsp of reaper powder and ate it with some tortilla chips.
edit: For the record, that much reaper in one meal-ish snack was a little bit farther than the extent of my current comfort zone.
-
RE: The Cooking Thread
@Cursorkeys said in The Cooking Thread:
The Carolina Reaper was a little clumpy, so I tried to mortar and pestle it. That was a bad idea, I've just stopped sneezing.
Just pouring the kg bag that I bought to transfer it into the spice shakers has a similar effect. I've basically just accepted it.
Tonight, I made spicy beef and mushroom stroganoff.
1 lb ground beef, an onion, about 24 oz sliced mushrooms, 4 cloves garlic, 1 tsp paprika, 2 tsp yellow mustard, half a cup of white wine, 2 cups beef broth, 2 Tbsp flour, 1 Tbsp worcestershire. About 4 teaspoons of Carolina Reaper pepper powder. A cup of sour cream. 16 oz of cooked egg noodles.
My head is sweating and my face feels hot, but I think I could've made it hotter. Maybe I'll add a bit more reaper when I have the leftovers.
-
RE: Notification tooltip script breaks after using the site for a while
@hungrier I wrote a function that triggers that error by trying to access
this
internally, but interestingly it only generates that specific error message in Chrome, and only for certain types of code.In addition to
delete
, I've found that callingObject.keys
with an undefined argument can also produce that error in Chrome, at least in certain situations. -
RE: Notification tooltip script breaks after using the site for a while
@hungrier Alright, then I think maybe I know what's happening. Somewhere internally, those functions are trying to use
this
, and they're expecting it to be thewindow
object. They're methods of thewindow
object, but they're not bound to it if you call them stand-alone (even thoughwindow
is global and you can refer to any of its properties or methods globally).I would argue that they should really still work, or at the very least this behavior should be consistent. It appears to be in the browser's native code, so I'd call it a bug in Chrome.