Android lets you change keyboards. IOS has something that appears to do this, but it randomly reverts (such as when entering passwords) and is terribly limited compared to Android, not even supporting dictation.

Theres certainly a bandwidth penalty.

Its worth remembering that that 98k IOPS will rapidly drop to 2-10k for basically every SATA based SSD on the market. The 750 being advertised here is the first one I've seen sustain 20k.

IOPS are like cores: for any one single task, more doesnt mean faster. But in the real world, on a multitasking OS, the more you have the better things will be and the fewer times you'll ever be stuck waiting on your PC to stop thrashing.

You'll note that to produce this crappy summary they skipped over the IOmeter pages which show the Intel 750 bursting @ 180k IOPS and sustaining 20k, while 90% of consumer SSDs cant sustain more than 8k and the x-25m theyre touting struggles to break 2k.

Load up a slew of VMs on a virtualization lab on that x-25M and compare it to the 750-- THEN tell me that its no faster.

Im calling BS on the statistics, which has a 1.2TB ssd as substantially slower than a 120GB SSD from years ago, which is itself substantially slower than consumer-grade drives like the Crucial BX series.

This all points to some horrible firmware issue, or testing problems, or bad methodology. Theres no real other way to explain that performance; simply increasing the capacity to 1.2TB should have it topping all of the benchmarks, regardless of the protocol used to connect it.

For starters, I have read up on it, and many many vendors agree that it IS security.
Sources:
Cisco (Top 2 paragraphs of intro)
http://www.cisco.com/web/about...
SANS institute (Page 5, 2nd paragraph)

And so on.

As to your solution, it has a massive issue. Route tables must use next hops as their gateway; you could not enter a command like that targetting my WAN, and have it work, because my WAN IP would not be a next hop for your computer. The only thing your route table can do is instruct your computer which IP on your broadcast domain will be willing to handle your datagrams. At that point, it is up to that router to figure out the next hops.

You will note I asked you what the L3 / L4 headers would be on your packet; this was specifically to demonstrate why such attacks would fail. You would have a source address of 9.9.9.9, and a destination of 192.168.50.5, and you would instruct your computer to pass that datagram off to a router at ethernet address 99:99:99:99:99:99 (your router), and he would promptly vomit and say "what the hell I cant route an RFC1918". Add the route on your router, and you've shoved the issue back to your ISP, whose router would either fail to find a route for that subnet, or (more likely) outright reject it as a violation of RFC.

The only scenario in which this attack makes sense is when the attacker IS the next hop, that is your ISP. And for 99.999% of users, this is not a realistic threat model they will face, and NAT will be "acceptable" security.

No one argues that a stateful firewall is BETTER (as it prevents attacks like you mentioned), but to say that NAT adds no security whatsoever is being silly; major infrastructure vendors disagree with you.

I understand these things quite well, as I wouldnt be in the field if I didnt. NAT provides some degree of security in the sense that if you are on an IPv4 network (99% of home users) on an RFC 1918 network (99% of home users) with NAT enabled, it is impossible for anyone to send an unsolicited datagram to your computer behind the NAT.

There are technologies which punch holes in this (like uPnP), but that does not change the implicit security.

Then you have a static port mapping. Generally to get through the NAT you need to know the public IP and port (out of 65536) you want to connect to, which is dynamically assigned. Then you need to deal with the fact that anything you send is going to be pinned to a specific client port not of your choosing, and you will not know the correct source port to get the client to accept your unsolicited datagram (whch will thence be dropped).

I never said it was perfect security, but it prevents folks from accessing listening ports (like 135-139) as a listener port wont have a dynamic mapping-- only outbound traffic gets those.

But you seem to think Im wrong, so educate me. Lets set up a scenario.

Gateway Public: 1.2.1.1
Gateway private: 192.168.50.1
Windows XP box: 192.168.50.5

No firewalls, NAT on the gateway, Windows XP listening on port 135-139.
What Layer3/4 headers are you going to use thats gonna get a packet delivered to one of those 4 ports on that XP box?

Most of those were around for a VERY short time, or else were rolled into another product. Goog411, for example, was specifically there to build a voice database, which is now used in Android and Google Voice.

NAT provides implicit security, even if it is not explicit. Being on an unroutable subnet means theres really nothing an intruder can do to get to your PC short of static port mappings.

People in those situations arent paying taxes unless theyre making enough to survive and are straight up blowing it. You do understand how our tax system works, right?

Adsense, gMail, Youtube, Android?

Never heard of em?

We live in a free society, not a police state, regardless of what you may be wishing. That makes a lot of things like this possible.

He could appeal to the Supreme.....oooooohhhhhhhh....

You forgot the part where Google decided to stop cooperating with repressive regimes in outing dissidents. Still waiting for Microsoft and Yahoo to do the same.