I've been wondering why not window.chrome == true or Boolean(window.chrome), but it turns out that the former doesn't work and that == has essentially no use unless you remember some completely arbitrary rules, and that JS developers would complain that the latter is too long given the fact that I've seen javascript code using !0 for true and !1 for false, instead of just true and false because they can save 2 to 3 characters that way.
In my experience public toilets are so badly maintained that I'd rather avoid touching any porcelain besides that of the sink. That's one of the main reasons I go for urinals. It's also often the most direct way to achieve my objectives if my only goal is to urinate, unless there are other people in which case I hover around waiting for one urinal to become less crowded or just use a stall if it doesn't look disgusting.
That's kind of what confuses me. Don't referees normally only talk with the players to ensure a fair game? I've never heard of them talking with the audience, but I also don't really watch sports.
This sounds a lot like me. Whether I have ADHD is something I've been wondering for some time now, but the descriptions of ADHD are always so conflicting to me, because every symptom can be taken as a evidence or counterevidence by changing perspective, partly because of this duality you described.
The huge differentiator is that KDE may look like windows OOTB on most distros, but if you want you can easily make it look like Gnome, Mac, Unity… whatever. The panels and menus are infinitely configurable.
Is there a way to configure the look of all the apps running on kde? Because one of the main things that keeps my away from KDE is how ugly all the k* apps look out of the box.
The phrasing of that sentence is confusing. I at first interpreted it as the user being the subject that uses comment threads, not the simulation. Only after reading the comments did I figure out the correct meaning of the sentence.
I've been wondering why not
window.chrome == trueorBoolean(window.chrome), but it turns out that the former doesn't work and that==has essentially no use unless you remember some completely arbitrary rules, and that JS developers would complain that the latter is too long given the fact that I've seen javascript code using!0for true and!1for false, instead of justtrueandfalsebecause they can save 2 to 3 characters that way.