It means exactly what I think it means. Apparently you think it means something else. Opera is #1 on mobile devices worldwide, and the #1 browser in more countries than any other besides Internet Explorer. Every Wii on the planet has Opera on it, as well.
So pretty much hugely successful. A credit to the team.
How about you show someplace where Opera claimed they had trouble with performance on Acid3? I suspect that you jumped to a conclusion when Opera announced *passing Acid3* but that there were "still some issues." You apparently decided what those issues were without evidence.
How about this. Download an run Opera. Now download and run Safari. See how fast Opera is compared to Safari? Notice how there is a noticeable pause at 69/100 on Safari, but not on Opera? Thanks. It seems to me like Safari still fails, even though I accept their claim that they passed.
Opera 8 was the version where they began calling it UserJS. The functionality, however, was mostly complete and usable in 7 but was there for other reasons (for fixing broken sites.) It is because users started using the feature for things other than fixing broken sites that they evolved it into a complete system.
opera has a surprisingly large market share on various embedded devices (as you mentioned) and in included on very large share of mobile devices.
Surprisingly large is an understatement. Opera is #1 on embedded devices by a very large margin (as in over 50% market share.) The rest of the alternatives combined would still be a minority, and this is the case because the competition doesn't have a clue about the importance of memory footprint on these devices. Opera is cheaper for the manufacturers than the alternatives.
For the most part, only the trendy high priced gadgets use something other than Opera.
I remember when many claimed that Opera rendered pages wrong. Over time, the other browsers have slowly moved to a position where they render those same pages "wrong."
This isnt to say that Opera doesnt have issues with standards.. all browsers do.. but time and again many complaints have been because Opera wasn't rendering incorrectly.
Well I can tell you that the Opera 10 alpha rendered it very quickly, well under a second on my 2ghz system, on the day it was announced.
But honestly.. you seem to be claiming that Opera has not passed the test, since you "have still not seen Opera claim [that] they pass the performance aspect of the test?" Really?
But I want to be honest here, in that you failed to cite the first instance of safari passing it, and guess who came first? It was a tie. They both announced on the exact same day.
For example, when FireFox users created an extension called GreaseMonkey so that they had the same functionality that already existed in Opera known as User JavaScript.
Opera's "support" for GreaseMonkey extends only so far as to support some of the proprietary bullshit that GreaseMonkey introduced due to limitations in FireFox's DOM support.
Some of the proprietary bullshit that isn't implemented in Opera is FireFox specific, such as
allowing a script to manipulate FireFox menus (what could possibly go wrong?)
or outright stupid (no cross-domain protections with greasemonkey's xmlhttprequest, what could possibly go wrong?)
What pisses me off is that some of the failings of FireFox (bugs they were too lazy to fix, after years of being told) have made it into the HTML5 specification... thanks mozilla asshats.. good to see you have so much control over the W3C
Sometimes the specific single letter has standardized usage, such as i and j, x and y, and so forth.
Then there are cases where the best name for a variable is something like 'value', 'string', 'data', 'array', or 'pointer' where using those instead of a single character doesnt help anybody.
Library programmers are more familiar with using single letters, because many variables are often entirely abstract and simply dont have a concrete meaning. What should you call the input to a sort function? 'arrayToBeSorted', or simply 'a'?
I have not looked at the code in question, so maybe he/they are using single letter names obsessively or something.. but I know that when I'm programming, often times a single letter is just as descriptive as anything else.
$2300 is considerably less than what an unmotorized high-end bicycle costs.
Just because some people are idiots that will spend several thousand dollars on a freaking bicycle does not testify to the practicality of the cost of e-bikes.
The median household income in the United States is about $50,000. That $2,300 bicycle of yours is 4.6% of the houses income. This is almost 2.5 *weeks* of income for the entire household, for a bicycle.
Thats insane considering the alternatives. I can find a used *car* for that price.
The same reason that FORTRAN is still used worldwide. You pick a theory, and then you run with it. Changing theories willy-nilly along the way is, far more often than not, stupid.
So after Gizmo #1 requires Thingamajig 6.0, Gizmo #2 is best to also require Thingamajig 6.0.
...after all.. you have Thingamajig 6.0 deployed everywhere to support Gizmo #1.
You win. We just don't care enough, and this fact is not something that can be changed, because we REALLY don't care in almost every case. My conversations on the phone are generally private, but not worthy of "secret" status, and thats all there is to it.
The same is true for what I do on the Internet. In almost every case privacy is preferred but its not "secret worthy."
My beef with VLC is that there are many H264 shoutcast video streams that it fails to play correctly. Specifically the stream will pause/skip every few seconds and no amount of tweaking seems to be able to fix it, and its not a bandwidth/buffering issue because WinAmp plays these same streams just fine for hours without even a single instance of the phenomena.
For awhile I was suspecting that maybe my computers clock ran slow or fast or something, causing the issue.. I tried to produce experimental evidence to support this theory but failed to do so. Specifically the PIT, HPET, and RDTSC (on each core) all agreed about the time to well within a tolerance that made the theory implausible.
So my conclusion is that there is something fundamentally wrong with VLC's shoutcast+H264 streaming playback.
Like most machine learning of this kind, I presume that its a popularity contest. One page with "wkjh wkfbw oizxz zxhlzx" isnt going to count. But a million pages with "I for one welcome our new..." is going to score some influence.
I dont want to foot the bill for people in flood regions when the river misbehaves, just like I don't want to foot the bill for people on the coast when the ocean misbehaves.
Next up: People living next to an active volcano situated on a fault line on a river basin that is somehow under sea level on a hill where mudslides are common, want help.
Smaller is better in many cases, but not all. For example, using the small 'loop' opcode is a bigtime performance fail on the average x86 desktop of today (still highly biased towards Athlon64 and Pentium4) and that was even true back in the days of the 80386
Back in the 8088 days, ENTER / LEAVE were preferred for stack frames, and then somewhere around the 80386 is became better to PUSH EBP.. MOV EBP, ESP / POP EBP.. and now again ENTER and LEAVE are preferred (this time, for their size)
But the killer fun fact of this post is that assembly language programmers don't often use stack frames. Stack frames are for debuggers so that the debugger can figure out whats going on during a break and how the machine code relates to the high level source code. Assembly language programmers dont need to relate to high level source code.. the machine code is the code.. assembly language programmers calculate where parameters are on the stack directly relative to the current stack pointer, rather than create a stack frame. This saves, on average, several cycles per function call.
Slashdot Mirror
It means exactly what I think it means. Apparently you think it means something else. Opera is #1 on mobile devices worldwide, and the #1 browser in more countries than any other besides Internet Explorer. Every Wii on the planet has Opera on it, as well.
So pretty much hugely successful. A credit to the team.
How about you show someplace where Opera claimed they had trouble with performance on Acid3? I suspect that you jumped to a conclusion when Opera announced *passing Acid3* but that there were "still some issues." You apparently decided what those issues were without evidence.
How about this. Download an run Opera. Now download and run Safari. See how fast Opera is compared to Safari? Notice how there is a noticeable pause at 69/100 on Safari, but not on Opera? Thanks. It seems to me like Safari still fails, even though I accept their claim that they passed.
Opera 8 was the version where they began calling it UserJS. The functionality, however, was mostly complete and usable in 7 but was there for other reasons (for fixing broken sites.) It is because users started using the feature for things other than fixing broken sites that they evolved it into a complete system.
opera has a surprisingly large market share on various embedded devices (as you mentioned) and in included on very large share of mobile devices.
Surprisingly large is an understatement. Opera is #1 on embedded devices by a very large margin (as in over 50% market share.) The rest of the alternatives combined would still be a minority, and this is the case because the competition doesn't have a clue about the importance of memory footprint on these devices. Opera is cheaper for the manufacturers than the alternatives.
For the most part, only the trendy high priced gadgets use something other than Opera.
..you mean standards compliant?
I remember when many claimed that Opera rendered pages wrong. Over time, the other browsers have slowly moved to a position where they render those same pages "wrong."
This isnt to say that Opera doesnt have issues with standards.. all browsers do.. but time and again many complaints have been because Opera wasn't rendering incorrectly.
Well I can tell you that the Opera 10 alpha rendered it very quickly, well under a second on my 2ghz system, on the day it was announced.
But honestly.. you seem to be claiming that Opera has not passed the test, since you "have still not seen Opera claim [that] they pass the performance aspect of the test?"
Really?
Its not such a bad thing to be the last browser to successfully sell copies in a market full of increasing numbers of free alternatives.
Opera had it first. Really.
Opera did it before that
But I want to be honest here, in that you failed to cite the first instance of safari passing it, and guess who came first? It was a tie. They both announced on the exact same day.
For example, when FireFox users created an extension called GreaseMonkey so that they had the same functionality that already existed in Opera known as User JavaScript.
Opera's "support" for GreaseMonkey extends only so far as to support some of the proprietary bullshit that GreaseMonkey introduced due to limitations in FireFox's DOM support.
Some of the proprietary bullshit that isn't implemented in Opera is FireFox specific, such as
allowing a script to manipulate FireFox menus (what could possibly go wrong?)
or outright stupid (no cross-domain protections with greasemonkey's xmlhttprequest, what could possibly go wrong?)
What pisses me off is that some of the failings of FireFox (bugs they were too lazy to fix, after years of being told) have made it into the HTML5 specification... thanks mozilla asshats.. good to see you have so much control over the W3C
Sometimes the specific single letter has standardized usage, such as i and j, x and y, and so forth.
Then there are cases where the best name for a variable is something like 'value', 'string', 'data', 'array', or 'pointer' where using those instead of a single character doesnt help anybody.
Library programmers are more familiar with using single letters, because many variables are often entirely abstract and simply dont have a concrete meaning. What should you call the input to a sort function? 'arrayToBeSorted', or simply 'a'?
I have not looked at the code in question, so maybe he/they are using single letter names obsessively or something.. but I know that when I'm programming, often times a single letter is just as descriptive as anything else.
$2300 is considerably less than what an unmotorized high-end bicycle costs.
Just because some people are idiots that will spend several thousand dollars on a freaking bicycle does not testify to the practicality of the cost of e-bikes.
The median household income in the United States is about $50,000. That $2,300 bicycle of yours is 4.6% of the houses income. This is almost 2.5 *weeks* of income for the entire household, for a bicycle.
Thats insane considering the alternatives. I can find a used *car* for that price.
The same reason that FORTRAN is still used worldwide. You pick a theory, and then you run with it. Changing theories willy-nilly along the way is, far more often than not, stupid.
...after all.. you have Thingamajig 6.0 deployed everywhere to support Gizmo #1.
So after Gizmo #1 requires Thingamajig 6.0, Gizmo #2 is best to also require Thingamajig 6.0.
ding!
You win. We just don't care enough, and this fact is not something that can be changed, because we REALLY don't care in almost every case. My conversations on the phone are generally private, but not worthy of "secret" status, and thats all there is to it.
The same is true for what I do on the Internet. In almost every case privacy is preferred but its not "secret worthy."
My beef with VLC is that there are many H264 shoutcast video streams that it fails to play correctly. Specifically the stream will pause/skip every few seconds and no amount of tweaking seems to be able to fix it, and its not a bandwidth/buffering issue because WinAmp plays these same streams just fine for hours without even a single instance of the phenomena.
For awhile I was suspecting that maybe my computers clock ran slow or fast or something, causing the issue.. I tried to produce experimental evidence to support this theory but failed to do so. Specifically the PIT, HPET, and RDTSC (on each core) all agreed about the time to well within a tolerance that made the theory implausible.
So my conclusion is that there is something fundamentally wrong with VLC's shoutcast+H264 streaming playback.
When I first began to program I used 8 space tab stops.
Somewhere along the way I dropped it down to 4 space tab stops and I think that was when I started sing 80x50 text screens instead of 80x25.
I now use 2-space tab's and I think almost certainly its because I get so many more lines of code on the screen due to high resolution GUI's.
Like most machine learning of this kind, I presume that its a popularity contest. One page with "wkjh wkfbw oizxz zxhlzx" isnt going to count. But a million pages with "I for one welcome our new ..." is going to score some influence.
which is another debate over stupidity for another thread
Bullshit. This is slashdot.. we debate stupidity wherever and whenever we want!
So now that I won my own combat jets, anybody got a slightly used aircraft carrier up for sale?
Thats exactly it as far as I am concerned.
I dont want to foot the bill for people in flood regions when the river misbehaves, just like I don't want to foot the bill for people on the coast when the ocean misbehaves.
Next up: People living next to an active volcano situated on a fault line on a river basin that is somehow under sea level on a hill where mudslides are common, want help.
you're still missing 7,700,000,000 people out of 8,000,000,000
Why do you want to turn this into a debate about illegal aliens?
Isnt the point of search engines to manipulate the results?
..because even when AMD was price AND performance king of the x86 CPU, Intel still sold more due to market manipulation.
Thats one of the reasons that we have Tax ID's. So that members of other tribes can also be part of the wonderful Social Security Number experience.
Smaller is better in many cases, but not all. For example, using the small 'loop' opcode is a bigtime performance fail on the average x86 desktop of today (still highly biased towards Athlon64 and Pentium4) and that was even true back in the days of the 80386
.. MOV EBP, ESP / POP EBP .. and now again ENTER and LEAVE are preferred (this time, for their size)
.. the machine code is the code .. assembly language programmers calculate where parameters are on the stack directly relative to the current stack pointer, rather than create a stack frame. This saves, on average, several cycles per function call.
Back in the 8088 days, ENTER / LEAVE were preferred for stack frames, and then somewhere around the 80386 is became better to PUSH EBP
But the killer fun fact of this post is that assembly language programmers don't often use stack frames. Stack frames are for debuggers so that the debugger can figure out whats going on during a break and how the machine code relates to the high level source code. Assembly language programmers dont need to relate to high level source code