For those of you just joining us from the twentieth century, the next phase of the reorientation tour: Apple. A hybrid of their earlier MP3 players with phone hardware, Apple's "I-phone" is among the top-selling smartphones on the market. Some of you may be familiar with "PDAs" from your millennium; modern "smartphones" are essentially PDAs merged with cell hardware built in.
Next on the tour: Paris Hilton. Who was she, and why the hell did anyone care?
Of course, I know there's a lot of work involved; like I said to justforgetme above, I was (mostly) joking about how long it seems to take. I realize it takes a lot of time to get everything right, and you need to do it right the first time or else everyone will support your broken version until the earth crashes into the sun. I'm just impatient and want my WebAudio NOW, dammit!:-)
Oh, sure, I realize it's a very complex task they have, I was speaking mostly in jest. I know I'm not alone in my frustration of their slower-than-molasses processes, but while I sometimes think they move too slow, I know they're still far more qualified for the job than I am. As you say, you can't break the old stuff with updates, and the new stuff you want to make sure you get right the first time.
As for Mozilla, I tried out some of their sound demos earlier today. They technically worked, but on my reasonably fast system I got slowdown, scratching, and lag. Meanwhile, the Chrome demos worked perfectly, even with a WebGL visualizer running on the page and 20 other tabs open. If this is the best Mozilla has to offer, I tend the think the Web Audio API is going to win this battle. That is, when the W3C eventually accepts it to the point other browsers begin implementing it, which if we're lucky will happen before HTML6 becomes the next big thing.
Replying to myself; I see below you're already aware of these. From two years ago. And it's still at the proposal stage.
It begs the question, what exactly is it the W3C does all day? Do they just spend all their time surfing the internet? And if so, wouldn't they want to approve this stuff faster so they'll have more ways to goof off?
Agreed, though progress is being made. Both Mozilla and Google have submitted proposals to the W3C, and already have some support in their browsers. Firefox uses the Audio Data API, and Chrome the Web Audio API. Obviously it'll be a while before one gets standardized (given the W3's track record, could be a very long time) and support becomes universal across browsers, but it's a start.
Top Gear is full of crap. I know someone who owns a Tesla Roadster, he regularly uses it in a 100-mile-plus commute and never comes close to running out the battery.
Have you seen Comcast's HD? It's compressed so much, some channels are barely any better than SD. I can't say anything about other cable providers, but if Comcast is your only option Netflix's HD is still far better.
-f causes ps to print the full command lines./[b]luefish/ will match "bluefish" but not "awk/[b]luefish/", because the [] characters are regex operators and are not part of the string that gets searched for.
Slashdot Mirror
Obligatory Big Bang Theory
For those of you just joining us from the twentieth century, the next phase of the reorientation tour: Apple. A hybrid of their earlier MP3 players with phone hardware, Apple's "I-phone" is among the top-selling smartphones on the market. Some of you may be familiar with "PDAs" from your millennium; modern "smartphones" are essentially PDAs merged with cell hardware built in.
Next on the tour: Paris Hilton. Who was she, and why the hell did anyone care?
So are the Wii and PS3. Well, the PS3 uses the Cell processor, but the instruction set is still PowerPC.
Indeed, I've found most of it to be an endless grind for coin. Character advancement is very slow, if it happens at all.
You mean like Nethack?
What if A and B are the same?
One might have already done that.
Of course, I know there's a lot of work involved; like I said to justforgetme above, I was (mostly) joking about how long it seems to take. I realize it takes a lot of time to get everything right, and you need to do it right the first time or else everyone will support your broken version until the earth crashes into the sun. I'm just impatient and want my WebAudio NOW, dammit! :-)
Oh, sure, I realize it's a very complex task they have, I was speaking mostly in jest. I know I'm not alone in my frustration of their slower-than-molasses processes, but while I sometimes think they move too slow, I know they're still far more qualified for the job than I am. As you say, you can't break the old stuff with updates, and the new stuff you want to make sure you get right the first time.
As for Mozilla, I tried out some of their sound demos earlier today. They technically worked, but on my reasonably fast system I got slowdown, scratching, and lag. Meanwhile, the Chrome demos worked perfectly, even with a WebGL visualizer running on the page and 20 other tabs open. If this is the best Mozilla has to offer, I tend the think the Web Audio API is going to win this battle. That is, when the W3C eventually accepts it to the point other browsers begin implementing it, which if we're lucky will happen before HTML6 becomes the next big thing.
Replying to myself; I see below you're already aware of these. From two years ago. And it's still at the proposal stage.
It begs the question, what exactly is it the W3C does all day? Do they just spend all their time surfing the internet? And if so, wouldn't they want to approve this stuff faster so they'll have more ways to goof off?
Agreed, though progress is being made. Both Mozilla and Google have submitted proposals to the W3C, and already have some support in their browsers. Firefox uses the Audio Data API, and Chrome the Web Audio API. Obviously it'll be a while before one gets standardized (given the W3's track record, could be a very long time) and support becomes universal across browsers, but it's a start.
Users who are shocked to learn their mouse has a second button.
Top Gear is full of crap. I know someone who owns a Tesla Roadster, he regularly uses it in a 100-mile-plus commute and never comes close to running out the battery.
For the ATM machine?
They support the video tag too. As in, the only reason you can watch YouTube on iOS.
Have you seen Comcast's HD? It's compressed so much, some channels are barely any better than SD. I can't say anything about other cable providers, but if Comcast is your only option Netflix's HD is still far better.
You can blame Dungeons and Dragons for that. I imagine if it never existed, today's WRPGs would be far different than they are.
Because they're colorful and cute, like pandas and dolphins. If they looked like flies or rats nobody would care.
-f causes ps to print the full command lines. /[b]luefish/ will match "bluefish" but not "awk /[b]luefish/", because the [] characters are regex operators and are not part of the string that gets searched for.
Believe it or not, the last one. http://www.wired.com/magazine/2011/05/ff_milk/
The best popcorn you have ever had. Add some tachyon sauce and you'll never go back.
You mean Portal 2: Episode 1. And by the time it comes out we'll be jacking into the Matrix to play games.
You tell me, they're your people.
So Microsoft is violently forcing people to use Windows? This explains a lot.
Good thing the "war on drugs" is being so effective at keeping it out of their hands, then.