32
u/SafariMonkey May 11 '20
I notice that the graphs appear only to go back as far as the author started tracking. Would it be valuable to retrospectively benchmark older versions of LLVM to find past regressions that may be able to be optimised?
25
56
u/wyldphyre May 11 '20
I can’t say a 10% improvement is making LLVM fast again, we would need a 10x improvement for it to deserve that label. But it’s a start…
The graph from March through May shows the hard work that's being put in to recover. How does current trunk look versus 9.0?
24
u/gaumutra_fan May 11 '20
The author mentions that the benchmark set up was for clang + llvm, so it might not be representative of performance on rustc. I wonder what the blocker is for creating a rustc + llvm benchmark.
17
u/Ek_Los_Die_Hier May 11 '20
I think rustc works on a slightly modified LLVM fork, so having rustc benchmarks that track the head of LLVM might not be quite as easy. Hopefully someone who knows more can correct me if I'm wrong!
39
u/nikic May 11 '20
The rustc LLVM fork mostly exists to make LLVM compile on CentOS 5, and for backporting. The bigger issue is that LLVM has an unstable API, so rustc needs to be adjusted to build against newer LLVM versions. We usually only do that work when new LLVM versions are released, so rustc is usually not compatible with current LLVM master.
4
u/matthieum [he/him] May 11 '20
Hijack...
Have you considered tracking Debug build times? In my experience incremental builds are generally at -O0 or -O1, with debug symbols, as developers work on their machines, and those are latency sensitive as a human is waiting in front of its keyboard.
11
u/nikic May 11 '20
I went ahead and enabled collection of
O0-gdata on the server. I agree that this is also an important configuration. This case will probably spend a large fraction of the time in clang itself (rather than LLVM) though.2
u/matthieum [he/him] May 12 '20
Thanks!
3
u/nikic May 12 '20
Funnily enough, the first debug build regression landed just an hour after I did that...
3
u/CUViper May 11 '20
If you look at perf.rust-lang.org, it includes data for
check,debug, andopt(optimized).
11
u/zyrnil May 11 '20
There’s also some larger ongoing efforts that have mostly stalled, such as the migration to the new pass manager, the migration towards opaque pointers (which will eliminate many bitcast instructions), or the NewGVN pass.
Can you talk a little bit about why these efforts are stalled?
21
42
u/game-of-throwaways May 11 '20 edited May 11 '20
Don't take this the wrong way, I think the work you're doing is great! But I find your choice to use -O3 instead of -O2, -O1 or even -Os very strange. The whole point of the difference between -O1, -O2 and -O3 is precisely in those optimizations where there is a trade-off between compile-time and run-time performance.
-O1favors compile-time speed, so doesn't do optimizations which take a lot of compilation time-O2then performs more optimizations, even those that may take a bit more compilation time-O3is the "extreme" end of the spectrum: nearly all optimizations, even those that take a long time to compile for little runtime benefit, are enabled
(EDIT: it appears that this may not be how it actually works for llvm, as -O2 apparently doesn't compile much faster than -O3?)
So it's very perplexing then for you to complain that llvm compiles take too long, while at the same time using -O3.
I also disagree with your statement here:
For the most part, optimization is already “good enough”, and additional optimizations have the unfortunate trend to trade large compile-time increases for very minor (and/or very rare) improvements to run-time performance
For most applications, that's true. But for some applications, there is no "good enough" run-time performance. More is just better. Examples are:
AI (e.g. chess engines)
machine learning whenever computation time, not data, is the limiting factor
high-frequency trading on the stock market
scientific computation that ends up being run on expensive supercomputers or distributed networks (like BOINC) for a long time
OS kernels, or common system-level libraries which are included as part of your distribution or provided in compiled form by a package manager
etc
For these applications, 1 minute of extra compilation time is irrelevant and well worth even a 0.1% increase in performance. These are the applications that -O3 is designed for. For everything else, where compilation speed is not irrelevant, there's -O2.
EDIT: after writing all this, I though, "wait, Rust in --release mode compiles with -O2 by default right, not -O3?" Well, nope. It's -O3. Now that is a very strange choice. No wonder people complain that it's llvm which drags down Rust compilation times. To me it would make much more sense to compile in -O2 by default and let the advanced users opt in to opt-level=3, instead of compiling with -O3 by default and expecting the common, non-advanced users to specify the more reasonable opt-level=2. What are your thoughts on this? Shouldn't Rust compile with -O2 in --release by default?
44
u/nikic May 11 '20 edited May 11 '20
In practice, O2 and O3 do not differ materially where compile-time is concerned (at least with LLVM). For many (rust) programs, anything below O2 is impractical, because it makes the resulting binaries too slow. 3x faster compilation does not buy you anything if your tests run 30x times slower. So in practice, there often is not much choice left.
See also the comment at on the general attitude here: https://www.reddit.com/r/programming/comments/ghc94x/make_llvm_fast_again/fq93tk1/ I do a lot of optimization work, and the actual quality of the codegen done by the compiler only figures into that very rarely, once you pass a certain baseline. That baseline is primarily the ability to optimize away all those "zero cost abstractions" to be actually zero cost. (Unfortunately this is not quite as true of Rust code as it is of C code -- LLVM does particularly badly with optimizing some Rust code patterns, because it is bad at things like bounds check elimination and memcpy elision.)
Beyond that, most of the optimization work has to happen by hand, and even the smartest compiler with the longest compile-times will not be able to help you there.
19
May 11 '20
it is bad at things like bounds check elimination and memcpy elision
Luckily these are viable optimizations to perform on MIR too, so perhaps some day we won't be relying on LLVM too much for this anymore.
3
2
u/PM_ME_UR_OBSIDIAN May 12 '20
If there were a sufficiently dedicated volunteer, could this be done LLVM-side? (I'm between jobs and looking for a project to do for the next few months.)
Pinging /u/lzutao because I'm interested in their opinion as well.
2
3
u/Shnatsel May 11 '20
it is bad at things like bounds check elimination and memcpy elision
Could you provide an example where bounds check elimination is not performed, even though it could be? I've found that rustc (presumably thanks to LLVM) is very good at bounds check elimination, and this behavior is stable across different compiler versions (unlike e.g. auto-vectorization). I've only seen it fail to eliminate bounds checks in cases where that would alter program behavior.
Totally agree with you on memcpy elision though.
2
u/nikic May 11 '20
Recent one I saw is https://github.com/rust-lang/rust/issues/71997. This is a SCEV/IndVars failure to eliminate an IV comparison.
Another common class are checks that should be known based on value range information. All the infrastructure to optimize these away is there, but doesn't get used where it matters due to a tricky LVI/CVP weakness.
Another typical problem is that "implied conditions" that don't involve constants are pretty hit and miss. If you have an assumption that x > y, LLVM will often not be able to optimize a later x >= y check away.
20
u/CryZe92 May 11 '20 edited May 11 '20
I'm honestly still under the impression that we just need a new additional default profile in cargo. One that you use by default, that optimizes for both compilation speed and decent runtime performance. At the moment we only have debug which focuses way too much on preserving debugging information that it's way too slow for applications that do a heavy amount of calculations. You really only want to use such a profile for actual debugging. And release is all about getting the maximum performance, where compilation time really shouldn't matter. But that totally makes it unsuitable as the main development profile as well.
So really there should be:
debug: for actually debugging your code (optimizes preserving debugging information)
development: for normal development (highly incremental, optimizes compilation times, with a slight amount of optimizations)
release: for actually generating the final binary (non incremental, possibly link time optimized and profile guided, full optimizations)
11
u/game-of-throwaways May 11 '20
Yeah perhaps that's an even better solution than making
--releasecompile in-O2by default. I often end up developing in--releasemode because the run-time performance of debug mode is so ridiculously slow, often 2 orders of magnitude slower.For now, what you can do, and what maybe I will do, is to specify in cargo.toml
[profile.dev] opt-level = 1 # Use slightly better optimizations. overflow-checks = false # Disable integer overflow checks.2
May 13 '20
unless you really trust your tests, disabling integer overflow checks in debug seems like an easy way to accidentally rely on overflow when you shouldn't be.
1
u/game-of-throwaways May 13 '20
What? That does not seem like something that you do accidentally, especially if you know you shouldn't. I have literally never had my code panic because of an integer overflow.
That is not to say I don't have integer overflow bugs. Some of my datastructures might behave poorly when the number of elements approaches 2^31 or perhaps 2^63 elements, but a unit test sure won't catch that.
1
u/lzutao May 11 '20
As nikic said,
-O2may not enough to optimize Rust code to zero-overhead abstraction. I once get that but I cannot find the example now.13
u/HildartheDorf May 11 '20
The 'default' would make sense to be Og (which is a mix of O1 and O2 flags, but focusing on not destroying debuggability).
6
u/mattico8 May 11 '20
The point is to notice regressions that are introduced. If a regression is introduced into an optimization that is only active at -O3, it's still important to know, right? You're right that it makes for a less useful benchmark if most users are using -O2.
1
u/game-of-throwaways May 11 '20
But a "regression" at -O3 could just be an extra optimization pass that takes a long time to run, for relatively small gains in runtime performance. That's not a "regression", it's what -O3 is designed for. There is no higher optimization level.
7
u/ssylvan May 11 '20
But a "regression" at -O3 could just be an extra optimization pass that takes a long time to run, for relatively small gains in runtime performance
It could be! Or it could be that you just added something that is unnecessarily slow at compile time and if you were made aware of it you could do something about it without affecting the runtime performance.
I think the whole compile time vs runtime tradeoff is a real tradeoff that sometimes has to be made, but without actually tracking compile time you aren't actually making that tradeoff. Knowing that there is a compile time performance regression is the first step to being able to actually make that kind of tradeoff. So while it's true that sometimes you may have to make a deliberate decision to sacrifice compile time for runtime, in my experience most performance regressions are not intentional like that. So if you get told that a change made compile time worse you can often fix that without hurting the runtime performance, or you can at least spend a little bit of time mitigating the cost.
1
u/game-of-throwaways May 11 '20
Yeah I agree, but ok. The situation before OP's efforts was: compile-time performance is not tracked at all. With OP's efforts, the compile times are tracked, under 3 sets of compilation flags, all -O3. Wouldn't it make more sense if at least some of them were tracking -O2?
3
u/mattico8 May 11 '20
Sure, you still need a knowledgeable reviewer who can understand the context of what's being introduced to see if the result is reasonable. The scenarios I'm thinking of:
A new optimization is introduced and originally enabled by default at O2 but it is found to increase compile times by 15% so it is changed to only be enabled by default for O3.
A change is made to an optimization pass which causes a single benchmark to compile 30% slower. After investigating, it is found that some code in that benchmark triggers an accidentally quadratic behavior which is then fixed.
I'm not suggesting "longer -O3 compile time = bad" as a metric I'm just saying it's useful information, even if you believe that O3 compile times don't matter.
5
u/Rusky rust May 11 '20
This is all true but unfortunately does not really make a difference to what needs to or can be done to improve the situation. LLVM is slower than it ought to be at all levels of optimization, and all levels ought to be tracked like this, much like rustc-perf.
There are many more performance-sensitive aspects of LLVM than "which analyses and transformations are running." The article addresses a few of them! Performance of those aspects affects every level of optimization.
5
May 11 '20
--releaseused-O2for many releases due to misoptimizations in LLVM. When it was switched back to-O3it was because it helped a few cases and didn't noticeably impact compile times (ie,-O2is just as slow as-O3).2
u/Alborak2 May 11 '20
For my core application, I'd trade compile time for runtime at a ratio of about 1000:1. As long as it takes less than about 24 hours to compile release builds, and I can still get -O1 builds for iniital testing, I'll take it.
2
u/whatisaphone May 11 '20
This is great insight. Taking it further, I'm guessing that when most people complain about compile times, they're actually talking about the edit-compile-run cycle, which is usually a debug build. So why not (also) measure build time without optimizations?
1
u/Ragarnoy May 12 '20
The difference between o3 and o2 (well, one of them) is that it can sometimes lose precision in floating point operations, if I recall correctly the worst offender was FMA optimizations. This is why gcc defaults to O2 and not O3. For most people the precision loss is negligible, but in some fields it's unacceptable.
Anyways, I'm rambling, my main point being O3 is dangerous.
1
1
u/jamadazi May 12 '20
I believe you are misinformed. O3 does not apply dangerous optimizations, you are thinking of "-ffast-math" (also enabled with "-Ofast") in GCC/Clang. Rust has no equivalent IIRC (which I think is a widely-requested feature by gamedev people).
O3 is for optimizations that have questionable performance benefit and might not benefit all code.
1
u/Ragarnoy May 12 '20
I did tests and used to work in the aeronautical field where they need to take those kinds of things very seriously. Ofast would make results outright wrong sometimes, but O3 would only slightly alter them around the 11th decimal sometimes, which is negligible unless that result is fed elsewhere and altered again, and again, and again. Now I'm talking about a specific case so I might be wrong in 99.9% of the other cases
1
u/jamadazi May 12 '20
OK nice to hear that you have actual experience confirming what you are saying. I was going based on reading the documentation.
It is indeed very difficult to manage floating point inaccuracies in practice. Little things like what order the assembly instructions are in can make a difference.
in the aeronautical field where they need to take those kinds of things very seriously
I am curious now, why even use floating point then? There are more accurate representations of numbers.
1
u/Ragarnoy May 12 '20
It's cost efficient, no one want put the money and brain power into rewriting simulators that were made in 2002 in C with hundreds of thousands of line of code. Especially since the people who made the damn thing tend to leave at some point.
1
u/jamadazi May 12 '20
is the "extreme" end of the spectrum: nearly all optimizations, even those that take a long time to compile for little runtime benefit, are enabled
AFAIK it is not about compile time, but for "questionable" optimisations that are not considered "universally good" for all code. O3 is for those optimisations that may or may not benefit performance depending on the use case, or maybe even regress in edge cases.
1
May 11 '20
I think that some Rust idioms or generic implementations in libcore rely on heavy loop optimization passes, in some cases, the loop needs to be optimized down to a constant-time operation or a memcpy, and similar things.
Of course, having the default be opt-level=3 does nothing to remove this dependency on these optimization passes! So it's still a great point to explore opt-level=2 by default.
8
u/gizmondo May 11 '20 edited May 11 '20
Great work. I wonder why -O3 was chosen as a target level instead of -O2.
4
May 11 '20
Presumably a lot of new optimizations are active at -O3 only or at least before they are added to -O2 since -O2 is supposed to have more conservative optimizations.
5
u/ice_wyvern May 11 '20 edited May 11 '20
I suppose this may be but some of the optimisations in -O3 may have a negative impact on performance or even or even have unexpected behavior if used w/o careful testing. That's usually why using -O2 is recommended
Edit: using -O3 also increases compile time as well as increases binary size which can be undesirable
6
May 11 '20
Maybe, but in the context of catching new optimization's performance regressions early -O3 seems like the right choice. Can't catch regressions in disabled optimizations.
0
May 11 '20
[deleted]
1
May 11 '20
Not sure what your point is considering the article is about LLVM, not Rust.
0
May 11 '20
[deleted]
1
May 11 '20
That may very well be but this comment thread was clearly about the article and why the author chose -O3 as a target for its benchmark.
-18
May 11 '20 edited May 11 '20
People from outside the US appreciate US politics differentlyt han US citizens, but "catchy" Trump-like slogans are quite politicized in the US, and might detract from some audience that associate them with a particular political ideology.
One might argue that this is expected, as the optimization pipeline is continuously being improved, and more aggressive optimizations have higher compile-time requirements.
We are talking about a 10% performance regression in rustc, but rustc is a bootstrapping compiler compiled with LLVM. So if rustc-stage1 takes 10% longer to compile because LLVM got slower, but the resulting rustc-stage2 would be equally fast as before, this wouldn't be an issue (LLVM got slower, but produces binary that run so much faster, than using LLVM to compile itself overcomes that issue). The problem is that LLVM takes 10% longer to compiler, but when compiling LLVM itself, the result is not 10% faster to cancel that out. So as you mention, one trades in a relatively huge compile-time increase, for a tiny or non-existant run-time performance increase, at least, when compiling LLVM itself.
It may be time for /u/nnethercote to also start looking at speeding up the LLVM parts that impact Rust. If they haven't been measuring compile-times there might be a lot of low-hanging fruit lying around, and since Rust expends a huge fraction of the execution time in LLVM, doing that could speed up Rust compile-times significantly.
15
u/nnethercote May 11 '20
I don't really want to work on LLVM internals, so I'm glad that somebody else is doing this sort of thing.
Having said that, I am currently looking at reducing the amount of LLVM IR that rustc produces, which has much the same effect as speeding up LLVM. See https://github.com/rust-lang/rust/pull/72013 for one example.
1
May 11 '20
Yeah, it was just an idea. Some of the optimizations that nikic applied look very similar to some of the ones you have applied to rustc in the past (e.g. using SmallVec, shrinking type sizes, etc.).
I think it might be helpful for them an everybody to maybe summarize some of the most common recurring issues that you have found while optimizing rustc.
43
u/tetroxid May 11 '20 edited May 11 '20
So now the entire world can't use sentences constructed like "Make <noun> <adjective> again" because of the orange monkey? Come on.
7
u/Ayfid May 11 '20
It is a super generic and fairly common construction in English. Complaining that any sentence with this format is "political" because a US president used it in a slogan makes as much sense as saying that wearing fake tan is now a political statement because said politician is famously orange.
It says something about how politically motivated the people complaining about it are, when they apparently see Trump and political motivation in everything.
9
u/epicwisdom May 11 '20
I mean, it's pretty clear the title is directly referencing 45's little phrase. That's a bit different than just coincidentally using a basic English construct.
6
u/irishsultan May 11 '20
Note that Trump didn't come up with this construct, Make Britain Great again (which is a much better pun) was used first(*) in 1950. It was used by someone who would probably also be hated by those hating Trump, but stating that clearly it references "45's little phrase" makes clear that you are probably in the habit of thinkin everything revolves around America.
(*) I say was used "first", but it may have been in use before, however it definitely predates contemporary american politics.
4
u/andoriyu May 11 '20
Technically MAGA slogan is based on Reagan "Let's make America great again" from the 80s campaign.
1
u/irishsultan May 12 '20
As far as I know the 80s do not predate the 50s, so even if that were true there are two possibilities, either Reagans slogan is based on Thatchers, or it is a natural way to phrase things, either way the insistence that clearly it's referencing Trumps slogan is nebulous at best.
1
1
u/epicwisdom May 12 '20
The title's not referencing the 1950s usage. You're reading too much into the precise wording.
2
12
May 11 '20
On the first point, I agree, spoofs on the Make X great again phrase are simply not funny and not appropriate.
-11
May 11 '20 edited May 11 '20
Unfortunately a lot of people appear to disagree with keeping /r/rust apolitical. Or maybe they just disagree about raising that issue up for submissions that are great content-wise.
9
u/gizmondo May 11 '20
I tend to agree, but it seems funny that more explicitly political "eat the rich" slogan in this post didn't receive such a reaction.
0
u/noxisacat May 11 '20
You are comparing a sample string deep in an article with a blog post title reused as a Reddit entry title. Obviously the string is not going to trigger any reaction.
I'm pretty sure that post would have been moderated instantly if that was its title, if only because people like you apparently care that hard about that one that you remembered it when it's 2 months old.
-3
u/fgilcher rust-community · rustfest May 11 '20
There's a slight difference between a phrase that goes back to the French Revolution and has entered pop culture through the likes of Motörhead and Aerosmith and the national resurrection slogan of the current US president.
Also, it's tired and uncreative.
-5
6
u/Ayfid May 11 '20
No, people are down voting because we don't want or need politics in the sub. The title is not political - those comparing it to US politics and complaining about it are.
-1
May 11 '20
The title is not political
Other replies here and other comments in the other submissions (e.g. /r/programming) do believe that the title is unnecessary political, because it uses the campaign slogan of a presidential candidate.
Care to back up your claim that this title is not political?
4
u/Ayfid May 11 '20
That is not how burden of proof works. You are projecting intent onto something for which there is no evidence. You (and everyone else who agrees with you) has the burden to prove that this is "political".
"I think it is political" only tells me about yourself, not about the title.
-2
May 11 '20 edited May 11 '20
That is not how burden of proof works.
You claimed, without proof, that "Make X Y again" is not a politicized statement, so I think it is fair to demand you to back it up.
OTOH, I wrote this in my top comment in this thread:
People from outside the US appreciate US politics differentlyt han US citizens, but "catchy" Trump-like slogans are quite politicized in the US, and might detract from some audience that associate them with a particular political ideology.
This:
explicitly acknowledges in the first sentence a lack of intent from part of the OP, since I know they aren't from and don't live in the US, which disproves your claim that I am projecting intent.
hypthetises that political titles distract from content - given how many replies and up/downvotes this has received here and in similar threads in other sub-reddits, this hypothesis has been tested and is now true,
claims that the title is political, and the fact that we are discussing whether it is or is not right now proves that it is.
2
u/Ayfid May 11 '20
You claimed, without proof, that "Make X Y again" is not a politicized statement, so I think it is fair to demand you to back it up.
Your disclaimer in the OP is only applicable when people read the title as being political. The claim that the title is political is a precondition of your statement, as it only applies to those who read it as such. In all other cases, your statement is moot. You aknowleding the moot case of someone who doens't see the title as political does not absolve those who do of the burden of proof.
In no case is the burden of proof on me to prove that the title is not political. Those who claim that it is need to prove that. Pointing at people who think it is political does not in any way constitute proof that it is so - that is a fallacy (argumentum ad populum). You are quite literally demanding that I prove a negative, and that I should assume you and everyone who agrees with you is correct until I can prove otherwise. No. That is not how this works.
claims that the title is political, and the fact that we are discussing whether it is or is not right now proves that it is.
For this to be true, the only requirement for something to be "political" is for someone to declare it as such. If that is the case, then the word is meaningless, because it can be applied to literally anything, has no concrete definition, and ascribes no properties to the object being labeled as such beyond the fact that it has been labeled. If that is the case, then your objection that "people might see the title as political" is equally meaningless and unavoidable.
-3
May 11 '20
I think I disagree too ;) it is an inappropriate title exactly because of the political charge it has, which is very negative. Making this judgement, that it is very negative, is political.
3
u/topin89 May 11 '20
You know, it's kind of ironic your own statement is the detraction you warned about.
Also yes, outside of US this statement is ironic or sarcastic itself, depending on context, and since "great again" here means humble 10%, I think the context is quite right.
2
May 11 '20
You know, it's kind of ironic your own statement is the detraction you warned about.
I know, I'm a true artist.
2
u/Senoj_Ekul May 11 '20
Came here to say this about "Make <noun> <adjective> again".
Given the kind of person Trump is, repeating Trumpisms even in light humour is just a tad shitty and will turn a lot of people away (myself included, because if you can't understand why it's bad then I'm not going to view your actual subject matter in a positive light).
13
May 11 '20
Trump stole if from Thatcher's "Make Britain Great Again." Why do you associate it with Trump? Forget about it already.
1
u/JoelFolksy May 12 '20
Trump stole if from Thatcher's "Make Britain Great Again." Why do you associate it with Trump?
Really? I have no dog in this fight, but - really?
1
May 12 '20
I understand why the typical careless reactinary who can't see the bigger picture would hang onto that association, but why would you? My comment was less of a reflection on how things are than it was a request to question your own role in making things that way. "Everyone does it" is not a reason for you to do it.
1
u/JoelFolksy May 12 '20 edited May 12 '20
I would have said that he's making too big a deal out of the association by tone policing what was probably just a cheeky attempt at an engaging title.
But this idea that we're supposed to pretend that MAGA isn't a massive cultural meme because it was based on an earlier phrase is just too goofy. That would be like me browbeating someone for associating the melody of "All By Myself" with Eric Carmen, given that it was borrowed from Rachmaninoff's 2nd concerto.
1
May 12 '20
It's a massive cultural meme because people respond to things without thinking. I only pointed out that it came from Thatcher to give something else to think about. So that maybe they could consider that living life as though it were a sequence of memes to react to is something one could learn to avoid.
MAGA doesn't matter. People matter. Maybe not when they let something as trite as MAGA destroy their ability to think and focus. But if 300+M people can't deal with one dude because they're too busy fighting over his propaganda, that's basically a situation they choose to be in.
0
u/Senoj_Ekul May 12 '20
Mate, I was a toddler when Thatcher was anything. I'm an adult now that Trump is president, and this is the first time I've ever heard that particular line so yes, this take on it is definitely attributed to him.
Given what Trump actually means for most Americans, if not the world, why on earth would you forget it?
1
May 12 '20
Because I don't want to be distracted by sophistic bullshit for the remainder of my life.
0
u/Senoj_Ekul May 13 '20
I don't want to be distracted by spins on a political messages that was popularized by a racist sexist xenophobic man.
See how that works? Confront it, call it out as absolutely not okay, and maybe neither of us will be distracted in the end.
1
May 13 '20
Calling it out is being distracted by it. If you can't get past an emotional response to a phrase, and you make it other peoples' problem, that's you being distracted by it in the end.
0
u/Senoj_Ekul May 13 '20
The distraction isn't the part that is the concern. It's what the phrase is understood to represent - distraction or not it needs to be called out.
1
May 13 '20
It needs to be called out? Sure. Does it need to be called out here, and now, in this context, by these people? No.
0
u/Senoj_Ekul May 13 '20
If not now, when? Does everyone just what for the "perfect time" to say something?
None of this affects me personally, because I'm white and privileged. But it sure as heck affects many many others and so I'll call it out when I see it, regardless of if others think it is the appropriate time.
→ More replies (0)1
u/topin89 May 11 '20
repeating Trumpisms even in light humour is just a tad shitty
if you can't understand why <...> I'm not going to view your actual subject matter
Wow. Just wow.
I really like it when someone made a bold claim and declare anyone who disagrees unworthy of their attention. Not.
-1
May 11 '20
People must really love politics, else you wouldnt be downvoted, most people prolly didnt even read past the first paragraph thinking it's a political rant
7
u/sasik520 May 11 '20
Some ppl (including me) just think that if someone mixes politics with programming, then it is not worth wasting time talking with this person. Simply because the discussion will end on politics sooner or later.
0
May 11 '20
[deleted]
1
May 12 '20
How can it be hard to depoliticize, rust isnt just used in america and as far as I can see (it rarely happens tho, which is good) its always american politics. Like we outside of america care a bit, but not enough that we want it to invade eveything
4
u/jgrlicky May 11 '20
Our hero!! <3 Always appreciate reading your optimization posts!