Single layer DVD-R for 720p. Double layer DVD-R for 1080p.
Very rarely will you need to stray from that. In those cases, just rip down to a 23.25 GB MKV / m2ts and store them until you can afford to burn them to blu ray.
What are you talking about? The standard is to encode a blu-ray rip down with x264. 720p in 4.37 GB and 1080p in 7.93 GB (single layer and double layer DVD +/- Rs).
Of course there are people out there who will just encode with a constant bitrate / quality target without caring for final file size (and some people who exceed 8 GB on purpose to make it seem like their release has higher quality, or just to piss people off).
It's a very active scene. Rips can be had easily. Encodes in various formats, sizes, resolutions, etc. can be had very easily.
Ads. Sites host ads. People buy ads through ad placement companies like Google. Bad people engineer ads to contain the exploit and payload. Site serves up bad ad. Users of site get fucked.
There aren't 20 forks of it. There aren't updates to the apps (and app store) every 5 minutes. No one ever says "try the nightly build, here's the latest tarball". You don't need to touch a command line to deal with it, ever. There's a person providing support for the store and for each app.
The vast majority of machines capable of running 7 will be running 64-bit CPUs. (Fuck Intel for still pumping out 32-bit CPUs for their new line of mini notebooks.)
The vast majority of 32- and 16-bit software will run in a 64-bit environment. The only issue is drivers. If MS had made 64-bit a requirement, the vast majority of manufacturer's would have gotten on the fucking ball.
Tweaky audio cards? Please do yourself a favor and look up the fiasco that the new audio DRM bullshit (introduced in Vista, still around in 7) caused.
They didn't. It's got a forced shiny UI I don't want, it's got a 32-bit version available, etc.
Vista introduced a completely new audio stack, in order to implement the secure audio path drm bullshit. Many older sound cards simply can NOT output digital surround because of it, regardless of driver updates.
A 32-bit Windows OS only 4 GB of memory space. You have 4 GB of addresses, and from that you subtract all memory-mapped I/O addresses, and that's what Windows presents to the user.
You could also use one of them 32-bit CPUs with a server version of the OS and a mobo that all support extended addressing to get more memory (typically 64 GB max, 36-bit addressing) while sacrificing performance.
Win7 in classic UI mode, without the endless indexing, without the enhanced DRM, etc.
If software vendors refuse to move forward, then we'll never move forward!
But no, it's not software vendors, it's hardware vendors refusing to put out 64-bit drivers.
See, you have both 32-bit and 64-bit software running on one 64-bit OS. All I want is for there to be no 32-bit OS option. The only issue is drivers (and yes, a few 32-bit programs that won't run on 64-bit, just as we had with 16-bit programs in 32-bit land).
How is that evident? Had spirit had a mini wiper, (no, it doesn't damage the panels, lol), we wouldn't have had to wait for months while it was on just enough power to stay alive.
Not if you're using a 64-bit instruction set and programs designed (not just recompiled) for it.
Helps immensely for media encoding, photo/video editing, compression, and sciency apps. In many cases you do get double (or even more) the performance. vs 32-bit.
Who says it's a word? Some dictionary that says "NEW WORDS FOR 2009! MEDIA RUN A STORY ABOUT ME!" ?
Awful does mean full of awe. Awful does not mean bad. Most people use it incorrectly. They mean to say "awfully bad".
Things that are artificial still are made by craftsmen. An average person couldn't make a pencil. Or a dye. Or a flavoring. Just because their tools and workshops and organizational structures are different, and the fact that the word has a negative connotation now, does not change the definition.
Just because people use words differently doesn't make them right. Nor does it invalidate the original meaning if an existing word is used to describe something else (we only have so many words).
Saying that "borrow" could be a synonym for "lend" is akin to saying "take" could be a synonym for "give". They are fucking antonyms!
Telling punk kids to get off my lawn is damned appropriate. I shake my fist at you.
XP Updated installer / boot loader (loading drivers from USB, etc.) 64 bits ONLY DirectX 10 & 11 UAC + not defaulting people to administrator The SATA and SSD support of Vista/7
Don't give me:
Shitty shiny baubles for the UI Extra DRM that makes my audio card useless Endless indexing Pointless bullshit like ReadyBoost
No, the question is "What costs can we add up on one side to make the other side look better?".
When you really consider ALL costs, they're pretty equal. You could cut the bias in the article (or any of MS's ad campaigns about cost of ownership) with a dull melon.
He is comparing the size as reported on the receiving machine with the size as reported on the sending machine, OR as reported by the FTP server on the sending machine.
Slashdot Mirror
Incorrect good sir!
Japan and North America share the same region code for Blu-Ray!
http://en.wikipedia.org/wiki/File:Blu-ray_regions_without_key.svg
I can buy a blu-ray and pop it into my PS3 and just play it.
If I buy a blu-ray drive for my PC, I can do the same.
Your vacation cabin in the woods, where you want no internet access, has a blu ray player and an hdtv?
You're doing it wrong.
BD movies compress really well.
Single layer DVD-R for 720p.
Double layer DVD-R for 1080p.
Very rarely will you need to stray from that.
In those cases, just rip down to a 23.25 GB MKV / m2ts and store them until you can afford to burn them to blu ray.
*Whip cracking noise*
"... the 1952 version of the Day the Earth Stood Still ... I have no intention of watching."
Fuck you.
What are you talking about?
The standard is to encode a blu-ray rip down with x264. 720p in 4.37 GB and 1080p in 7.93 GB (single layer and double layer DVD +/- Rs).
Of course there are people out there who will just encode with a constant bitrate / quality target without caring for final file size (and some people who exceed 8 GB on purpose to make it seem like their release has higher quality, or just to piss people off).
It's a very active scene.
Rips can be had easily.
Encodes in various formats, sizes, resolutions, etc. can be had very easily.
Ads.
Sites host ads.
People buy ads through ad placement companies like Google.
Bad people engineer ads to contain the exploit and payload.
Site serves up bad ad.
Users of site get fucked.
It's always the fucking ads.
Great idea, as long as:
There aren't 20 forks of it.
There aren't updates to the apps (and app store) every 5 minutes.
No one ever says "try the nightly build, here's the latest tarball".
You don't need to touch a command line to deal with it, ever.
There's a person providing support for the store and for each app.
I sure do.
The vast majority of machines capable of running 7 will be running 64-bit CPUs. (Fuck Intel for still pumping out 32-bit CPUs for their new line of mini notebooks.)
The vast majority of 32- and 16-bit software will run in a 64-bit environment. The only issue is drivers. If MS had made 64-bit a requirement, the vast majority of manufacturer's would have gotten on the fucking ball.
Tweaky audio cards? Please do yourself a favor and look up the fiasco that the new audio DRM bullshit (introduced in Vista, still around in 7) caused.
They didn't.
It's got a forced shiny UI I don't want, it's got a 32-bit version available, etc.
Vista introduced a completely new audio stack, in order to implement the secure audio path drm bullshit. Many older sound cards simply can NOT output digital surround because of it, regardless of driver updates.
I thought that for Vista 64...
How would BIOS memory remapping fix that problem?
A 32-bit Windows OS only 4 GB of memory space.
You have 4 GB of addresses, and from that you subtract all memory-mapped I/O addresses, and that's what Windows presents to the user.
You could also use one of them 32-bit CPUs with a server version of the OS and a mobo that all support extended addressing to get more memory (typically 64 GB max, 36-bit addressing) while sacrificing performance.
Win7 in classic UI mode, without the endless indexing, without the enhanced DRM, etc.
If software vendors refuse to move forward, then we'll never move forward!
But no, it's not software vendors, it's hardware vendors refusing to put out 64-bit drivers.
See, you have both 32-bit and 64-bit software running on one 64-bit OS. All I want is for there to be no 32-bit OS option. The only issue is drivers (and yes, a few 32-bit programs that won't run on 64-bit, just as we had with 16-bit programs in 32-bit land).
How is that evident?
Had spirit had a mini wiper, (no, it doesn't damage the panels, lol), we wouldn't have had to wait for months while it was on just enough power to stay alive.
Not if you're using a 64-bit instruction set and programs designed (not just recompiled) for it.
Helps immensely for media encoding, photo/video editing, compression, and sciency apps. In many cases you do get double (or even more) the performance. vs 32-bit.
The only thing that doesn't work in 64-bit land is kernel-level shit (drivers). You can run 32-bit apps in 64-bit land.
(Yeah, there are some stupid exceptions, I don't give a fuck.)
(I mean only one version of the OS. Obviously we're not cutting out the 32 bit instruction set, or the 64-bit OS's support of 32-bit software.)
Who says it's a word?
Some dictionary that says "NEW WORDS FOR 2009! MEDIA RUN A STORY ABOUT ME!" ?
Awful does mean full of awe.
Awful does not mean bad.
Most people use it incorrectly. They mean to say "awfully bad".
Things that are artificial still are made by craftsmen. An average person couldn't make a pencil. Or a dye. Or a flavoring. Just because their tools and workshops and organizational structures are different, and the fact that the word has a negative connotation now, does not change the definition.
Just because people use words differently doesn't make them right. Nor does it invalidate the original meaning if an existing word is used to describe something else (we only have so many words).
Saying that "borrow" could be a synonym for "lend" is akin to saying "take" could be a synonym for "give". They are fucking antonyms!
Telling punk kids to get off my lawn is damned appropriate. I shake my fist at you.
I think he is biased (and hypocritical), loud, and annoying. I do not think he is funny nor intelligent.
However, I find your criticism to be lacking for various reasons.
Give me:
XP
Updated installer / boot loader (loading drivers from USB, etc.)
64 bits ONLY
DirectX 10 & 11
UAC + not defaulting people to administrator
The SATA and SSD support of Vista/7
Don't give me:
Shitty shiny baubles for the UI
Extra DRM that makes my audio card useless
Endless indexing
Pointless bullshit like ReadyBoost
No, the question is "What costs can we add up on one side to make the other side look better?".
When you really consider ALL costs, they're pretty equal. You could cut the bias in the article (or any of MS's ad campaigns about cost of ownership) with a dull melon.
For hipster trash neourbanites like you.
Get the weekender so we can tell you what to think, and what to parrot off to your friends in order to sound smart and cultured.
You don't even get mad cow from eating the beef.
You have to suck on the brain / spinal cord of a hundred mad cows to get enough prions in you.
LASER is not a word.
It's an acronym.
Fridge is not a word, it's an abbreviation.
Videogame is not a word. Video and game are both words.
Email is not a word. E-mail is an abbreviation for electronic mail.
Etc. for most of your list.
Either way, there's a big difference between making a new word to describe something new, and changing the meaning of an existing word.
They are both Windows machines.
We're using FTP.
He is comparing the size as reported on the receiving machine with the size as reported on the sending machine, OR as reported by the FTP server on the sending machine.
I prefer to lash out for no reason.