720/1080 "standards" my ass! My 1080p TV is just a 1680x1050 monitor with some tuner hardware inside the case, and that's actually a good deal considering that a lot of HDTVs (even huge, expensive ones advertised as 1080p) are ripoffs running at 1366x768.
I'm waiting for DisplayPort to take over on the computer side - it might put an end to these lame 96DPI screens we've been stuck with for the past decade.
The person who ported it took everything from the original game and released it on a newer platform. That is like someone taking Sonic the Hedgehog or Mario bros and porting it over with all the same graphics, sounds, and design.
You might have had a point with Nintendo, but Sega has never -- as far back as I can remember -- attacked its own fanbase like this. They turn a blind eye to ports (probably because they can't do it right themselves); most of the "collection" discs they put out on newer consoles are actually a shiny frontend around Gens.
Google already serves most of its videos in the old Flash codec + H.264 + WebM, probably more for mobile too and that's without even counting the multi-resolution encodes for 1080/720p videos.
HTML5 requires a more complex parser than XHTML ever will.
Guess what? The real world isn't a pretty theoretical little flower. HTML5 defines consistent error handling for content on the existing internet, not the non-existent one.
XHTML can be validated for correctness, HTML5 is more difficult to do so.
The code exists for both already, so this is a moot point.
I honestly don't understand the reason for following the HTML route. XHTML is already in an industry understood format that tools already exist for.
Because we're sick of waiting decades for the fucking W3C to do anything. They've procrastinated themselves into irrelevance.
The market rarely reflects a superior technology. I still support XHTML. HTML5 is messy, ugly and a kludge.
Is BASIC also messy, ugly and a kludge to you? Would you say the world would be better off if C64s came with Haskell instead? Get real.
This is all very reminiscent of the events leading up to the Titanic disaster.
"Er... you're heading straight into an ice field ther-" "LOL FUK OFF NOOB!!1/mode +m"
Re:Is GNU/Linux networking as poor as it was befor
on
OpenBSD 4.7 Released
·
· Score: 1
There's rumours that iptables might be going away eventually for this instead.
Now I'll admit I've never used *BSD, but even I can see iptables is *fucking awful* for anything more than the most basic IP/port matching. Hopefully this'll happen sooner rather than later.
Pro-tip: if you need a pronunciation guide, then you desperately need to pick a better name. Yes, better, as in "the current one sucks and should be taken out back and shot".
So, is the "dot" in "H.264" silent or vocalised? Are the numbers spelled out or a single number?
I suspect the final nail in the hard disk's coffin won't come from technical advances in SSDs, but when people start to realise they're being ripped off by an exponentially growing amount. We're up to 10% already.
Slashdot Mirror
720/1080 "standards" my ass! My 1080p TV is just a 1680x1050 monitor with some tuner hardware inside the case, and that's actually a good deal considering that a lot of HDTVs (even huge, expensive ones advertised as 1080p) are ripoffs running at 1366x768.
I'm waiting for DisplayPort to take over on the computer side - it might put an end to these lame 96DPI screens we've been stuck with for the past decade.
Whole disk? I've been using partitioned SD cards with UDF for ages now, what's wrong with doing that?
A performance pissing match has as much place in HTML/JS as it does in ODF and spreadsheet macros. Web 2.0 can fuck _right_ off.
The person who ported it took everything from the original game and released it on a newer platform. That is like someone taking Sonic the Hedgehog or Mario bros and porting it over with all the same graphics, sounds, and design.
You might have had a point with Nintendo, but Sega has never -- as far back as I can remember -- attacked its own fanbase like this. They turn a blind eye to ports (probably because they can't do it right themselves); most of the "collection" discs they put out on newer consoles are actually a shiny frontend around Gens.
Implying that being a developer means you know every single option in about:config
Implying that Flash developers lack the requisite brain cells to look it up on a search engine.
You might be on to something there.
The last digit of the acronym makes clear how much redundancy it has. They knew what they were doing when naming these.
Does that mean we won't be forced to use a flash-based clusterfuck that doesn't work half the time, like the BBC currently uses?
Google already serves most of its videos in the old Flash codec + H.264 + WebM, probably more for mobile too and that's without even counting the multi-resolution encodes for 1080/720p videos.
Turn on HTML5 mode, install flashblock and you won't see any ads on YT videos. The ones that do have ads are forced to use flash.
You're the one with no grasp on reality.
Do you seriously think people watching Youtube videos give a shit about microscopic differences in encoder quality?
Why are we using HTML5 and not XHTML 2?
HTML5 is more than vapourware, and provides new features that are useful to people making real-world websites.
XML abuses aside, XHTML is superior to HTML5.
That is not logically possible when XHTML is a subset of HTML5.
HTML5 requires a more complex parser than XHTML ever will.
Guess what? The real world isn't a pretty theoretical little flower. HTML5 defines consistent error handling for content on the existing internet, not the non-existent one.
XHTML can be validated for correctness, HTML5 is more difficult to do so.
The code exists for both already, so this is a moot point.
I honestly don't understand the reason for following the HTML route. XHTML is already in an industry understood format that tools already exist for.
Because we're sick of waiting decades for the fucking W3C to do anything. They've procrastinated themselves into irrelevance.
The market rarely reflects a superior technology. I still support XHTML. HTML5 is messy, ugly and a kludge.
Is BASIC also messy, ugly and a kludge to you? Would you say the world would be better off if C64s came with Haskell instead? Get real.
A what?
Gee, where have I seen this before?
So how do they measure a lost sale? Not even the RIAA can do that properly.
Or some seriously emaciated people.
OMFG! The government will know where I live!
And so will whoever "finds" the right laptop at the right time.
While they're at it, DOM Level 1 support would be nice. It's only a year older than IE6.
The firmware is reprogrammable, the display can do up to 0xFFFFFFF.
256 million should be enough. If it isn't, then use the 7 segments to represent one bit each.
Nouveau can render polygons now. It's roughly at where ATI support was about 4 years ago.
This is all very reminiscent of the events leading up to the Titanic disaster.
"Er... you're heading straight into an ice field ther-" /mode +m"
"LOL FUK OFF NOOB!!1
There's rumours that iptables might be going away eventually for this instead.
Now I'll admit I've never used *BSD, but even I can see iptables is *fucking awful* for anything more than the most basic IP/port matching. Hopefully this'll happen sooner rather than later.
But Rambus was (and still is) a patent troll. They deserved it.
Pro-tip: if you need a pronunciation guide, then you desperately need to pick a better name. Yes, better, as in "the current one sucks and should be taken out back and shot".
So, is the "dot" in "H.264" silent or vocalised? Are the numbers spelled out or a single number?
No thanks, I'll take an objective analysis over a rushed out piece of FUD from non-credible ffmpeg/x264 developers any day.
I suspect the final nail in the hard disk's coffin won't come from technical advances in SSDs, but when people start to realise they're being ripped off by an exponentially growing amount. We're up to 10% already.