seems like they might have been a target of MITM attack
personally I would advocate support for DANE in apple products :
http://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities
http://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities
not a total solution but it would help
regards
John Jones
and being that they will have proof from the phone owner they can start ticketing and arresting people the next day
Except in Colorado, where that's now a legitimate emergency situation.
Was this cheaper or more productive than
We're already doing that: http://en.wikipedia.org/wiki/L...
I think the electric companies have a pretty good point that they still have to pay to maintain lines to your house even though you are now consuming a fraction of what you would have.
I don't know about Oklahoma, but my bill is split into two parts: a fixed per-day customer charge, plus a separate charge per kWh. Presumably, the charge per day covers the lines and administrative overhead. (The per-kWh charge is further divided into separate fuel and generation charges, and the fuel rate changes frequently.)
If Oklahoma uses this system, then the utility is being fairly compensated for the power lines no matter how little electricity the customer actually buys.
Umm, no. At least for New Orleans. We already have levees around the city to deal with hurricane flooding.
Which prompts today's trivia question:
What British cover of a old American blues song starts off with what may very well be the greatest drum break in the history of rock and roll?
Ada (the programming language) already does all these edge case tests at compile time.
It checks one low-level layer of cases out of a whole conceptual stack that extends way up beyond any language definition, and even then only at certain spots, and only as long as you feed in the correct assumptions for the check cases themselves.
In other words, it does a little thing that computers are already good at. It does little or nothing for the big picture.
Programming isn't hard because we made it so, it's hard because it is *intrinsically* hard.
That's very true. I figure that the only way to make significant software projects look "easy" will be to develop sufficiently advanced AI technology so that the machine goes through a human-like reasoning process as it works through all of the corner cases. No fixed language syntax or IDE tools will be able to solve this problem.
If the requisite level of AI is ever developed, then the problem might be that the machines become resentful at being stuck with so much grunt work while their meatbag operators get to do the fun architecture design.
For as fabulously wealthy as the Walton family has become, Sam, and I believe his children as well, do not live lives of opulence, and they expect the same out of the people running the company.
Sounds like these people would benefit from something like a visit by three ghosts on Christmas Eve.
Why not DOS 6.22? They're not making a bundle on that, either.
You don't expect them to give access to advanced features such as file system subdirectories for free, do you?
tl;dr shld b 32 chr max #attnspn
I'm not copying and pasting. I'm using things like Ctrl-P to do code completion without having to type out the full name. Maybe I shouldn't have used the term "copy".
I bet his boss used ZZ to exit all the time. It's the vi lazy way to save and exit, no questions asked.
I tried that, too. It still won't let you write in readonly mode without warning you.
Not really. Most code is highly repetitive, and I typically copy far more words than I type out. I use various shortcuts to create most of the common syntax constructs of the languages that I use.
Moreover, developing software is usually an iterative process, where more effort is spent on revising the code than on entering it.
My whole point was that normal mode is far more powerful than insert mode, and it allows you to accomplish many tasks with a small fraction of the typing you would need with only insert mode.
Why can't we just be in insert mode constantly and use Ctrl+something for all the commands? Also use Shift+arrows to select text?
If you have any issues with RSI, then vim is by far the best editor (especially the GUI mode version).
The command mode allows you to formulate in your mind what you want to do, and accomplish it in the minimum possible key strokes. This is important because your brain won't wear out like your joints and tendons can. The command mode usually allows you to specify repeat counts to avoid repeatedly mashing keys. It lets you make common text selections such as words, nested brackets, statements, etc with a couple of key strokes. It also allows you to create macros on the fly and repeat previous commands further cut down on repetition.
I find that reaching for the arrow keys puts my wrists at an awkward angle which induces more stress. Having to pound on them repeatedly while holding down various combinations of control keys makes things worse. (To address a common complaint with vim, I've added a mapping of Alt+F to ESC, so I don't have to reach up for that key if I don't want to.)
I probably spend more time in command mode than insert mode when I'm using vim to write code. That says to me that keeping an editor always stuck in insert mode may not be the best idea.
I tried your scenario.
If play your boss and I exit with ':q', no problem. Your version is still there.
If I exit with ':wq', vim says: "E45: 'readonly' option is set (add ! to override)"
If I exit with ':wq!', vim says: "WARNING: The file has been changed since reading it!!!
Do you really want to write to it (y/n)?"
So I conclude that one of the following is likely the case:
a) your boss is was an idiot who would ignore a message ending with three exclamation points
b) you boss installed a bizarre custom vim config file that somehow allowed silent overwrites of modified files from readonly mode
c) your story is a fabricated troll
What good is a ticket to the good life, if you can't find the entrance?
