If you feel the necessity to swear, just fucking do it you asshole. Self-censoring your own words just make you come across as an immature teen, who has just discovered the pleasure of cursing, but still puts in asterisks in case Mummy sees what you are doing and scolds you for using "naughty words".
And you posted anonymously anyway, so what the hell, just go for it.
Yes, Flash is not a codec, it is a CONTAINER. Exactly the same as arbitrary-plugin is a container, or the HTML-5 video tag is a container.
The point is, which you still seem to miss, is that no-one cares.
My further point is that while Flash just went out and implemented a solution, the HTML-5 committees will still be arguing the pros and cons of which codec to use in 10 years. The video tag will just become another kludge with embedded flash / object tags for fallbacks to other delivery systems, thus making the whole issue moot.
While a newer, better codec can be implemented with a new version of the flash player plugin, that same codec cannot be implemented via the video tag without a whole bloody browser upgrade. So you are tying all the functionality back into the browser, making it LESS modular than the current system. Hardly what I'd call progress.
Modern PCs and laptops can manage perfectly well, and if your [choice-of-mobile-device] sucks, then blame the mobile manufacturer for not allowing developers proper API access to the underlying hardware acceleration.
Any shortfalls in performance will be addressed in the next version and improvements are always being made. Hell, I can remember a time donkeys year ago when I had to specify a frame skip in my MPEG2 player, because the processor couldn't keep up with decoding every single frame.
I was merely describing a very simple compression system, which does in fact define up to 2^4339 distinct messages. The fact that all the messages are composed of a single character does not detract from the theoretical maximum number of possibilities.
Of course, as your dictionary (character set) increases, then the number of your "arbitrary" messages becomes a lot less than this...
If your character set is limited to the uppercase A-Z and a space (enough to transmit a simplistic English message, albeit without punctuation), and with zero redundancy, you can still encode about 904 characters on the basis 2^4339 / 2^4.8
As all text will have some redundancy, I'd put an upper bound at maybe 3000 characters using that 27 character subset. 1.44 bits per character is perfectly "doable" with todays compression algorithms.
Except for the fact the algorithms he has submitted have NOTHING to do with compression, and are just a method of mapping the 4339 bits into the allowable Unicode character set over 140 x 32 bit character "slots", i.e. encoding / decoding only.
With 4339 bits, hell in theory the longest actual tweet you could make is 2^4339 of any single character you choose, using the 4339 bits just to represent a (very large) counter of how many times to repeat the character.
Considering that 2^4339 is approximately 10^1305, and there are probably only 10^82 atoms in the whole universe, that's one bloody long tweet.
I guess YouTube and every other "tube" site on the net must be wrong then, and you're right.
Most people don't give a fuck about whether it's encoded in Ogg, h264, MPEG-4 or whatever. They also don't give a fuck whether the container is open source, closed source, patent encumbered, etc. etc. They don't want to have to worry about whether or not A,B or C codec is installed on their system, a simple download of Flash player and they're ready to go on 99% of the nets' video sites (hell, most of them already had Flash on their system right after they played their first Facebook game).
They just want to watch the damn video. Nothing more, nothing less.
Stop trying to turn a simple media functionality into some kind of religious crusade, and go find something useful to do.
Until Jobsy releases version 4, no virus is gonna run (in the background anyway).
Of course the iPod/iPad/iPhone is more secure... you can't do fuck-all with it without permission from Apple headquarters... and even then any virus must be written in Objective-C to conform to Steve's code "laws".
You are taking the law quite literally, but without applying the common sense that a judge and jury will likely use (or not, you never know with some people).
Hypothetical situation.
You lose your wallet, it has your name, address and contact number in it, along with 50 bucks. You contact the owner, tell him you found his wallet, and he says "wow, an honest person in this day and age, what a fucking miracle. Tell you what, keep the money and the wallet, you deserve it".
Are you STILL required now to proceed to step 2, and report it to the police ? For what purpose exactly ? So they can also contact the owner who has already said you can keep it ?
Now, moving on a little. What if the owner tells you "it is not mine", even if it's patently obvious that it IS his... again, what purpose does step 2 serve ?
I'll tell you... step 2 serves to cover step 1 in the event you CANNOT identify or contact the owner yourself. If step 1 has already been fulfilled, and the owner has said it is not mine... you cannot then be at fault for not proceeding to step 2.
I'M SORRY ANONYMOUS COWARD, I CAN'T LET YOU DO THAT.
Filter error: Don't use so many caps. It's like YELLING. Nope, I'm just trying to emulate what was done on Tron and later revamped on Southpark. Stop being so fucking judgmental, you don't know me !
I'll reply to myself, as everyone seemed to have missed the point of the parent's question, and my response.
I was merely saying that in the space of 2 years, the capacity of a typical keydisk has gone up by a factor of 64 while the price has remained constant.
Assuming that same rule for the next 2 years, and we end up with a 1TB keydisk for $10 in about 2012.
Bearing in mind that perhaps 2 years ago, a 256MB USB Keydisk cost me $10, and today, I can get a 16GB for the same price, yes, I'd say it's just a matter of time.
Writing a METHOD to do basic arithmetic options such as incrementing a variable by 1 ?
Look, objects and have their place... that doesn't mean you have to use the fuckers everywhere !
Methods encapsulate a commonly used piece of code, and are very useful if that code changes in future. How exactly could "increment a variable by 1" EVER need modification at a later date ?
If you use that as your guideline, you'll never find yourself making dumbass statements like "point.incrementX(1) is just as clear as point.X++", and looking like some OCD maniac coder.
Slashdot Mirror
Ah the old chestnut ...
"Linux supports far more hardware than X,Y or Z operating system".
"But why won't my A,B or C modem work under Linux".
"Ah you shouldn't buy crappy hardware".
(Note this is the same hardware that works perfectly well under X,Y and Z operating system).
In summary, Linux is still not ready for (everyone's) desktop, only those with non-crappy hardware.
If you feel the necessity to swear, just fucking do it you asshole. Self-censoring your own words just make you come across as an immature teen, who has just discovered the pleasure of cursing, but still puts in asterisks in case Mummy sees what you are doing and scolds you for using "naughty words".
And you posted anonymously anyway, so what the hell, just go for it.
Being a hypocrite and being a cunt are not mutually exclusive.
I'm not your buddy, guy!
You must have watched an outtake.
The quote is actually "God damn these electric sex pants".
Coming soon to a country near you ... The War on Intellectual Property Rights.
Hell, they covered drugs and terror already, and look how well those worked out.
someone will sell a mobile device in 5-10 years that will run a real OS
Android, Maemo ... why wait 5-10 years, they're here now !
Yes, Flash is not a codec, it is a CONTAINER. Exactly the same as arbitrary-plugin is a container, or the HTML-5 video tag is a container.
The point is, which you still seem to miss, is that no-one cares.
My further point is that while Flash just went out and implemented a solution, the HTML-5 committees will still be arguing the pros and cons of which codec to use in 10 years. The video tag will just become another kludge with embedded flash / object tags for fallbacks to other delivery systems, thus making the whole issue moot.
While a newer, better codec can be implemented with a new version of the flash player plugin, that same codec cannot be implemented via the video tag without a whole bloody browser upgrade. So you are tying all the functionality back into the browser, making it LESS modular than the current system. Hardly what I'd call progress.
Modern PCs and laptops can manage perfectly well, and if your [choice-of-mobile-device] sucks, then blame the mobile manufacturer for not allowing developers proper API access to the underlying hardware acceleration.
Any shortfalls in performance will be addressed in the next version and improvements are always being made. Hell, I can remember a time donkeys year ago when I had to specify a frame skip in my MPEG2 player, because the processor couldn't keep up with decoding every single frame.
Depends on your definition of "arbitrary".
I was merely describing a very simple compression system, which does in fact define up to 2^4339 distinct messages. The fact that all the messages are composed of a single character does not detract from the theoretical maximum number of possibilities.
Of course, as your dictionary (character set) increases, then the number of your "arbitrary" messages becomes a lot less than this ...
If your character set is limited to the uppercase A-Z and a space (enough to transmit a simplistic English message, albeit without punctuation), and with zero redundancy, you can still encode about 904 characters on the basis 2^4339 / 2^4.8
As all text will have some redundancy, I'd put an upper bound at maybe 3000 characters using that 27 character subset. 1.44 bits per character is perfectly "doable" with todays compression algorithms.
Except for the fact the algorithms he has submitted have NOTHING to do with compression, and are just a method of mapping the 4339 bits into the allowable Unicode character set over 140 x 32 bit character "slots", i.e. encoding / decoding only.
With 4339 bits, hell in theory the longest actual tweet you could make is 2^4339 of any single character you choose, using the 4339 bits just to represent a (very large) counter of how many times to repeat the character.
Considering that 2^4339 is approximately 10^1305, and there are probably only 10^82 atoms in the whole universe, that's one bloody long tweet.
I guess YouTube and every other "tube" site on the net must be wrong then, and you're right.
Most people don't give a fuck about whether it's encoded in Ogg, h264, MPEG-4 or whatever. They also don't give a fuck whether the container is open source, closed source, patent encumbered, etc. etc. They don't want to have to worry about whether or not A,B or C codec is installed on their system, a simple download of Flash player and they're ready to go on 99% of the nets' video sites (hell, most of them already had Flash on their system right after they played their first Facebook game).
They just want to watch the damn video. Nothing more, nothing less.
Stop trying to turn a simple media functionality into some kind of religious crusade, and go find something useful to do.
Dozens of servers ought to be enough for anybody.
To put some perspective on it for non-nerds / Slashdot editors.
Port 80 and 443 are the Web ... the other 65534 ports are the Internet, where everything interesting happens.
The plural of box is boxes ... please stop trying so hard to sound smarter than you are.
Until Jobsy releases version 4, no virus is gonna run (in the background anyway).
Of course the iPod/iPad/iPhone is more secure ... you can't do fuck-all with it without permission from Apple headquarters ... and even then any virus must be written in Objective-C to conform to Steve's code "laws".
Arghh .... got 2nd and 3rd person mixed up ... try again.
Someone loses their wallet, it has their name, address and contact number in it.
You are taking the law quite literally, but without applying the common sense that a judge and jury will likely use (or not, you never know with some people).
Hypothetical situation.
You lose your wallet, it has your name, address and contact number in it, along with 50 bucks. You contact the owner, tell him you found his wallet, and he says "wow, an honest person in this day and age, what a fucking miracle. Tell you what, keep the money and the wallet, you deserve it".
Are you STILL required now to proceed to step 2, and report it to the police ? For what purpose exactly ? So they can also contact the owner who has already said you can keep it ?
Now, moving on a little. What if the owner tells you "it is not mine", even if it's patently obvious that it IS his ... again, what purpose does step 2 serve ?
I'll tell you ... step 2 serves to cover step 1 in the event you CANNOT identify or contact the owner yourself. If step 1 has already been fulfilled, and the owner has said it is not mine ... you cannot then be at fault for not proceeding to step 2.
To be fair, 1 in 10 of kdawsons stories are dupes ... so they actually only stole 9 original works.
Facepalm ... I'll hand in my geek card in the morning.
Not get off my lawn!
Okay, I'll stay right here on your lawn.
I'M SORRY ANONYMOUS COWARD, I CAN'T LET YOU DO THAT.
Filter error: Don't use so many caps. It's like YELLING. Nope, I'm just trying to emulate what was done on Tron and later revamped on Southpark. Stop being so fucking judgmental, you don't know me !
What glaring discrepancy are you talking about.
Those Chinese workers having a nap are packaging mice and joysticks into plastic containers ... they are hardly "programmers".
I'll reply to myself, as everyone seemed to have missed the point of the parent's question, and my response.
I was merely saying that in the space of 2 years, the capacity of a typical keydisk has gone up by a factor of 64 while the price has remained constant.
Assuming that same rule for the next 2 years, and we end up with a 1TB keydisk for $10 in about 2012.
Bearing in mind that perhaps 2 years ago, a 256MB USB Keydisk cost me $10, and today, I can get a 16GB for the same price, yes, I'd say it's just a matter of time.
Writing a METHOD to do basic arithmetic options such as incrementing a variable by 1 ?
Look, objects and have their place ... that doesn't mean you have to use the fuckers everywhere !
Methods encapsulate a commonly used piece of code, and are very useful if that code changes in future. How exactly could "increment a variable by 1" EVER need modification at a later date ?
If you use that as your guideline, you'll never find yourself making dumbass statements like "point.incrementX(1) is just as clear as point.X++", and looking like some OCD maniac coder.
Registrar of Births Deaths and Marriages has, in UK at least, computerised records going back to 1930 something ...
No one NEEDS to go trawling through old newspapers anymore looking to see who has died.