Forgot your password?
typodupeerror

Comment: Re:Bullshit.... (Score 1) 127

by nine-times (#47561455) Attached to: A Fictional Compression Metric Moves Into the Real World
Well no, the metric is real. The question would be whether it's useful or meaningful. You originally implied that it wasn't because:

A "combined score" for speed and ratio is useless, as that relation is not linear.

It seems now that it's not about the relation being linear, but about something else that you won't say. I'm afraid I'm not closer to understanding.

Comment: Re: Bullshit.... (Score 1) 127

by nine-times (#47561433) Attached to: A Fictional Compression Metric Moves Into the Real World

Decompression time is always real time? So it doesn't matter what computer, what processor, the size of the file, the complexity of the file, or even what kind of file it is? Or do you mean that it needs to be able to be done in real-time (or faster) for some particular use a a particular kind of file on a particular platform that you have in mind?

Comment: Re: Bullshit.... (Score 1) 127

by nine-times (#47557039) Attached to: A Fictional Compression Metric Moves Into the Real World

Ok, so let's start from where you're wrong that "What's important is to save space when broadcasting the content." There are other important things.

Next, what would you like to do then? Change this benchmark to measure decompression speed rather than compression speed? Sure, fine. Let's do that.

Comment: Re:Bullshit.... (Score 1) 127

by nine-times (#47556531) Attached to: A Fictional Compression Metric Moves Into the Real World

I find it surprising and almost funny how much ire this has drawn from people with some kind of weird "purist" attitude about the whole thing.

It doesn't seem "generally useless" to me, but it would be more appropriate to say that it's "useful only in general cases". I would say that in most circumstances, I'd want compression algorithms that balance speed and compression. I often don't zip my files to maximum compression, for example, because I don't want to sit around waiting for a long time in order to save a very small amount of space. I also don't zip without compression, because speed is not that *that* important. I look for compression that's balanced. "Compress it as much as you can without making me sit around and wait for it."

Similarly, if I were ripping CDs to MP3, and you offered me a different format that would save me 1MB per song, I'd jump on board. If you told me that it would save me that space by requiring 1 hour to compress, and then another hour to decompress before I could play it, I'd tell you to fuck off. If you told me it would drain my battery life on my phone to play it, I'd say it's not worth the trouble.

So I don't know if this is the right metric or the most useful metric, but certainly there could be a metric for compression that deals with "total space savings" vs. "time and complexity in compressing and decompressing". Such a metric could actually be a solid indicator of which compression is useful in a vague general sense.

Comment: Re:Bullshit.... (Score 1) 127

by nine-times (#47556473) Attached to: A Fictional Compression Metric Moves Into the Real World

How much time it takes to compress is irrelevant, even if you get diminishing returns the longer you take. What's important is to save space when broadcasting the content.

Well, and also that it can be decompressed quickly and with little processing power, or else with enough hardware support that it doesn't matter. Otherwise, it'd take a long time to access and drain power on mobile devices.

Comment: Re:Bullshit.... (Score 1) 127

by nine-times (#47554873) Attached to: A Fictional Compression Metric Moves Into the Real World

Hence a single score is completely unsuitable to address the "quality" of the algorithm, because there is no single benchmark scenario.

So you're saying that no benchmark is meaningful because no single benchmark can be relied upon to be the final word under all circumstances? By that logic, measuring speed is not meaningful, because it's not the final word in all circumstances. Measuring the compression ratio is meaningless because it's not the final word in all circumstances. The footprint of the code is meaningless because it's not the final word in all circumstances.

Isn't it possible that a benchmark could be useful for some purposes other than being the final word in all circumstances?

Comment: Re:Bullshit.... (Score 1) 127

by nine-times (#47554857) Attached to: A Fictional Compression Metric Moves Into the Real World

Depending on what you're talking about, providing a huge table of every possible test doesn't make for easy comparisons. In the case of graphics cards, I suppose you could provide a list of every single game, including framerates on every single setting on every single game. It would be hard to gather all that data, and the result would be information overload, and it still wouldn't allow you to make a good comparison between cards. Even assuming you ad such a table, it would probably be more helpful to add or average the results somehow, providing a cumulative score. Of course, then you might want to weight the scores, possibly based on how popular the game is, or how representative it is of the actual capabilities of the card. But if that's the result that's actually helpful, why not design a single benchmark that's representative of what games do, rather than having to test so many games?

Comment: Re:Bullshit.... (Score 1) 127

by nine-times (#47554827) Attached to: A Fictional Compression Metric Moves Into the Real World

there's not a meaningful way to pick the "best" in that group that everyone will agree on

Metrics often don't provide a definitive answer about what the best thing is, with universal agreement. If I tell you Apple scores highest in customer satisfaction for smartphones last year, does that mean everyone will agree that the iPhone is the best phone? If a bunch of people are working at a helpdesk, and one closes the most tickets per hour, does that necessarily mean that he's the best helpdesk tech?

It's true that a lot of people misuse metrics, thinking that they always provide an easy answer, without understanding what they actually mean. That doesn't mean that metrics are useless.

If you're comparing a bunch of cars that get 32-35 mpg and go 130-140 mph, there's not a meaningful way to pick the "best" in that group that everyone will agree on

Yeah, but that's a really dumb metric since most people don't actually care what the top speed of a car is. Or to be more truthful, only morons care about top speed unless it's below 80mph, since you basically shouldn't be driving your car that fast. So really, in a metric like this, the "top speed" isn't a metric of "faster is better". It's a metric of "fast enough is good enough".

But if you were in the habit of doing car reviews, it might make sense to take a bunch of assessments, qualitative and quantitative, like acceleration and handling, MPG, physical attractiveness, additional features, and price (lower is better), and then weigh and average each score. That would enable you to come up with a final score which, while subjective, makes some attempt to enable an overall ranking of the cars. In fact, this is the sort of thing that reviewers sometimes do.

Comment: Re:Bullshit.... (Score 3, Insightful) 127

by nine-times (#47553917) Attached to: A Fictional Compression Metric Moves Into the Real World

Since the "correct" weighting is a matter of opinion and everybody's use-case is different, a single-dimension metric isn't very useful...[snip] User A is trying to stream stuff that has to have latency less than 15 seconds, so for him the first algorithm is the best.

And these are very good arguments why such a metric should not be taken as an end-all be-all. Isn't that generally the case with metrics and benchmarks?

For example, you might use a benchmark to gauge the relative performance between two video cards. I test Card A and it gets 700. I test Card B and it gets a 680. However, in running a specific game that I like, Card B gets slightly faster framerates. Meanwhile, some other guy wants to use the video cards to mine Bitcoin, and maybe these specific benchmarks test entirely the wrong thing, and Card C, which scores 300 on the benchmark, is the best choice. Is the benchmark therefore useless?

No, not necessarily. if the benchmark is supposed to test general game performance, and generally faster benchmark tests correlate with faster game performance, then it helps shoppers figure out what to buy. If you want to shop based on a specific game or a specific use, then you use a different benchmark.

Comment: Explains some things (Score 4, Interesting) 234

Maybe these fliers were honest, and Comcast just believes the investing in an ISP is a money-losing venture. It would explain some things.

I guess the only sensible response is to sell your stock in Comcast. They view their own business as a money-pit and a disaster waiting to happen.

Comment: Re:Bullshit.... (Score 4, Insightful) 127

by nine-times (#47553137) Attached to: A Fictional Compression Metric Moves Into the Real World

Can you explain in more detail?

I'm not an expert here, but I think the idea is to come up with a single quantifying number that represents the idea that very fast compression has limited utility if it doesn't save much space, and very high compression has limited utility if it takes an extremely long time.

Like, if you're trying to compress a given file, and one algorithm compressed the file by 0.00001% in 14 seconds, another compressed the file 15% in 20 seconds, and the third compressed it 15.1% in 29 hours, then the middle algorithm is probably going to be the most useful one. So why can't you create some kind of rating system to give you at least a vague quantifiable score of that concept? I understand that it might not be perfect-- different algorithms might score differently on different sized files, different types of files, etc. But then again, computer benchmarks generally don't give you a perfect assessment of performance. It just provides a method for estimating performance.

But maybe you have something in mind that I'm not seeing.

Comment: Re:Can we just recognize it as currency and be don (Score 1) 154

by nine-times (#47551675) Attached to: US States Edge Toward Cryptocoin Regulation

Does it really qualify as a currency yet? I don't know. How do we define what makes a currency?

And don't misunderstand me. I'm not trying to claim that bitcoins aren't worth anything. But Garbage Pail Kids trading cards are probably still worth something. There may be someone in the world who would accept them as payment for goods and services. Does that make them a currency?

Does a currency need to be backed by some kind of country? Is there an expectation of stability of price? Do you need an area of economic activity where the currency is ubiquitously accepted as a form of payment? Maybe you know the answers to these questions. I don't. There are probably a lot of people in Congress who don't.

Comment: Re:No need for a conspiracy (Score 1) 275

Though I don't remember Apple being explicit about it, it seems that their OS updates support the past 3 models. iOS7 was released when the iPhone 5s had not yet been released, and supported the iPhone 4, iPhone 4s, and iPhone 5. You can still buy an iPhone 4s, so I would expect that iOS8 will support it, but will not support the iPhone 4 anymore.

So you will probably be able to upgrade your current phone, though it'll probably be a bit slow and will lack some features. That's just an educated guess, though.

Comment: Re:The only good thing (Score 1) 474

Yes.

And please note, in case you don't understand how comparisons work, that you don't compare things that are identically the same. They're the same, so it doesn't make sense to compare them. You also don't compare things that are so similar that people have a hard time understanding the differences. In those cases, it's much more meaningful to contrast them.

The only time it really makes sense to compare things is if they're significantly different and yet have similarities. Coffee and amphetamine are very different, and yet both are addictive stimulants that lots of people use in order to be productive. That makes for an interesting comparison.

If at first you don't succeed, you must be a programmer.

Working...