171 karma · joined January 12, 2012
i.e. nobody, but nobody says their favorite language is C anymore, they've all found languages that have trade-offs, and most people don't need the trade-offs C can provide. Parsing XML? Un-fun. Regular expressions? Un-fun. GUIs? Un-fun. Hierarchical subclasses of actors? Un-fun.
Some problems can scale out, but only if latency between nodes is low enough and bandwidth is high enough. For example, an MMO server would not function as well if there was a 50 msec ping between nodes. You may or may not have control over that depending on what cloud service you use.
These are real concerns and should not be trivialized as "BS for BS" or "throw more virtualized CPU cores at it". Every problem is different; it should be studied and the best solution for the problem applied.
EDIT: I would also like to add that only in the strictest and most painful sense was the legacy OpenGL "just an abstraction". Before, it was a simplistic cross-platform layer over actual hardware and while abstract to a degree, hardly attempted to shield the programmer from hardware details. It's notable that the features that OpenGL "happened" to include as the "core abstract GL state machine" mapped pretty much 1-to-1 onto SGI's tiered hardware offerings at the time. In other words, what made the cut was very much based on real hardware, hence, the evolution of the API was not based on random abstractions that seemed like a good design [cough]. The legacy-GL-on-modern-hardware -- we refer to it as "fixed function emulation", since the abstraction is so far removed from actual hardware nowadays. Perhaps this isn't a "good reason" to change the abstraction, but it is notable that if the entire legacy API can be emulated using the newer API, then the legacy API may not deserve to be part of the driver (which takes a lot of time and effort to develop) so much as another library. That is to say, if one were to change it into terms of "computability", there are some things that cannot be computed using the FF, but the reverse is not true, i.e. FF can compute a proper subset of the programmable pipeline. In fact, this is pretty much the exact idea that Gallium takes in Mesa -- and why you can implement D3D / GL ES / core GL / legacy GL on top of it.
Now, on to the real issue that I raised, which is a purely API design choice. Direct state access vs bind-modify-unbind. The consequences of bind-modify-unbind have been lamented by developers for _ages_. As a response, the newer GL sampler objects do not use that. However, the old style API (you know, the thing we've been lamenting over for ages) does not have a modern equivalent. Please tell me how this has ANYTHING to do with GPUs? It's pure and simple API cruft. The API is _not_ consistent with itself.
The GL 3.3 samplers, e.g., are great. It does not require you to bind a sampler object in order to change the properties of it. However, the rest of the GL objects follow bind-change-unbind and a lot of implicit state which makes writing OpenGL libraries that can be reused highly weird because you never know what state some moron left the GL machine in.
Now GL 3.3+ is in an interesting position. They've got old functions that operate in a specific bind-change-unbind and new function that operate directly. So not only has the API not yet been fully "modernized", it's in the halfway state and it looks like it won't be pushed in one direction or the other -- just stuck in limbo for something like 3-4 revisions.
So I guess what I'm saying is, until the inconsistencies are ironed out, OpenGL still has some cruft that directly affects even the most modern GL 4.x programs.
In short, I'm saying "Help me understand what the right thing to do now. I can't undo history." I hear far too much debate about guilt assignment and not enough about practical advise.
I'd like to think that selfless and concrete action is also patriotic. Is that not the case? If not then... well.. I'm not terribly skilled with weapons, not that strong, not that athletic, and my eyesight is kind of meh -- I'm not sure I can be that kind of patriot.
That having been said ... What is expected of me? How should I act? How should I feel?
When people get angry about this subject, I understand their feelings and I don't think for a minute that everyone was born with equal opportunity -- but, should I be throwing money at people? Should I give up my life dreams to go even the odds? I'm not sure what the expected response is? Is it enough if I hang my head at my ancestors, pay my taxes, and do my best to not sound entitled? I'm quite serious, because for all of the complaining about how good people like me have it, I never hear a series of actions that makes my life "acceptable" instead of "something that just causes seething rage in people when they think about it."
EDIT: I guess what I'm saying is, I don't understand what the appropriate response is when someone says, "You don't own slaves but that doesn't mean you didn't get the benefits from it!". Is the answer "yes", "no", "I see", "I'm sorry"?
Suppose I had GL 4.3 capable hardware.
Closed Source Drivers on Windows = OpenGL 4.3
Closed Source Drivers on Linux = OpenGL 4.3
Open Source Drivers on Linux = OpenGL 3.1 [best case]
Closed Source Drivers on MacOS = OpenGL 3.2
My Game Engine Requires = OpenGL 3.3
---
As you can imagine, that means:
If you're running Linux on open source -> no
If you're running Mac at all -> no
In fact, what is ironic is the ONLY systems in the ENTIRE PLANET that can run this game are ones using proprietary drivers, specifically Windows and *NIX (but not MacOS)
Men and women have unwanted sex all the time. They do it because they don't want to let their partner down, because they think it is their "job", because they want to get something, because they are bored, because they want to feel wanted, because they just want to feel loved, because they haven't in a long time, etc. -- not always the best reasons. Typically, those feelings can be resolved in other ways.
We, as lovers, should strive to reduce the number of unwanted sex events as possible, and to do so requires an open bidirectional communication channel. However, while it may be sad that women are more prone to agreeing to unwanted sex, this is not the same thing as //raping// someone. I think it's really important to make the difference, because for one we say that the relationship is a bit off, in the other, we lock a person up and mark them for life.
No, you didn't say "We don't have hot sex". I didn't say "You don't have hot sex" either. Now that you're feeling validated, please consider what was written again, but without getting offended.
You stated what worked for you, and you measured its "workingness" by unambiguousness of the process, the lack of bad feelings on rejection, and (ostensibly most importantly, seeing as how you put it in italics) the quantity. I'm happy for you.
But what if what you are suggesting can come by following your advice //is not what I value//? What if I can achieve what is optimal for my relationship in a different way? What if, and this is crazy but, what if what works for you and what is best for you, isn't best for everyone? -> False consens effect.
I was remarking that I find it interesting that you're defending a particular strategy that works in your relationship and is not a cultural norm (hence, atypical), while at the same time suggesting that all men should act more like you. Too fast there cowboy! If all men woke up tomorrow and acted like that, there might be a few (million?) women who find their choice of mates underwhelming all of a sudden. Why? Because it violates our cultural norms. But at the level of one couple, you and your partner, sure, you have the luxury of making such "optimizations" and being "absolute" about what is best.
There is no need to defend yourself, your sex life, or your relationship. I'm sure you're in a great one; may you two be together forever. Communication is great and key. However, please consider as well that I am not going to follow your advice, and that I, too, am delusional about how awesome my relationship is compared to everyone else's. :) :) :)
In summary, let's keep rape as a reserved term for obvious and gratuitous violations. This "accidentally raped" is kind of stupid.
EDIT: which is to say, it's not wrong that this works for you, this isn't a criticism of that. I think you may be mistaking a local optimum for a global [in the sense of math - so the country/dating pool] optimum because it works so well for you; i.e. the false-consensus effect.
Also, I don't value "having way more sex" over "having extremely hot sex", but this is also just me.
Your advice would not work in my relationship. In fact, it is decidedly unhot to ask a "yes/no" question and I would probably get rolled eyes. It would still work and bluntly convey my intentions, but it would come off as completely un-suave. For us, the language of the body is far more rich, intimate, and revealing to one's true desires. In fact, rarely when we have sex does it start with both parties reaching the same conclusion at the same time. Sometimes, something as simple as a good-bye kiss can turn into a 20-minute delay -- and I wouldn't have it any other way.
1) The legal definition of rape (at least in most states?) makes it such that one cannot "accidentally" do it.
Keywords: "[by means of] force", "duress", "physical resistance", "objected verbally".
A woman who was: * Not forced * Had no duress * Not physically resisting * Not verbally objecting * Mentally capable of making decisions
...is considered to be consenting. In other words, and perhaps contrary to the way you believe it should be, THE LAW REQUIRES YOU TO EXPRESS YOUR DISCOMFORT OR ELSE THERE IS NO PLAUSIBLE WAY THE OTHER PERSON COULD KNOW. Sorry. :(
If a person has sex but later decides they weren't really that into their partner, wished that they didn't, wished that they had stopped it earlier -- it's not rape. Regret and the discomfort / dissonance that comes from it is a far cry from traumatic, forced rape.
2) You know long before you were "accidentally raping" someone whether or not they were consenting.
So yeah, if your goal is play it safe for fear of lawsuits, offense, or rejections, then by all means, do not initiate any physical contact. Expect to be forgettable and for people to tell you "they just didn't feel that spark."
This is the problem with your argument. I'll admit it, I don't explicitly "ask consent" and there have been times where there was "no doubt in my mind", and yet, I was rejected. :(
But if I was rejected, then I've clearly committed sexual assault in the most strict sense.
It's called "misreading a situation". You may think something is enthusiastic consent, but it isn't. Hence, why I will continue to ignore your advice and "live dangerously" by attempting to interpret the situation and predict the other partner's desires by other subjective and unreliable means such as body language and the nebulous concept of "where we are in our relationship".