Free isn't a magic bullet. There are countless Google failures that are all free, but no one wants (esp Google+)
Part of the issue is that all of the flagship phones run Android. Another part is that everyone knows that they can continue to use all of their existing Android stuff (esp. apps) if they stick with Android.
Regardless, very few companies can be successful with an approach of "You will like what we tell you to like", especially if the market tells them otherwise.
I have Chrome on my Nexus 7, and my Galaxy Nexus. Although it can bog down if I try to open a bunch of new tabs at once, I do not have those problems.
My guess is your phone has a bunch of crapware installed, and that's causing the issues you're having. If it was just the browser, you wouldn't have the same results in Firefox. (I consider Touchwiz, Sense, MotoBlur to be crapware if they cause problems)
Clearly, you have not actually tried that. Even at launch, XP on 128MB was painful. Last time I tried it (about a year ago) XP (fully patched) on 512MB still required plenty of swapping.
For what it's worth, I've been running a media player (no AV, minimal overhead) on 1GB and 7 x64. It wasn't until last month's updates when it finally showed signs of insufficient RAM.
That assumes that keeping the name XBMC was their goal. I'm not sure that it was.
I actually had ignored XBMC for years, believing that it's purpose was to create a media client for Xbox devices. It was not until this post that I realized it was something else entirely, and that I'm actually interested in it.
(If I can figure out how to set up caching properly, I will be using it exclusively on my media box)
.Net was a promotional name applied to many products at the time, much like XP before that.
Part of this was to align the current versions, and part of it was to emphasize the network capabilities being introduced. This all happened ~2002, and that was a very big thing (from a marketing perspective) at the time.
Degrees are not always 2 or 4 years (or 6, or 7), but can vary by degree. While the usual EE degree is normally a 4-year Bachelor's program, that is not always the case.
Most likely, you are correct, the Electronic Engineering degree is not the EE degree the parent expected.
Also, "Install and maintain a firewall configuration to protect cardholder data" appears to be the VERY FIRST requirement of PCI. Now, I'm not sure if that can be met with a separate (hardware) firewall, but I suspect they require firewalls on each piece.
I'm assuming by "vendor", the OP meant a small company that sold the equipment and installation, not the manufacturer.
Generally, they work by brand recognition. Same as ads on TV, etc. When they show you an ad for (e.g.) a Ford truck, you aren't supposed to go out and buy one right away. It's supposed to linger in the back of your mind, so that when you do go shopping for a truck, you're inclined towards buying a Ford.
As the old saying goes, "Half the money I spend on advertising is wasted; the trouble is I don't know which half." -John Wanamaker
I fail to see how that article supports that claim. In fact, it shows that Apple is putting forth considerable effort to reduce child labor, and punish suppliers that get caught using it.
When you pay for gas with a credit card and the pump asks you to punch in your zip code, it's not collecting marketing information. It's using the zip code as a (rather flimsy) security measure to protect against someone buying gas with a lost/stolen credit card
Sometimes. Other times, it's explicitly used for marketing purposes, and has nothing to do with card security. Gas at the pump is usually security, but any time a cashier is involved it's usually marketing.
There was a study a while back about what people wanted most in a phone. The top 2 responses were a bigger screen, and for it to be slimmer. Physical keyboards are a problem for the latter.
The submitter (as well as myself) are in the minority by being willing to accept a thicker phone in exchange for a physical keyboard.
I had Swype on my last phone. My new phone (and tablet) do not. I used Google Keyboard, and felt it to not be as good as Swype. I also still had access to SwiftKey from back when it was Amazon Free App of the Day, so I installed it. I am now back to Google keyboard, and am considering buying Swype.
Here's the real difference - how it handles mistakes. On Swiftkey, when you try to enter a word and it gets the wrong one, invariably I find it easier to erase the whole thing, and enter it manually.
Swype provides a long list of similar words, and it's easy enough to change to one of them. It also defaults to the words I actually use.
Combo that with Swiftkey recognizing the word 'fuck', but refusing to ever assume that's what I meant, and it's not a good experience.
While there are situations where infrastructure really can't scale with needs (e.g. crowded stadium, or a large event), I'm sure their claim that it won't affect very many people is bullshit. I'm sure, because this is a non-trivial change to make, and they wouldn't be doing it if wouldn't affect anyone.
My (and everyone else's) faith in VZW makes me think this is merely another attempt to kill unlimited data.
On a related note, last week, I was at a crowded stadium, and I made sure to torrent 4.1GB. I didn't need to, but if VZW wants to make unlimited such a pain, I'm going to make sure I use it to its fullest.
Slashdot Mirror
Free isn't a magic bullet. There are countless Google failures that are all free, but no one wants (esp Google+)
Part of the issue is that all of the flagship phones run Android. Another part is that everyone knows that they can continue to use all of their existing Android stuff (esp. apps) if they stick with Android.
Regardless, very few companies can be successful with an approach of "You will like what we tell you to like", especially if the market tells them otherwise.
My guess is those numbers are for the x64 version, which does use more RAM.
So, we're supposed to ignore the actual screen, and simulate input with another, independent device?
That sounds an awful lot like a mouse.
And I think I've been trolled.
I have Chrome on my Nexus 7, and my Galaxy Nexus. Although it can bog down if I try to open a bunch of new tabs at once, I do not have those problems.
My guess is your phone has a bunch of crapware installed, and that's causing the issues you're having. If it was just the browser, you wouldn't have the same results in Firefox.
(I consider Touchwiz, Sense, MotoBlur to be crapware if they cause problems)
Clearly, you have not actually tried that. Even at launch, XP on 128MB was painful. Last time I tried it (about a year ago) XP (fully patched) on 512MB still required plenty of swapping.
For what it's worth, I've been running a media player (no AV, minimal overhead) on 1GB and 7 x64. It wasn't until last month's updates when it finally showed signs of insufficient RAM.
These are known to have timing issues, so are unsuitable for a variety of uses.
That assumes that keeping the name XBMC was their goal. I'm not sure that it was.
I actually had ignored XBMC for years, believing that it's purpose was to create a media client for Xbox devices. It was not until this post that I realized it was something else entirely, and that I'm actually interested in it.
(If I can figure out how to set up caching properly, I will be using it exclusively on my media box)
I believe this is an example of Poe's Law. If I weren't familiar with the Uncyclopedia, I probably would've started repeating it as fact.
.Net was a promotional name applied to many products at the time, much like XP before that.
Part of this was to align the current versions, and part of it was to emphasize the network capabilities being introduced. This all happened ~2002, and that was a very big thing (from a marketing perspective) at the time.
This post seems to think the main reason was the latter. .NET product names
Partial list of
I still can't read a word of it though
Degrees are not always 2 or 4 years (or 6, or 7), but can vary by degree. While the usual EE degree is normally a 4-year Bachelor's program, that is not always the case.
Most likely, you are correct, the Electronic Engineering degree is not the EE degree the parent expected.
Also, "Install and maintain a firewall configuration to protect cardholder data" appears to be the VERY FIRST requirement of PCI.
Now, I'm not sure if that can be met with a separate (hardware) firewall, but I suspect they require firewalls on each piece.
I'm assuming by "vendor", the OP meant a small company that sold the equipment and installation, not the manufacturer.
He's referring to the address bar also being the search bar, which provides suggestions. I do believe this feature can be disabled.
Generally, they work by brand recognition. Same as ads on TV, etc. When they show you an ad for (e.g.) a Ford truck, you aren't supposed to go out and buy one right away. It's supposed to linger in the back of your mind, so that when you do go shopping for a truck, you're inclined towards buying a Ford.
As the old saying goes, "Half the money I spend on advertising is wasted; the trouble is I don't know which half." -John Wanamaker
Per this article, either you're doing things wrong, or you are a very specific type of merchant.
Generally, if the card is swiped, your card processor (merchant account) eats the loss. If the card number is entered manually, you eat the loss.
Apple stores routinely set off fraud prevention, because thieves like to target Apple. Apple gear is easy to fence.
There are a number ways to handle this properly, but they clearly didn't follow any of them.
I fail to see how that article supports that claim. In fact, it shows that Apple is putting forth considerable effort to reduce child labor, and punish suppliers that get caught using it.
Sometimes. Other times, it's explicitly used for marketing purposes, and has nothing to do with card security. Gas at the pump is usually security, but any time a cashier is involved it's usually marketing.
You can add words to the dictionary, and Swype will find them just fine.
(Not necessarily true of other keyboards)
Glass screens (like the Note) do not scratch easily from metal. There are plenty of Youtube videos about this.
Sand, OTOH, would destroy that screen in a second.
People might *SAY* they want small screens, that so many phones are too big.
Whereas people actually *BUY* the phones with enormous screens. I believe 4.3" is the standard now, with phablets (like the Note) selling very well.
(The battery's probably not as big an issue as you think, because the screen sucks more juice than anything)
There was a study a while back about what people wanted most in a phone. The top 2 responses were a bigger screen, and for it to be slimmer. Physical keyboards are a problem for the latter.
The submitter (as well as myself) are in the minority by being willing to accept a thicker phone in exchange for a physical keyboard.
I had Swype on my last phone. My new phone (and tablet) do not. I used Google Keyboard, and felt it to not be as good as Swype. I also still had access to SwiftKey from back when it was Amazon Free App of the Day, so I installed it. I am now back to Google keyboard, and am considering buying Swype.
Here's the real difference - how it handles mistakes. On Swiftkey, when you try to enter a word and it gets the wrong one, invariably I find it easier to erase the whole thing, and enter it manually.
Swype provides a long list of similar words, and it's easy enough to change to one of them. It also defaults to the words I actually use.
Combo that with Swiftkey recognizing the word 'fuck', but refusing to ever assume that's what I meant, and it's not a good experience.
While there are situations where infrastructure really can't scale with needs (e.g. crowded stadium, or a large event), I'm sure their claim that it won't affect very many people is bullshit. I'm sure, because this is a non-trivial change to make, and they wouldn't be doing it if wouldn't affect anyone.
My (and everyone else's) faith in VZW makes me think this is merely another attempt to kill unlimited data.
On a related note, last week, I was at a crowded stadium, and I made sure to torrent 4.1GB. I didn't need to, but if VZW wants to make unlimited such a pain, I'm going to make sure I use it to its fullest.
Virgin is a Sprint MVNO, and Cricket was recently bought by AT&T (which will likely kill it for competing)