Bzzzzzt. Combining tabs and spaces to make up a single indent level is BRAIN DEAD.
Actually no. Indenting w/just tabs is brain dead and indenting w/just spaces is counter-productive. Your low UID aside, I'll stack my 30 years of experience using Emacs like that against that any day.
Actually, yes. Mixing tabs and spaces to make a single indent level (e.g., 0x09 0x20 0x20 0x20 0x20 0x09 0x20 0x20 0x20 0x20) is about the most braindead, stupid, foolish, retarded, dumb thing you could ever do in a text file. It ruins things for everyone.
An assertion should just be the evaluation of a boolean expression.
Assertions can be anything you want them to be. There is no (nor should there be) requirement that they be a boolean expression.
Sometimes it is sensible to say assert(foo_is_valid(foo)); on some object foo, and the foo_is_valid() call might need to do a lot of work.
Or... In an arbitrary precision integer arithmetic library, if you compute the quotient and remainder q and r of a divided by b, it is sensible right before returning to assert that b times q plus r equals a, which obviously incurs a significant speed penalty and should not be part of the production code if the math library needs to be as performant as possible.
I write assertions to document state and to help catch errors. I don't care how fast or slow they run. They are meant to be compiled out.
Yet h265 requires vastly more energy to decode its video streams. Of course, as x265 matures, the situation may change.
"May" change? Nah. Will change. Is changing. Jeez, you can *almost* decode 1080p24 H.265 on an iPhone 6 Plus without ever stuttering (using the VLC app for iOS). If you're plugged in to power, it doesn't matter if it burns the battery; all that matters is that the content plays.
h265 excels in POOR QUALITY encodes at lower bit-rates than h264. But the moment one cares about the quality of the encode, the advantage of h265 currently vanishes when best practices are used with x264.
In my experience, H.265 also excels in high-quality encodes (e.g., RF18 or better) — consistently 2x better than H.264. Your mileage may vary, of course. But I am *quite* happy with H.265.
In an answer above, Kempf says: "I believe H.265 will achieve around 30% gain, in some cases, but I doubt it will bring that much more."
This is so very, very wrong.
I have transcoded literally terabytes of video as both H.264 and H.265, and H.265 consistently is about 2x smaller file size at the same quality as H.264 (even when the H.264 Advanced settings in HandBrake are maxed out). This is far, far better than a 30% gain.
After using H.265, I will never go back to H.264; no regrets about adopting H.265 fully. It is an amazing codec.
Audio volume control has been a feature in the iOS version of the app for over a year. Slide your finger up and down on the right half of the video while it's playing. Similarly, sliding up and down on the left half adjusts the screen brightness.
JavaScript is a SCRIPTING Language, not a PROGRAMMING language.
JavaScript is an interpreted PROGRAMMING language.
If you can't put a shebang line on a.js file and chmod +x the file and run it from the command line, then it isn't a scripting language.
Slashdot Mirror
Bzzzzzt. Combining tabs and spaces to make up a single indent level is BRAIN DEAD.
Actually no. Indenting w/just tabs is brain dead and indenting w/just spaces is counter-productive. Your low UID aside, I'll stack my 30 years of experience using Emacs like that against that any day.
Actually, yes. Mixing tabs and spaces to make a single indent level (e.g., 0x09 0x20 0x20 0x20 0x20 0x09 0x20 0x20 0x20 0x20) is about the most braindead, stupid, foolish, retarded, dumb thing you could ever do in a text file. It ruins things for everyone.
Back in the day, a multi-user system might have had a single 4.8M hard disk, shared between ...
I believe you mean 4.8 MiB, not 4.8 MB.
Standard disk size then was 5 MB, which was about 4.8 MiB.
An assertion should just be the evaluation of a boolean expression.
Assertions can be anything you want them to be. There is no (nor should there be) requirement that they be a boolean expression.
Sometimes it is sensible to say assert(foo_is_valid(foo)); on some object foo, and the foo_is_valid() call might need to do a lot of work.
Or... In an arbitrary precision integer arithmetic library, if you compute the quotient and remainder q and r of a divided by b, it is sensible right before returning to assert that b times q plus r equals a, which obviously incurs a significant speed penalty and should not be part of the production code if the math library needs to be as performant as possible.
I write assertions to document state and to help catch errors. I don't care how fast or slow they run. They are meant to be compiled out.
for(i=0;i
Slashdot does have a Preview button, you know.
Binaries shipped to the field should almost always have assertions left enabled.
With assertions enabled, my most speed-critical code runs 2x or 3x slower. No thanks. I'll stick to proper error handling.
(That said, I love assertions and use them liberally in my code.)
Destruction of evidence is itself a crime.
Destruction of evidence of a crime is a crime.
If you destroy evidence that you took a poop yesterday morning, that is not a crime.
The word you are looking for is statute, not statue.
No their name wasn't Clinton. If it were any other candidate in any political party right now, they would have been on trail right now.
She is on trail right now. On the campaign trail.
In the eyes of the law (courts), spoliation of evidence is equivalent to guilt, but perhaps to a lessor degree.
I think you mean lesser. A lessor is someone who leases, e.g., a landlord.
Yet h265 requires vastly more energy to decode its video streams. Of course, as x265 matures, the situation may change.
"May" change? Nah. Will change. Is changing. Jeez, you can *almost* decode 1080p24 H.265 on an iPhone 6 Plus without ever stuttering (using the VLC app for iOS). If you're plugged in to power, it doesn't matter if it burns the battery; all that matters is that the content plays.
h265 excels in POOR QUALITY encodes at lower bit-rates than h264. But the moment one cares about the quality of the encode, the advantage of h265 currently vanishes when best practices are used with x264.
In my experience, H.265 also excels in high-quality encodes (e.g., RF18 or better) — consistently 2x better than H.264. Your mileage may vary, of course. But I am *quite* happy with H.265.
In an answer above, Kempf says: "I believe H.265 will achieve around 30% gain, in some cases, but I doubt it will bring that much more."
This is so very, very wrong.
I have transcoded literally terabytes of video as both H.264 and H.265, and H.265 consistently is about 2x smaller file size at the same quality as H.264 (even when the H.264 Advanced settings in HandBrake are maxed out). This is far, far better than a 30% gain.
After using H.265, I will never go back to H.264; no regrets about adopting H.265 fully. It is an amazing codec.
The submitter and Slashdot editors are illiterate.
Crackdown is a noun.
Crack down is a verb.
Title should be: China To Crack Down On Unauthorised Radio Broadcasts
FFS.
Woosh. :) :)
Read again more closely... you wrote "costumers" when you meant "customers."
The woes of MicroSoft SQL Server should not be dictating the future. I, for one, am very glad that you argued in favor of 128-bit addresses.
[...] after winning all of their big lawsuits against their own costumers, [...]
Why would they sue their costumers? Someone sew a button in the wrong place or something?
What? The original iPhone in 2007 was the first true smartphone. So yes, there was a period when iOS completely dominated the smartphone landscape.
Audio volume control has been a feature in the iOS version of the app for over a year. Slide your finger up and down on the right half of the video while it's playing. Similarly, sliding up and down on the left half adjusts the screen brightness.
What if the TV refuses to function without a network connection?
Don't buy a TV that refuses to function without a network connection.
Today being an unapologetic straight white Christian Bale is about the only subversive thing left you can do.
FTFY
first of a list makes sense. But if butfirst means "all but the first", then that is the most retarded function name I've ever heard.
rest or remainder would be much smarter names.
If you are the one in a million with 20/8 vision
It's a lot more than that if you could glasses and contacts. It's trivial to get 20/10 vision with glasses if you go to a good optometrist.
JavaScript is a SCRIPTING Language, not a PROGRAMMING language.
JavaScript is an interpreted PROGRAMMING language. .js file and chmod +x the file and run it from the command line, then it isn't a scripting language.
If you can't put a shebang line on a
http://grammarist.com/usage/af...
The 97% dark matter theory is the additional mass required to bind each galaxy together.
Oh, come on. We all know that it's The Force that binds the galaxy together.