It doesn't have anywhere near the features of amarok 1.4. It calls itself a "port", but as far as I can tell that's a lie; it neither looks like amarok 1.4 nor plays the same.
I switched to freebsd so I could keep using amarok 1.4; I plan on doing an actual port of amarok 1.4 to qt4 when I've time.
trying to instill it in a child is likely (but not guaranteed) to help them in life.
A simple correlation doesn't imply that instilling it is going to help. Maybe those children with naturally high self-control are going to succeed, and efforts to instill it make no difference, or are even harmful.
So, an interesting result, but more research needed before we can turn it into parenting advice.
a lot of you are disliking the sequels, and bashing them, because at that point the movie had had become popular in mainstream and everyone was talking about it.
Look in the mirror dude. "Everyone" loves the first film, and hates the other two, so that argument doesn't hold water; rather, you're the one taking a contra-mainstream position so you look "hip".
It's funny because it's actually true. Not that slashdot will believe it for another decade or so (not that I blame them with the kind of crap MS has pulled in the past).
Some countries have crazy software patents, so who knows? But that's the same for any decent video compression format. Sure, google claim VP8 is clean, but the claim hasn't withstood a lot of scrutiny yet, and they're not offering indemnification.
I think it may be a little more complicated than this.
No. It's not complicated.
I think the hole in your logic may be that 0.333... == 1/3. I think 0.333... may only be a very close numerical approximation of 1/3, but 1/3 cannot be expressed absolutely as a number (even assuming infinite 3s).
No. 0.333... == 1/3 by definition; that's what the notation means. You're thinking about this wrong; a decimal isn't a "numerical approximation", it's notation for, well, if you want to get technical about it then the notion of a Dedekind cut may help.
The thing is, if the credit is spent on cleanup, and removes as much as it permits one to emit, that's actually just fine, and will provide exactly the right framework to let the free markets I'm sure you love find the most efficient solutions to carbon emissions.
The impact of allied codebreaking during WW2 is vastly overestimated. During the most intense parts of the battle of the atlantic in 1941 and 42, we couldn't actually break the naval enigma, the most relevant one. It didn't change the eventual outcome.
It's a shame that wikipedia has ceased to be
"somewhere you can find anything, no matter how obscure". Nowadays I tend to Tv Tropes instead, with its "no such thing as notability" policy - even for real-world things, you've more chance of getting a useful article.
Everyone can suggest improvements to VP8 but is not necessarily listened to, hence VP8 is closed.
Everyone can suggest improvements to h264 but is not necessarily listened to, hence 264 is open.
Well leaving aside the fact that the bitstreams are now fixed so there's no way improvements will make it into either, H264: Everyone can suggest improvements, the group as a whole votes on whether to accept them, therefore open. VP8: Everyone can suggest improvements, google unilaterally decides whether to accept them, therefore closed.
Face it, h264 development certainly isn't one bit more open than VP8's right now.
Development has finished in both cases - and while development was happening for VP8 it was entirely closed, while that for h264 was open.
By the way, am I allowed to fork h264 and make my own codec?
That article's written as if digital downloads have already killed physical music sales. But my local HMV's alive and well. So how true is its "we all know how that one played out"?
The aether was exactly the same thing - an explanation for the real observation that light behaved like a propagating wave. It was perfectly legitimate science too. The situations are quite similar.
In order for the human owners of the company to be able to do so much as buy a car with the profits they have to pay themselves out of the company first, and at that point they get taxed far more "2.4%", in fact they get taxed much higher than your 30%.
Really? Don't they take their profits in stock, and thereby avoid paying on that too?
Even if you had a time machine, you still couldn't contribute anything to the VP8 "standard" - it was developed entirely by that single company, and now the bitstream has been fixed and google are not accepting improvements or even obvious bugfixes. Wheras h264 was a real ISO standard - everyone was welcome to speak (though of course not necessarily be listened to) in the standardization discussions, and every country got to vote.
(Well, almost; the ASF's implementation may or may not work, but they can't possibly show that it does because they don't have access to the test cases and never will. There are also a couple of nominally separate implementations - but IME they are all derived from the Oracle one to the extent that they all have the same bugs).
Even if you require "porn" to be more explicitly sexual, the basic problem remains: a 16-year-old girl can still send such a picture to your phone and thus destroy your life.
Even without apps, sites introduced specialized versions of their content for mobile phones -- not just to reduce the data size per page, but to make it pages suitable to the smaller screen by eliminating (or minimizing) less-important information that took up either significant data or significant screen space.
Those were changes that they should've made anyway. I actually set my user agent on my desktop browser to spoof an iphone for a while - it's amazing (and sad) how much nicer it makes sites.
to treat content on on a device with multitouch on 9" screen in the exact same manner as content on a device with keypad-only inputs and a 2.5" screen is in many cases going to make the experience worse for users of one or both devices.
The point of HTML is that you provide the content, and the device displays it in the way most appropriate to it.
Slashdot Mirror
I switched to freebsd so I could keep using amarok 1.4; I plan on doing an actual port of amarok 1.4 to qt4 when I've time.
So KDE is now a "software compilation"? What was wrong with "desktop environment"?
A simple correlation doesn't imply that instilling it is going to help. Maybe those children with naturally high self-control are going to succeed, and efforts to instill it make no difference, or are even harmful.
So, an interesting result, but more research needed before we can turn it into parenting advice.
Look in the mirror dude. "Everyone" loves the first film, and hates the other two, so that argument doesn't hold water; rather, you're the one taking a contra-mainstream position so you look "hip".
Even if we assume there's a difference, you're being very naive there. This has been going on since history began.
It's funny because it's actually true. Not that slashdot will believe it for another decade or so (not that I blame them with the kind of crap MS has pulled in the past).
Some countries have crazy software patents, so who knows? But that's the same for any decent video compression format. Sure, google claim VP8 is clean, but the claim hasn't withstood a lot of scrutiny yet, and they're not offering indemnification.
No. It's not complicated.
I think the hole in your logic may be that 0.333... == 1/3. I think 0.333... may only be a very close numerical approximation of 1/3, but 1/3 cannot be expressed absolutely as a number (even assuming infinite 3s).
No. 0.333... == 1/3 by definition; that's what the notation means. You're thinking about this wrong; a decimal isn't a "numerical approximation", it's notation for, well, if you want to get technical about it then the notion of a Dedekind cut may help.
The thing is, if the credit is spent on cleanup, and removes as much as it permits one to emit, that's actually just fine, and will provide exactly the right framework to let the free markets I'm sure you love find the most efficient solutions to carbon emissions.
The impact of allied codebreaking during WW2 is vastly overestimated. During the most intense parts of the battle of the atlantic in 1941 and 42, we couldn't actually break the naval enigma, the most relevant one. It didn't change the eventual outcome.
It's a shame that wikipedia has ceased to be "somewhere you can find anything, no matter how obscure". Nowadays I tend to Tv Tropes instead, with its "no such thing as notability" policy - even for real-world things, you've more chance of getting a useful article.
I hold all browsers to the same standard. And FF consumes more memory and is more generally sluggish than any of the rest of them. Including IE.
Well leaving aside the fact that the bitstreams are now fixed so there's no way improvements will make it into either, H264: Everyone can suggest improvements, the group as a whole votes on whether to accept them, therefore open. VP8: Everyone can suggest improvements, google unilaterally decides whether to accept them, therefore closed.
Face it, h264 development certainly isn't one bit more open than VP8's right now.
Development has finished in both cases - and while development was happening for VP8 it was entirely closed, while that for h264 was open.
By the way, am I allowed to fork h264 and make my own codec?
Yes, of course.
That article's written as if digital downloads have already killed physical music sales. But my local HMV's alive and well. So how true is its "we all know how that one played out"?
The aether was exactly the same thing - an explanation for the real observation that light behaved like a propagating wave. It was perfectly legitimate science too. The situations are quite similar.
Really? Don't they take their profits in stock, and thereby avoid paying on that too?
Even if you had a time machine, you still couldn't contribute anything to the VP8 "standard" - it was developed entirely by that single company, and now the bitstream has been fixed and google are not accepting improvements or even obvious bugfixes. Wheras h264 was a real ISO standard - everyone was welcome to speak (though of course not necessarily be listened to) in the standardization discussions, and every country got to vote.
You can, but only by replacing them with hundreds of thousands of lines of XML.
(Well, almost; the ASF's implementation may or may not work, but they can't possibly show that it does because they don't have access to the test cases and never will. There are also a couple of nominally separate implementations - but IME they are all derived from the Oracle one to the extent that they all have the same bugs).
The GP's point was that anyone who knows all that will certainly know what an API is.
You don't think that's something anyone who's seen your facebook profile could guess?
Even if you require "porn" to be more explicitly sexual, the basic problem remains: a 16-year-old girl can still send such a picture to your phone and thus destroy your life.
They were. But since they've had to break all the protections to do that, pirates now have free reign.
That wouldn't have been reasonable.
Those were changes that they should've made anyway. I actually set my user agent on my desktop browser to spoof an iphone for a while - it's amazing (and sad) how much nicer it makes sites.
to treat content on on a device with multitouch on 9" screen in the exact same manner as content on a device with keypad-only inputs and a 2.5" screen is in many cases going to make the experience worse for users of one or both devices.
The point of HTML is that you provide the content, and the device displays it in the way most appropriate to it.