On rereading Martin's email, he did not write what I thought he wrote. His meaning probably was "you may not like the truth, but I'll still say it" rather than "(unlike you) I'll speak the truth because I am German", which was how I parsed it.
My apologies.
Having been on the receiving and the giving end of non-backwards compatible places, I can share the pain of Martin. Sometimes, there's simply no good solution: should you improve your implementation even though that might break existing programs? Or do you keep reporting invalid information because some application may have come to rely on it, even though you've explicitly written that this info shouldn't be relied upon? And if you go the second route, for how long?
It's all about tradeoffs. Those who have used the winapi should know the cost of backwards compatibility - much of the madness there is the result of support for win3.11-era applications.
And those who have programmed for MacOS/MacOSX should know the cost of evolving APIs: "what do you mean Carbon is deprecated in favor of Quartz? Am I supposed to rewrite a few million lines of code just because you say so?" (That's what, say, Photoshop had to go through).
Announcement
Collapse
No announcement yet.
Intel Mesa Gives Problems With KDE's KWin, Again
Collapse
X
-
Originally posted by Henri View Post[...]
As a reply to this thread as a whole (or perhaps this site in general...), please do some research, check facts, etc. before repeating things you read on some random part of the internet. The person you're repeating may not necessarily know what he's talking about either, and the consequences may not necessarily just be harmless flamewars.
I read his mail, though when replying here I had forgotten the exact way he wrote it and so did not spote the wrong quote.
Leave a comment:
-
Originally posted by Henri View PostTo me it seems obvious that Martin's intent was to express that as a person he values expressing his opinion / making issues he's running into known over avoiding potentially offending other people. I suppose you can argue about what the best way to express that is, but I don't think that's a very useful discussion by itself.
Leave a comment:
-
Originally posted by yotambien View PostI don't think the distinction between what refers to the character of the
author and what refers to some feature suposedly shared among Germans is
that neat. Was he really making a completely random, unrelated statement
about Germans, only to carry on with whatever he had in mind immediately
after? Like, you know spanish woman have moustache and I like Phoronix
forums? I don't think so. Actually, I had read those sentences in the
same way Blackstar had before he (inaccurately) quoted them in the forum.
Originally posted by yotambien View PostAnyway, my partner is an expert on racism questions. She tells me
it would be a stretch to consider that a racist remark. Not because
some prejudice about Asians and Europeans is common place, or
because some cultural differences as was suggested before, but because
Originally posted by yotambien View Postopposed to Turks, and a positive value were assigned to directness (which
normally is) we could start talking about something. Since I won't find a
I think your partner's opinion is close enough to my own that I'd agree with her. I'd argue for "it clearly isn't" over "you can't really tell", but my main point would be that things like context and intent matter. Taking a quote out of context and mangling it like that is unfair, IMO.
Leave a comment:
-
Originally posted by HenriCouple of points:
- "I speak the truth even if it hurts." is quite a different statement
from "Germans speak the truth."
- Even then, it should be pretty obvious from the context that it's a
statement about Martin's own personal character and values, rather than
some kind of statement of German superiority.
- Perhaps you take issue with "You know we Germans are direct". It's of
course a huge generalization, but I do think it's commonly accepted that
for example western Europe tends to favor a somewhat more direct approach
in communication compared to for example eastern Asia. At worst the
statement is simply wrong, but I'd hardly call it racism in any
case.
I don't think the distinction between what refers to the character of the
author and what refers to some feature suposedly shared among Germans is
that neat. Was he really making a completely random, unrelated statement
about Germans, only to carry on with whatever he had in mind immediately
after? Like, you know spanish woman have moustache and I like Phoronix
forums? I don't think so. Actually, I had read those sentences in the
same way Blackstar had before he (inaccurately) quoted them in the forum.
Anyway, my partner is an expert on racism questions. She tells me
it would be a stretch to consider that a racist remark. Not because
some prejudice about Asians and Europeans is common place, or
because some cultural differences as was suggested before, but because
there is not enough material to know what the position of the author
really is. If he had made explicit, for instance, that Germans are direct
in constrast to, say, French, that would be OK because there isn't an
asymmetric power relation between those peoples. If Germans were direct as
opposed to Turks, and a positive value were assigned to directness (which
normally is) we could start talking about something. Since I won't find a
more informed opinion than hers on the whole internet, I retract my
comment about those words.
Leave a comment:
-
Originally posted by bridgman View PostI was under the impression that ARB_texture_rectangle was supposed to provide an extension which better matched hardware capabilities, although AFAIK it doesn't use normalized coordinates. Am I close ?
Leave a comment:
-
Originally posted by Henri View PostYeah. Though in the specific example you mention, I think everyone would have been much happier if ATI at the time had just created some kind of "conditional NPOT" or "normalized texrect" extension.
Leave a comment:
-
Originally posted by bridgman View PostMost of the missing features are pretty subtle, eg certain texture options aren't available with Non Power Of Two textures. Some can be worked around but the workarounds usually have a cost in terms of performance or ability to run the largest shaders so on balance it's usually better to only implement what the hardware can directly support -- but this leads to developers being accused of "lying and saying something is implemented when it is not".
The key point is that the decision about exposing specific bits of OpenGL support is rarely as simple as people think, not only during initial development (which was how this issue blew up in the first place) but even after support has matured.
Leave a comment:
-
Originally posted by monraaf View PostAnd KWin people, well they mostly rant
If a large distribution paid one of them to work on it full-time (like they do with Gnome-Shell and Mesa drivers), I'm sure that the results would be very different.
Leave a comment:
-
Originally posted by yotambien View PostOoooh, that's extremely interesting. According to Wikipedia OpenGL 2.0 was released in 2004, and OpenGL 2.1 in 2006. R300s were released in
2002/2003, and a lot of R400s were released in 2004. R500s saw the light of the day mainly in 2005/2006.
Are the OpenGL 2.1 features required by Kwin among those not fully supported by hardware from these generations? Is that what's killing its performance? If yes, what would be the possible workarounds?
The key point is that the decision about exposing specific bits of OpenGL support is rarely as simple as people think, not only during initial development (which was how this issue blew up in the first place) but even after support has matured.
Leave a comment:
Leave a comment: