... and both to behave like the typical adolescent.

Don't do that. Problem solved.

Any hard drive that is protected by a simple "password" encryption wouldn't withstand ordinary decryption means. Which suggests that the user had a REAL password, which they would be unlikely to "forget" due to its complexity and the value of the data it protects.

So the "I forgot" defense won't work for long. And I'm guessing a little PITA time will jog the defendant's memory, regardless.

I doubt SCOTUS would hear this case, since it's a pretty straightforward situation that they would, with 99.9% certainty, agree with the judge on. It's common sense to anyone who understands this kind of stuff.

Of course, that won't stop the tinfoil-hat crowd from freaking out about it anyway.

Where do YOU live, Somalia? Either that, or you don't understand the laws you are living under wherever you are.

The judge's ruling in this case is perfectly reasonable, and in conformance with the US Constitution and US law. And common sense.

I'm not a USA law fanboi, but I have worked around enough GOOD lawyers (there actually are a few), and witnessed enough ACTUAL legal proceedings, to understand just how balanced and fair our system is. This "news" story really isn't news at all, except to someone who really doesn't understand the bigger picture here.

... while under oath.

Yes, I find that perspective troubling too. Seems like at least PART of the savings coming from reduced licensing costs for non-FOSS software could be used to fund the transition away from same.

The comment suggests to me a lack of clarity in the motivation for the transition. Money shouldn't be the only incentive, of course (I find the other upsides to a FOSS environment to be much more compelling), but anyone who understands the current state of affairs for software licensing would be reasonably expected to acknowledge that in a discussion about moving away from it.

Android devices AREN'T different, actually.

Part of the confusion is buzzword-compliance, part is a desire by competitors to cast Android-based devices in a "not for professionals" light, and the rest is just addressing users who email, etc. sensitive data around and thereby bypass the no-sensitive-data-on-the-device mandate. (Such bypasses are almost irresistible in situations where you have poor connectivity back to the remote server where the sensitive data is normally kept).

Finally, unless you want to type in your VPN keys each time you connect to said remote server, they need to be stored on the device. And they are arguably equivalent to the sensitive data, at least from a security perspective.

Your entire response is schizophrenic. Look it up.

I do Linux kernel code and device drivers for a living. As a freelancer for over a decade. I assure you, laziness and time-to-market are NOT why I don't comment my code.

Related, many have noted the general lack of commenting in the Linux kernel source code. My explanation is that it's because such comments are viewed as noise by other kernel developers. Your explanation is that most Linux kernel developers are lazy. One of us is wrong.

Turns out, clear and easy-to-follow code also optimizes like gangbusters. So by helping your fellow developers, you are also helping your toolchain give you the best it can offer in terms of high-performing output.

Truly, the only upside to complicated and hard-to-understand code is job security. The kind we don't need. Ever.

I'm not arguing with you on this point. But at the end of the day, it doesn't matter what the developer intended, because the computer can't read the developer's mind--- it can only read the code. Even in legacy systems. Which means you always have to come back to understanding the code and ignoring the comments.

Ignoring the comments also protects you from being misled by them. Why expose yourself to a risk you don't need?

If you genuinely don't want someone who can write clear code, then PLEASE DO NOT HIRE ME.

How about if I also agree not to work for you? Because I'm willing to go that extra mile. :)

Very rarely, but it sometimes happens. The rest of the time, I have to teach it. Which is why I tend to prefer developers who seem teachable, rather than developers with experience. "Experienced" developers are often the hardest to to help unlearn their old, unproductive ways due to their bias against anything different from those old, unproductive ways. Sad, but true.

I'm not a big fan of commenting code. I prefer code possessing such clarity that it is self-commenting. If your code fails this test, no amount of commenting will improve the situation. Bad code is bad code, no matter how well-commented it is. (True, some code is truly difficult to comprehend and therefore requires comments, usually because what the code is doing is supremely complicated and difficult to comprehend itself. I'm not talking about that kind of code).

Now describing the design overall, that's another matter. But most of the designs I'm called in to fix are so bad that they are undocumentable.

DIA alone will handle more than that many passengers in a month.

Don't get me wrong, as a passenger through TLV I was definitely impressed with their security system. But it definitely won't scale to USA levels.

I think it is interesting that neither the Democrats nor the Republicans are outing each other on this point. So while both try to paint themselves as being on the side of their constituents, it's clear that neither one is. Nor the President, for that matter.