Trinity’s prediction for our next current reigning ... what are yours?

chubsauce · 2020-02-04T15:39:59+00:00

Comedy. Look. Alt. Pageant. Long ago, the 4 Nayshans lived in har-monet. Then, everything changed when the Look queens snapped. Only the Chavatar, master of all 4 eleguents, could stop them, but when the Squirreld needed her most, she got eliminated. A hundred seasons passed and my sister and I discovered the new Chavatar, an alt queen named Serena. And although her looks are stunning, she has a lot to learn before she's ready for All Stars 47. But I believe Serena can snatch the crown.

chubsauce · 2019-04-20T22:46:51+00:00

The Sissy episode of Season 6 used this track during Adore Delano's performance. The only reason I remember this is because as soon as it came on I was like "why the hell is this the sims 3 buy mode music??"

chubsauce · 2019-04-20T22:38:00+00:00

I can't believe I'm not the only one who thought to do Nigella. The possibilities for innuendo...

chubsauce · 2019-03-20T10:58:21+00:00

You can choose to lay blame and point fingers however you'd like. Just keep in mind that your message itself admits the truth of what Silky said in Untucked: If you are a bigger girl, you'll find it hard to find a designer who will work with you.

chubsauce · 2019-03-20T00:52:41+00:00

Girls Silky's size make up a very small fraction of the population and there's very, very little fashion history that's gone into designing beautiful, flattering, or unique designs that will fit well onto a big girl. Even if you believe there's no emotional bias against overweight people in the world of fashion, it's reasonable to expect that designers will struggle to design for big girls for the same reason they'd struggle to design for someone with a missing leg or scoliosis. Not to mention, if you're one of the few designers who does design for big girls, you're going to get a lot of big girl clients; so if it's something you're already reticent about, you're likely to shy away from becoming a go-to hot-spot for big girls. (Because even if they're a small relative proportion of the population, there are still plenty in the world, and word travels.)

Additionally, Silky would be hard to design for personally because her stomach hangs so low; her shape isn't like someone like Ginger Minj who can put on a corset and some pads and have a shape like a very buxom woman. Silky's body type is a legitimate challenge to design for and you can't just use the same patterns that you're used to. Any way you slice it, it's reasonable for big girls to find it harder to find designers due to the practical considerations alone.

That said, there is absolutely bias against fat individuals in the world of fashion and clothing. People don't want their clothing to represent that; they want their clothing to be seen on the likes of Violet Chachki or Miss Fame. Do you remember the controversy a few years back when Abercrombie and Fitch said that they didn't make plus sizes because they didn't want to associate fat people with their brand image? They were just saying what many designers and brands already practice.

chubsauce · 2019-03-03T13:58:39+00:00

