That guy is totally cosplaying Benny from The LEGO Movie
That guy is totally cosplaying Benny from The LEGO Movie
It isn't an "upgrade bug" as the upgrade isn't slated for release for months.The build in question has only been released to the fast ring for Insider testing. In other words, it's only been given to those on the extreme bleeding edgeof Windows testing.Is Slashdot going to start posting articles for every minor issue in Chrome canary releases also?
"That's funny since most printed text is printed at like 72dpi"
That is entirely incorrect.You can't find any commercial quality high volume offset press that has such a ludicrously low resolution. Even twenty years ago, when I was stillworking in the publishing industry, final output was always at (or above) 1200dpi with color proofs coming at around 600dpi and b&w pasteupsoff of a laser printer at 300dpi. Nothing, absolutely NOTHING ever dropped below 150dpi.150 was a rarity, mostly from when a client would cheap out and only get a flatbed scan of a photograph instead of opting for the higher quality (andpricier) drum scan.
Which PEP 8 are you reading, as you areclearly not reading the correct one. In the entirety of PEP 8 the word 'tabs' only appearsseven times. Hereis all the PEPhas to say on that subject,
Tabs or Spaces?
Spaces are the preferred indentation method.
Tabs should be used solely to remain consistent with code that is already indented with tabs.
Python 3 disallows mixing the use of tabs and spaces for indentation.
Python 2 code indented with a mixture of tabs and spaces should be converted to using spaces exclusively.
When invoking the Python 2 command line interpreter with the -t option, it issues warnings about code that illegally mixes tabs and spaces. When using -tt these warnings become errors. These options are highly recommended!
And since PEP 8 only deals with code being written for the Python Standard Library those statements are only applicable to that codebase.
So far you've referred to people who use tabs as 'idiots','brain dead', and'morons' in various, all demonstrably incorrect, replies in this discussion, yet all you have done is continually demonstrate your lack of actual knowledge regarding PEP 8. If anyonein this discussion deserves to have disparaging names regarding their lack of mental acuity assigned to them it would be you.
"It doesn't say'tabs are OK'."
While I admire your attempt to try to steer the argument to yourlimited comprehension of PEP 8 and yourinsular viewthat tab using people are "idiots", your strawman attempt was quite awful.All one has to do is read the parent post to which you are replying to see that youmade up a fake quote and tried topass it off as something I wrote.
Go read PEP 8 again, please. It is quite clearly denoted as the style guide that should be adhered toif you are contributing to the Python Standard Library.It is not promoted or positioned as the only style guide to ever be used on any Python project. In fact the final sentence of the Introduction to PEP 8 says all that needs to be said about projects using their own conventions, "Many projects have their own coding style guidelines. In the event of any conflicts, such project-specific guides take precedence for that project." But, honestly, if you are sosmall minded as to view people who use tabs as "idiots" I doubt we can hold it against you that you were unable to read and comprehend five (5) sentences. If you had somehow maintained the mental stamina necessaryto readthe title of the second section of the PEP, "A Foolish Consistency is the Hobgoblin of Little Minds" you might have managedthe insight that the following sentences would further clarify the situation. Starting at sentence four (4) in that section are these four (4) sentences, "A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is the most important."
To summarize, projects can have their own coding styles, project specific coding styles take precedence for that project, and consistency within a project is more important than consistency with PEP 8.
That you would say 'Wake up' as a reply to my post, as if I'mnot comprehending something when it is absolutely clearthat you can't comprehend nine (9) sentences at the very start of a PEP is pretty self-righteous of you. Why don't you take your ego down a peg or two (or nine) andgo read PEP8, for it is not what you are portraying it to be.In other words, words that you can probably understand, "wake up". There is no mandate whatsoever in PEP 8 that all Python ever written must adhere tospaces and an indentation level of 4, let alone anything else specified in that PEP.
Have you actually read PEP 8 or are you just throwing it out there?The intro to that PEP goes to great lengths to explain that it is the preferredstyle guide for the Python Standard Library, thatother coding standards are OK, and that you should always adhere to the coding standards any given project uses. It is not some sort of dictatorial manifesto that ALL PYTHON SHOULD BE 4 SPACES.
Your statement has no relevance to this story or the trial whatsoever. Oracle v. Google dealt with copyright and fair use. Patent abuse/trolling is an entirely different issue.
As for 'shaking up' Congress to fix the not-relevant-to-this issue, would you care to elaborate on what you've done in that regard?
"Adds the submitter...(And of course there's Periscope)"
Which is a tool 100% unlike either the app the NY Times is writing about or the other two apps the submitter referenced. So while yes, there is Periscope, it is not germane to this discussion.
Well, I did. But now that I've read your thought provoking, well researched, and immaculately composed post I do believe you have changed my mind. Your insightful and intelligent argument will sway many, I believe.
So how do you explain superior performance on consoles, then? And no, there isn't 11GBs worth of texture data difference between the PS4/XB1 and PC versions.
You realize that light bounces and people have peripheral vision. People shouldn't have to 'get over it'. If you are so self centered as to not care about other people, including the woman you were with, enjoying a movie then you are an asshole. If you are so attached to Slashdot that you can't go the length of a movie without checking it, get your ass up and go to the lobby.
Thanks for being the self-centered asshole who feels it's OK to fire up his phone screen in a darkened theater. Why should you have to bother to park your selfishness for 90-120 minutes and let the scores of other people see a movie in peace, right?
It was a joke
No, it wasn't. You could more correctly state, "It was meant as a joke". That would be a valid statement.
Will ClanLib turn around the tides and finally challenge SDL?
If you let the code generate the UI you'll get what only a programmer thinks is a good UI (for reference, property grid controls). It's akin to thinking the content of a magazine can dictate a pleasing layout. It can't. Without writing code (or using a tool that writes code based on a graphical layout tool) to specify what is important, what needs emphasis, how the user should progress through the UI, you'll just get a mess. As soon as you go down the path of tagging items in the source code to help a system determine those things you're back at the starting point, you're having to "write text" (horrors!) to get a workable UI. Yes, just workable. You'll never get a stellar UI without a proper person designing it.
The F-15 Eagle: If it's up, we'll shoot it down. If it's down, we'll blow it up. -- A McDonnel-Douglas ad from a few years ago