"Both Android and iOS have been plagued with exploits"
"The only current smartphone OS that is safe against exploits and vulnerabilities is Windows Phone 7"
"even on the desktop Windows most exploits are against third party apps like Flash or Java, not Windows itself"
"if you want to get a smartphone that is safe against exploits and malware, Windows Phone 7 is your only answer"
You have absolutely no idea what you're writing, do you? I'm amazed this got upvoted 5 points and labelled Informative.
I'm not sure if you are referring to Rickard Falkvinge as the "wannabe journalist/blogger" or as the "unreliable source". Do you even know the first thing about his political efforts? Do you even know who he is?
Of all nationalities, a CHINESE company is feeling bereft of its idea, and goes to court over it. It's funny to see the PRC govt. crack down on this as well, while systematically turning a blind eye to all other plagiariasm and IP theft that is the technological foundation of the nation.
The computer generated imagery and FX are so obvious. Also, there's no such thing as the Japanese Institute of Science and Technology (JIST). However, there is a Japanese ADVANCED Institute of Science and Technology - JAIST. How did this slip through and reach the front page?:)
Oh, so, just because some of these people expressed exaggerated grief and idolizing, RMS' blunt blurting is just fine? You seem to have a knack of saying absolutely nothing at all of any substance what so ever while still being able to sugar-coat it with fancy words and paraphrasing. Say, do you also happen to have something clever to say about the people in North Korea who put on fake cries when the, or someone close to the Great Leader passes away?
...are buried deep on the website for some weird reason. They are available for Windows and "Macintosh". No generic *nix version so far, which struck me as something pretty bad given the common demography generally interested in helping out with this sort of project.
The Linux kernel and the GNU userland is afterall i386, is it not?
Up until just recently I had a long-running OpenBSD system on an old P75 with 64mb of RAM. It wasn't until just last year OpenBSD/i386 actually started requiring a 486.
They're called "ocean swimming pools", and have been around for over a hundred years now. Help yourself to a google image search and enjoy the beautiful images.
It's more intensive in terms of software decoding than the current best H.264 decoders. I am not aware of any software that can do hardware decoding of VP8 video on current, common GPUs.
Why don't you just google and enjoy the results of the many decent tests of WebM vs x264's H.264 output that you can find out there? So far, the current best (only?) WebM encoder hasn't proven itself to give better quality at same bitrate as what x264 puts out as H.264 in any test; x264's results consistently bests WebM at same (and sometimes even lower) bitrate. The bonus? H.264 decoding is adopted in hardware all over the place.
HE-AAC uses SBR to reduce its data footprint. This results in worse reproduction of the source audio than LE-AAC at same (and often even lower) bitrate. The whole deal with HE is that it can maintain good quality at very low bitrate, by giving up accuracy. The article is misleading in the sense that it alludes people into believing that HE-AAC is the best choice for audio, regardless what kind and its purpose, incl. the thing the predominant masses think of when hearing the term audio - music - and do far no digitally lossy encoder can rival Apple's Core Audio LE-AAC codec when it comes to that case.
HE-AAC uses SBR to reduce its data footprint. This results in worse reproduction of the source audio than LE-AAC at same bitrate (and often even lower bitrate). The whole deal with HE is that it can maintain good quality at very low bitrate, by giving up accuracy. So far, Apple's LE-AAC encoder in their Core Audio framework is the best choice for digitally non-lossless compression.
No, you're wrong. It's only "illegal" if you ask money for the software without paying your license fees, as this puts the software in a commercial context. The license for MPEG-4/AVC clearly states that the "technology" may be used in non-commercial contexts WITHOUT being subjected to license fees - just like with MPEG-4/ASP.
Please state your definition of "end-users"; do you mean the manufacturers using Android in their phones, or do you mean the customers buying and using the phones? If you mean the latter, then you are either yet another misinformed individual in this debate speaking out of his/her behind, or you're just a troll ("being sued into the ground, as is happening now"). The final end-user has never been a direct subject for MPEG's license fees. Ever. Never ever means NEVER EVER - not even before the MPEG-LA clearly stated that they will not deal licensing fees on cases of free distribution of MPEG-4/AVC material on the web in the form of YouTube, Vimeo etc.
Another curious detail to this ridiculous debacle is how NOBODY made a squeak over MPEG-4/ASP during the approx. 8 years it has been in use on the web. Not the slightest sound of a tiny violin has been heard about that. Why? Why start now? The scenario has not changed.
The specifications are fully open for anyone to -freely- implement both coding and decoding for. The specifications were fully open in the sense that not a single commercial entity was responsible for drafting and controlling it, but any company that wanted to partake; so-called open participation. These are undisputable facts about the MPEG codecs. The problem here isn't that H.264 isn't as open as Google wants it to be - the problem is that it isn't as FREE as they want it to be. In order to make use of the MPEG "technology" in a _commercial_ context, you need to pay, and Google does not want to pay.
Not sure why the original poster claims that the 6502 core design was lost in time. WDC (Western Design Center http://www.westerndesigncenter.com/wdc/ ) bought the core design and the rights to license it many many years ago. These are the guys behind a few variants building on top of the 6502 as well, like f.e. the 65816 used in the Super Nintendo.
No, you're actually wrong - in the context of password protection, encrypting passwords means using a one-way encryption scheme. The method is in some ways similar to hashing, but the common process used is actually that of a modified version of the Blowfish crypto cipher resulting in a non-reversible output. The process is very time-consuming compared to generic hashing such as MD5, SHAx etc., and is practically impossible to create rainbow tables for, practically impossible to bruteforce. You can educate yourself further on the topic here: http://codahale.com/how-to-safely-store-a-password/
The magnetical north pole is on the opposite side of the planet, close to our geographical south pole; a compass' N needle points towards the magnetical south pole, but as we use compasses to orient towards our geographical south pole, we simply mark the needle N.
Slashdot Mirror
"Both Android and iOS have been plagued with exploits"
"The only current smartphone OS that is safe against exploits and vulnerabilities is Windows Phone 7"
"even on the desktop Windows most exploits are against third party apps like Flash or Java, not Windows itself"
"if you want to get a smartphone that is safe against exploits and malware, Windows Phone 7 is your only answer"
You have absolutely no idea what you're writing, do you? I'm amazed this got upvoted 5 points and labelled Informative.
I'm not sure if you are referring to Rickard Falkvinge as the "wannabe journalist/blogger" or as the "unreliable source". Do you even know the first thing about his political efforts? Do you even know who he is?
Of all nationalities, a CHINESE company is feeling bereft of its idea, and goes to court over it. It's funny to see the PRC govt. crack down on this as well, while systematically turning a blind eye to all other plagiariasm and IP theft that is the technological foundation of the nation.
Same as used in the rest of the world? Europe has no problems with GPS and 4G.
...when it costs more energy to blog about your breakfast than it does actually cooking it.
Just to elaborate on what I mean, and try not to get me wrong with this example:
"We understand that a non-muslim doctor would do the job just as good, but we really prefer that a muslim doctor treats our daughter's injury."
You see the problem here, right? My point is that maybe your priorities aren't what they should be.
Do you absolutely need this? Is it not enough if the software is free of charge and functional?
The computer generated imagery and FX are so obvious. Also, there's no such thing as the Japanese Institute of Science and Technology (JIST). However, there is a Japanese ADVANCED Institute of Science and Technology - JAIST. How did this slip through and reach the front page? :)
Oh, so, just because some of these people expressed exaggerated grief and idolizing, RMS' blunt blurting is just fine? You seem to have a knack of saying absolutely nothing at all of any substance what so ever while still being able to sugar-coat it with fancy words and paraphrasing. Say, do you also happen to have something clever to say about the people in North Korea who put on fake cries when the, or someone close to the Great Leader passes away?
...are buried deep on the website for some weird reason. They are available for Windows and "Macintosh". No generic *nix version so far, which struck me as something pretty bad given the common demography generally interested in helping out with this sort of project.
Didn't you just love this series?
The Linux kernel and the GNU userland is afterall i386, is it not? Up until just recently I had a long-running OpenBSD system on an old P75 with 64mb of RAM. It wasn't until just last year OpenBSD/i386 actually started requiring a 486.
...studios all seem to think that it's the ISPs' duty and responsibility to do their job for them, for free. Ask them where to send the bill, I say.
They're called "ocean swimming pools", and have been around for over a hundred years now. Help yourself to a google image search and enjoy the beautiful images.
Because a license that ties the hands of the developer is not equal to freedom. Freedom is not freedom unless it involves both end-user AND developer.
It's more intensive in terms of software decoding than the current best H.264 decoders. I am not aware of any software that can do hardware decoding of VP8 video on current, common GPUs.
Why don't you just google and enjoy the results of the many decent tests of WebM vs x264's H.264 output that you can find out there? So far, the current best (only?) WebM encoder hasn't proven itself to give better quality at same bitrate as what x264 puts out as H.264 in any test; x264's results consistently bests WebM at same (and sometimes even lower) bitrate. The bonus? H.264 decoding is adopted in hardware all over the place.
HE-AAC uses SBR to reduce its data footprint. This results in worse reproduction of the source audio than LE-AAC at same (and often even lower) bitrate. The whole deal with HE is that it can maintain good quality at very low bitrate, by giving up accuracy. The article is misleading in the sense that it alludes people into believing that HE-AAC is the best choice for audio, regardless what kind and its purpose, incl. the thing the predominant masses think of when hearing the term audio - music - and do far no digitally lossy encoder can rival Apple's Core Audio LE-AAC codec when it comes to that case.
HE-AAC uses SBR to reduce its data footprint. This results in worse reproduction of the source audio than LE-AAC at same bitrate (and often even lower bitrate). The whole deal with HE is that it can maintain good quality at very low bitrate, by giving up accuracy. So far, Apple's LE-AAC encoder in their Core Audio framework is the best choice for digitally non-lossless compression.
No, you're wrong. It's only "illegal" if you ask money for the software without paying your license fees, as this puts the software in a commercial context. The license for MPEG-4/AVC clearly states that the "technology" may be used in non-commercial contexts WITHOUT being subjected to license fees - just like with MPEG-4/ASP.
Please state your definition of "end-users"; do you mean the manufacturers using Android in their phones, or do you mean the customers buying and using the phones? If you mean the latter, then you are either yet another misinformed individual in this debate speaking out of his/her behind, or you're just a troll ("being sued into the ground, as is happening now"). The final end-user has never been a direct subject for MPEG's license fees. Ever. Never ever means NEVER EVER - not even before the MPEG-LA clearly stated that they will not deal licensing fees on cases of free distribution of MPEG-4/AVC material on the web in the form of YouTube, Vimeo etc. Another curious detail to this ridiculous debacle is how NOBODY made a squeak over MPEG-4/ASP during the approx. 8 years it has been in use on the web. Not the slightest sound of a tiny violin has been heard about that. Why? Why start now? The scenario has not changed.
The specifications are fully open for anyone to -freely- implement both coding and decoding for. The specifications were fully open in the sense that not a single commercial entity was responsible for drafting and controlling it, but any company that wanted to partake; so-called open participation. These are undisputable facts about the MPEG codecs. The problem here isn't that H.264 isn't as open as Google wants it to be - the problem is that it isn't as FREE as they want it to be. In order to make use of the MPEG "technology" in a _commercial_ context, you need to pay, and Google does not want to pay.
Not sure why the original poster claims that the 6502 core design was lost in time. WDC (Western Design Center http://www.westerndesigncenter.com/wdc/ ) bought the core design and the rights to license it many many years ago. These are the guys behind a few variants building on top of the 6502 as well, like f.e. the 65816 used in the Super Nintendo.
No, you're actually wrong - in the context of password protection, encrypting passwords means using a one-way encryption scheme. The method is in some ways similar to hashing, but the common process used is actually that of a modified version of the Blowfish crypto cipher resulting in a non-reversible output. The process is very time-consuming compared to generic hashing such as MD5, SHAx etc., and is practically impossible to create rainbow tables for, practically impossible to bruteforce. You can educate yourself further on the topic here: http://codahale.com/how-to-safely-store-a-password/
The magnetical north pole is on the opposite side of the planet, close to our geographical south pole; a compass' N needle points towards the magnetical south pole, but as we use compasses to orient towards our geographical south pole, we simply mark the needle N.