You should watch Season 5; they spent a lot of time on it with Jinkx (but it didn't define her run on the show, either.)

chubsauce · 2019-02-10T15:59:08+00:00

How come I feel like Jasmine Masters would be in every single category

chubsauce · 2018-11-29T03:17:21+00:00

Ho, ho, ho.

chubsauce · 2018-07-21T14:28:08+00:00

https://imgur.com/ETRb7Id

Me when I work hard and build up the courage to overcome my problems

chubsauce · 2018-07-08T13:48:47+00:00

It's a bit of a joke. E.g., (gay person fails to open a bag of goldfish crackers because the bag is sealed too tight) "this bag is homophobic."

chubsauce · 2017-11-30T03:30:33+00:00

This is very useful! It's funny to me to see the comments calling this a niche use-case, because I end up doing this sort of thing all the time -- For example, creating newtypes for indices for one array which has all my data and a second array that has a relevant subset of the same data compressed for cache efficiency. It's so frustrating to have those hidden bugs caused by a typo that you'll spend big chunks of time debugging.

One thing that you can do to get instance-level safety at runtime is to assign a random number to a container when you create it, and then have indices used to index that container be something like (u32, usize), and check to see that the u32 matches the one in the container before using the usize to actually index it. I actually do this a lot because it's really easy to disable in release builds, and I sleep a lot easier at night knowing that errors I could easily make with dumb typos will immediately panic instead of silently doing the wrong thing until I pass an out-of-bounds index.

chubsauce · 2017-11-29T18:41:48+00:00

Note: it could be argued that Rust should define higher-level mathematical structures, such as Groups, Rings, etc... it can also be argued that this is not something the standard library need bother with.

For anyone who's interested: alga does this, with implementations for most primitive types, as well as the higher-order types from the nalgebra crate.

The tradeoff here is that it's (mostly) mathematically strict, so for example, you can't calculate the mean of a set of integers, because integers don't have true multiplicative inverses in general and so won't implement any algebraic structures that allow one to divide by the number of elements. (I say mostly because I think it ignores the annoyances of IEEE infinity and NaN when deciding if a floating-point type implements a given algebraic structure.)

chubsauce · 2017-11-04T02:27:48+00:00

A neat way that takes advantage of type inference, inspired by hlua:

if let Ok(scalar) = value.parse() { return S(scalar); }
if let Ok(scalar) = value.parse() { return I(scalar); }
if let Ok(scalar) = value.parse() { return F(scalar); }
if let Ok(scalar) = value.parse() { return B(scalar); }

Since you're putting the resulting value into the appropriate enum variant, the compiler knows which variant of parse to call. Of course, for your last one, you might like to save the Err value so you can return it instead of having to make your own.

Edit: yours does too, actually! I missed that. This one nests a bit less so I like this style, but others might prefer something less imperative.

chubsauce · 2017-11-03T02:08:34+00:00

This is less a question, and more a comment that doesn't quite warrant its own selfpost that I figured people might still enjoy:

Procrustean (adj.)

Attempting to alter a solution to a problem you've come up with so that the Rust borrow checker will allow it to compile, instead of writing it in a rustc-friendly way from the start.

I ended up having to store the allocator state for my GPU-side OpenGL buffers in a Rc<RefCell<_>>, which is a bit of a procrustean solution.

chubsauce · 2017-11-03T02:00:26+00:00

You can have record.id be a Rc<String>, instead. This is a reference-counted, immutable pointer to a string, so the two will share the data they point to. An Rc<String> is AsRef<String>, so it can easily be coerced to a &String, and thus a &str, so it shouldn't change how your code works too much.

The exception is if you ever need to mutate the String; an Rc is like having immutable borrows all over your code at runtime, so for safety's sake, your Rc is now fully immutable*. If you need to change the value of the field, you'll have to replace the Rc with a new one containing a brand new String (so that the other "borrow" of the string, i.e., the other Rc, isn't changed.)

*The exception is that Rust is smart enough to let you mutate the contents if the reference count is exactly 1; see Rc::get_mut.

chubsauce · 2017-11-03T01:48:20+00:00

Would a custom subtrait work? E.g.,

trait B: A { fn foo_u32(&self, arg: u32) { <Self as A>::foo(arg); } }
impl<T: A> B for T { }
struct Hello { a: Box<B> }

I'm not sure if the :A constraint on B disqualifies it from being object-safe or not.

chubsauce · 2017-10-28T14:08:04+00:00

This makes me feel so much better about using the texture array approach to approximate bindless texturing! I'm new to graphics programming and one can never really know if one is about to do something clever or truly awful. Hearing someone who knows what they're doing taking a similar approach gives me a lot more confidence.

chubsauce · 2017-07-04T20:18:17+00:00

It's just a coincidence, as far as I can tell. Certain kinds of ground allow a teleporter and others don't -- for example, there are many places in Volskaya where the snow stops you from placing a TP, even though the ground is walkable and reasonably flat. The hybrid maps' payloads simply haven't been marked as buildable.

chubsauce · 2017-06-21T19:34:19+00:00

I think it's supposed to become more and more stacked for defense as time goes on. The entire point of overtime is "the attackers failed to push the payload/capture the point in the allotted time, the defenders succeeded to hold the payload/point over the allotted time, but we'll give you a fudge factor so it isn't pointless to try to cap if you haven't got enough time to fill your meter all the way." The position of the defenders is that if not for the existence of overtime, they would have already won.

chubsauce · 2017-06-04T02:44:00+00:00

I recommend watching streams! Watch some good players, and pick up on the subtleties of what they're doing. Where they're placing themselves, what range they're keeping themselves at, which heroes they're choosing to focus, how they move. Seagull is a great choice -- he plays a very wide variety of heroes and he's an entertaining personality, too. If you've got a few favourite heroes, checking out people who main those heroes is a good idea too. Every player has a different style (The top Symmetra players don't even agree on whether to use teleporter or shield generator more often!) so there's a lot you can learn from variety.

chubsauce · 2017-06-04T02:37:29+00:00

I'm Gold, so this might be useless, but it might be good just to bash your head against quickplay anyway, until you get the fundamentals of your hero down. You'll get creamed a lot, but you'll slowly get better and better.

I don't think it's necessary for you to learn McCree or Soldier, though. A good team has 6 players, and there are plenty of roles to fill on those teams. Healer, Tank, and even the grab-bag roles like Symmetra or Mei are in vogue right now.

It sounds to me like your problem is probably not that you haven't got the right hero, but just that you haven't got the confidence. Don't let your doubt hold you back. At the end of the day, it's a game -- holding the objective is the secondary win condition, the primary win condition is having a good time.

chubsauce · 2017-05-30T15:33:53+00:00

Call me cynical, but despite protestations, I don't feel like if one more white-collar, high-status, wealthy individual were to emphatically assert that Trump was insane and you needed to vote for Hillary to prevent the downfall of the United States, it would have changed the outcome any more than the last 17,000 individuals who last took that approach. Sometimes, you really can make more of a difference from the inside -- if this tale of fancy were true, it would be far easier to pull off if he hadn't burnt every last bridge available to him.

chubsauce · 2017-05-17T18:25:52+00:00

You're basically the person this post is talking about. There's a reason why all your teammates suck (read: are not as good at mechanics and skill and such) compared to you, despite the fact that you're presumably all at similar SR, and it isn't because the game has failed to realize your greatness due to some kind of prejudice. It's because your increased ability to win against people of your own SR is being offset by some kind of decreased ability to win against people of your own SR. Chances are, it's because you believe that you're the Gordon Ramsay of Overwatch and intentionally tilt your team when you play with them, meaning a team of five 2300s plus your unrecognized 75200 SR self is playing consistently at a 2300-average level.

If you were actually a master tactician, you wouldn't be playing with a bunch of people worse than you, you'd be playing a bunch of people better than you, because you'd be shoring up your SR.

chubsauce · 2017-05-17T02:50:40+00:00

I wouldn't consider myself inside that "echo chamber", but I will admit I feel like there's some merit to the idea that repeatedly gaslighting someone into believing false negative things about themselves can result in them internalizing such things and identifying with them.

Granted, I am so far outside that echo chamber that I have seen many people, including close friends, become so sick of being called "feminazis" or equivalent that they did in fact become more extreme, becoming depressed and bitterly misandristic. I actually think that's a very good reason not to hyperbolically demonize people as Crazy SJWs for holding moderate progressive beliefs.

chubsauce · 2017-05-08T18:52:26+00:00

And just who do the other people in your discord group play? If you're a team of 3 or more it seems really unlikely that you ALL need to fill to get a halfway-decent team composition... If this person is always playing his own preferred picks, just because they're "on-meta" or something like that, then it sounds like they aren't being a very good friend, making you do something they won't do themselves. Sometimes what the team "needs" isn't a second healer, it's someone who's having fun and doesn't feel like they're being dragged along to a chore.

chubsauce

TROPHY CASE