The article is very low on details. I read it and I'm still not sure how it works, whom it affects and what I can do to protect myself (obviously, since I don't know how it works).
It would have been nice if they went into some more detail for technical users.
I totally agree with the AJAX part. AJAX isn't inherently bad, it was just overused. Also, coming back to the article, why is the author comparing a framework to a language? I bet he could do everything he wanted in Ruby as easily as with PHP if he hadn't used Rails (I don't know Ruby, but I know you can do it in Python without using any frameworks).
The complexity for minimum component costs has increased at a rate of roughly a factor of two per year... Certainly over the short term this rate can be expected to continue, if not to increase. Over the longer term, the rate of increase is a bit more uncertain, although there is no reason to believe it will not remain nearly constant for at least 10 years. That means by 1975, the number of components per integrated circuit for minimum cost will be 65,000. I believe that such a large circuit can be built on a single wafer.
That's from Wikipedia. He actually said that the cost would halve every year.
I don't understand the PlaysForSure name. Seeing PlaysForSure is a surefire indication that it doesn't play on most media. That's not what I don't understand, though. I don't understand why they would THINK it plays for sure? It's like saying "mp3 MIGHT play on this, but our format PlaysForSure!" What were they thinking, can anyone explicate?
That's true, but I'd rather not spend three days pressing the "next" arrow 800 times like I did with my MuVo. Much faster to go to the song's general vicinity and slow down.
It's not actually integration with iTunes (it's the most bloated piece of crap I've seen since RealPlayer), but the fact that there is any integration at all, i.e. a database of songs you can search and sort any way you want. Plus there's a really intuitive interface to control it. If there was another company that had that I'd buy its offer, I don't like Apple's overpriced hardware.
If it has to do with paths, it's in os.path. If it has to do with the OS in general, it's in OS. If it has to do with strings it's in string, and with regular expressions in re. What's so hard? The only two libraries in the whole of python that one might confuse are sys and path, and besides, why would you confuse two libraries? What are the docs for?
According to Guido the language differences aren't going to be so huge that code can't be ported, I think he said that something like 90% is going to already run, and there will be tools to help you locate and convert the other 10%.
Slashdot Mirror
Too bad privacy and the number of people you can call are inversely proportionate :/
Or one more, depending on how you count it.
You know that it's not mandatory for you to run this program, right?
Ig-pay atin-lay.
I use Opera, does this mean I am forever doomed to fall in the hands of every internet predator that comes along?
I still need the exact information if I am to make any informed decisions about my browsing habits.
The article is very low on details. I read it and I'm still not sure how it works, whom it affects and what I can do to protect myself (obviously, since I don't know how it works).
It would have been nice if they went into some more detail for technical users.
It's personalized because different countries have different cultures. The fact that we use the same currency doesn't mean it can't be personalised.
Didn't you hear? The "Canadian dollar" jokes were switched for "American dollar" jokes recently.
I totally agree with the AJAX part. AJAX isn't inherently bad, it was just overused. Also, coming back to the article, why is the author comparing a framework to a language? I bet he could do everything he wanted in Ruby as easily as with PHP if he hadn't used Rails (I don't know Ruby, but I know you can do it in Python without using any frameworks).
The whole article is just a bad comparison.
Mmm, class action suit, baby!
As a Greek, I'd like some remuneration for founding civilization please (democracy is a freebie). You guys have been mooching off us too long!
Or this. This one is actually more on target.
Like many people have said before me, if she had Linux you would be singing a very different tune!
No, you miscalculated by a factor of SUCK!
:/)
(Hah
That's from Wikipedia. He actually said that the cost would halve every year.
How will S3 work for storing anything other than static media?
I don't understand the PlaysForSure name. Seeing PlaysForSure is a surefire indication that it doesn't play on most media. That's not what I don't understand, though. I don't understand why they would THINK it plays for sure? It's like saying "mp3 MIGHT play on this, but our format PlaysForSure!" What were they thinking, can anyone explicate?
That's true, but I'd rather not spend three days pressing the "next" arrow 800 times like I did with my MuVo. Much faster to go to the song's general vicinity and slow down.
It's not actually integration with iTunes (it's the most bloated piece of crap I've seen since RealPlayer), but the fact that there is any integration at all, i.e. a database of songs you can search and sort any way you want. Plus there's a really intuitive interface to control it. If there was another company that had that I'd buy its offer, I don't like Apple's overpriced hardware.
It's the scrollwheel.
I have only read the first book of the series and found it quite great. Does it get worse later on? Why are you saying this?
Knowing Comcast, you should probably assume the average song size to be about 300 KB.
I meant sys and os, sorry about that.
If it has to do with paths, it's in os.path. If it has to do with the OS in general, it's in OS. If it has to do with strings it's in string, and with regular expressions in re. What's so hard? The only two libraries in the whole of python that one might confuse are sys and path, and besides, why would you confuse two libraries? What are the docs for?
According to Guido the language differences aren't going to be so huge that code can't be ported, I think he said that something like 90% is going to already run, and there will be tools to help you locate and convert the other 10%.