Comment Re:Sad (Score 1) 467
Since we all got mothers, I'd argue misogyny IS misanthropic.
Since we all got mothers, I'd argue misogyny IS misanthropic.
Civil disobedience has ALWAYS carried the potential for punishment and if you break the law to make your point that the law is unjust you should stand ready to be arrested, imprisoned and tried in court for what you choose to do.
Your argument would carry more weight if the government who'd be trying Snowden weren't the same one he outed for violating its own laws, with the active collaboration of its judicial branch. Not to mention all of the recent fully-public sidestepping of due process for hundreds of other enemy combatants. Oh, and the torture, including of US citizens. And... do I really need to go on?
Snowden has extremely good reason to be skeptical of the fairness of a trial... or if he'd even get a real trial.
Snowden may be using what leverage he has left. He has not yet disclosed all the information he obtained so the US government might cut a deal to avoid further disclosures.
I see no evidence that Snowden didn't hand everything over to the Guardian et al, all at once, as he said he did. On what do you base your claim that he's still got something left?
Cross-platform compatibility of C++ code is excellent these days, C++ can call low-level Apple APIs exactly as well as C, and there is no performance cost to C++ unless you choose it.
1) Good but not as good as C.
In most cases these days it's a distinction without a difference.
2) But it's an unnecessary third layer. Obj-C has the objects. C has the speed and compatibility. What do you need a third layer for?
I see this differently. Obj-C has the objects I need to interact with the framework. C++ has the speed, compatibility and expressive power I want. C has speed and compatibility, but lacks expressive power, which creates a lot of tedium and loses a lot of safety.
3) Indeed.
We agree on something
So virtually no one uses it in this scenario.
Only time I see it used is when it's a library that was written in C++ on another platform and is simply being used on a Mac.
I haven't really done much on Macs, but I did a lot of work on NeXTstep back in the day, and C++ was quite common in scientific computing there. Actually, what I saw a lot of was "Objective-C++"... they may have grown further apart, to the degree that this no longer works, but in the early 90s gcc allowed you to mix Objective-C and C++ constructs freely in the same code. So a common approach was to build everything in an OO fashion, but to choose between Objective-C and C++-style classes based on performance and flexibility tradeoffs. The result required you to be fluent in both, but that really just means being fluent in C++ because a C++ programmer can learn Objective-C in a day (which is something I respect about the language).
Personally I'd go with the CX3000, it does POTS, SIP, and USB connectivity and you can use the expansion microphones which is huge if you have more than a few people on the call.
I recommend you follow your own advice. Stop feeding the trolls.
The "Islamic State" is not a country, just a bunch of religious bigots going around killing people as if no one could have a different opinion or way of life.
Ah, Alabama!
He may now be famous enough that he couldn't be simply "disappeared" or sent to Guantanamo. That's the best guarantee.
Being famous (or infamous) is a gurantee against being "disappeared"?
I'm sure Jimmy Hoffa will be happy to hear that.
Better yet, go to Ukraine. Less Putin, more cute women. Sorta like Russia-Lite.
... and soon enough, Russia proper?
If you put an infected executable on my machine and gave it a TXT file extension it's totally harmless. So it tries to open the file in notepad....no harm there.
But how do you know that it will open it in notepad? Do you examine the registry?
How do you know that an app you tried a year ago and quickly uninstalled didn't change the extension association for
It doesn't have to be a trojan you ran either - it could have been done through an IE/Flash exploit a long time ago too.
distinction without a difference: there still has to be some sort of indication both to the OS and to the User what a file is and how to handle it.
Whether this is accomplished via Icons, File Name Extensions, Tags, or any other sort of mechanism
is ultimately irrelevant as they all accomplishes the same thing.
And they all still require the user (and the OS) to be at least somewhat intelligent.
The only way to remove this basic requirement is to remove the User, which rather defeats the purpose.
The mechanism of indicating this to the user is NOT irrelevant. A 3 character extension, with a vast legacy of possible permutations that all mean executable of some fashion is BAD. The OS may need that detail of distinction between types of executables, the user does not. Training a user that the icon that looks like 'this' means it's a program and that it means you better trust it because it can do anything you can do if malicious is world's easier than, here is a, mostly, complete list of file extensions that you should be as cautious with.
You cannot tryst the extension to be what the file actually is. But you CAN trust the extension to determine what Windows will do with it. That
No, this is what I have tried to tell here, and keep getting modded down for. You cannot trust that. Really. You can trust that Windows will treat it as a
What Windows treats
All that's needed is to modify HKEY_CURRENT_USER\Software\Classes\.jpg and it will override the system defaults. It's in the user hive, and does not even require admin privileges.
Apps do this all the time, benignly to associate file types with themselves. That your
So you cannot trust that Windows treats a
Few people will check the registry before "running" a file. They trust that Windows will open the
You're dropping out of Obj-C for cross platform compatibility, because you're dealing with a low level Apple API, or because you want maximum speed for some part of the code. All these things are usually best served by C.
Cross-platform compatibility of C++ code is excellent these days, C++ can call low-level Apple APIs exactly as well as C, and there is no performance cost to C++ unless you choose it.
Unless you're concerned that you may need to target a platform not supported by a decent C++ compiler (which is really rare, given that gcc is basically everywhere), the only reason to choose C over C++ is personal preference or concern that some of the users of the code may not know C++.
The issue with FDE in Android has for long been the lack of combining strong passwords with a pattern lock or pin lock for unlocking the screen. In other words, your encryption key is only as strong as the pin code or password you are willing to put in every time you open your screen lock.
No, it doesn't. At least in Lollipop FDE-password is separate and you enter it at boot.
It's not separate. In stock Lollipop there is only one password, and it's used both for FDE and for screen unlock. Some customized ROMs (e.g. CM) have separated it, which allows you to choose a strong boot password and a more convenient unlock password. Stock Android didn't go that direction because too many users would set a strong boot password which they only use once every few weeks and therefore forget, losing all of their data.
Had I jumped to the Nexus 6 at the same time, however, that may not have been an issue.
As a recent Nexus 6 owner, I can confirm that encryption is enabled by default. I have not noticed any performance lag and the battery life has been really good. I will admit, I'm coming from an 'ancient' phone, so maybe that's why I think it's fast enough; way faster than my old phone.
As mentioned by Gaygirlie, a big factor is the AES-NI instruction in the ARMv8 instruction set supported by your Nexus 6. It dramatically reduces the performance and power hit of AES operations.
Only God can make random selections.
