FortyCharacterCobolNamesLikeThisForExample and all.
FortyCharacterCobolNamesLikeThisForExample and all.
This really is a moronic article. Programming language choice is not about "popular" or "cool" - it's whatever tool gets the job done.
For a hobby? Sure. Otherwise it's about whatever tool gets the paycheck done. Java sucks today and isn't the best tool for any job, yet it dominates the job market. It was a bad tool 15 years ago, and it will be a bad tool 15 years from now, when it will still dominate the job market. And by then, sadly, $10 computers will run Java easily.
C will always be the kernel guy's tool, and those jobs pay nicely, but there will never be very many of them. C++ has faded (despite being a darn good language with the latest standard, too many burned bridges). C# will go down with the Microsoft ship. Will one of the new fad languages have staying power? Maybe. Likely 1 of them will, if not a current one. But fucking Java just refuses to die.
Knighthood only overlapped with religion in a few times and places - it was really just cavalry. "Chivalry" meant "horsemanship" for most of the time the word was current, and only came to mean "and other things knights should do" towards the end.
Human nature doesn't change, nor does the need to protect civilization from assholes. However, combat robots will fundamentally redefine "arms" in the coming decades, and there's no telling what that looks like.
All who fly them low enough deserve the hate. You don't see many people upset about drones flying high enough that you can't see them, or they're just a dot. It's the assholes who buzz animals, peek into upper story windows, disturb your family in your back yard, that sort of thing.that draws the hate.
In some states, it is perfectly legal to shoot someone on your property as long as you say the magic words "I was in fear for my life". Of course, it would be awkward if your target survived the shot and told a different story, but that problem has a straightforward solution.
True story from Texas: my mother bought a gun after a couple of break-ins. She asked the cops what the rules were. The explained that she should make sure he "falls inside the house *wink*" and that he doesn't survive.
How high it extends is defined by law (state by state), but is something like "the higher of 50 feet or the tallest nearby building". TFS says this drone was under 30 feet, which is just obnoxious (especially near livestock).
I'm waiting for the lawsuit where one of their laptops is so thin it slices up a user's hand.
In the early days of America, most of the colonies had a law requiring you to bring your gun to church, at least for men, in case something/someone needed shooting that week. Similar laws predate guns, going back, well, as far as we have written records of laws . Many cultures, perhaps most, have required citizens to keep arms in good condition. Heck, mostly what defined a "knight" from roman times to medieval was that your could brings better weapons to the fight.
I wouldn't be worried about his fines, I'd be more worried about the consequences of shooting at an aircraft in federal airspace.
That's a federal crime that could net you up to 20 years in jail.
It depends on the state, but somewhere around 50 feet it stops being "airspace" and starts being "your property". Much like you're still trespassing if you climb a tree.
All my data is stored on a CPM machine with no networking capability. I hand code all binaries in Assembly Language. Never had a breach.
For a long time, the GAO ran all its internet-facing servers on Netware. I don't think they had a breach during those years. I've always thought that was a clever strategy, if only because the list of people who could hack on the Netware kernel was so small.
These days I'm not sure if there really is a platform you could make work in production but is so obscure that no one bothers developing exploits for it. Maybe a mainframe OS, now that the financials have left mainframes behind? But then, government-funded attackers can develop expertise in whatever oddball system they need to, so maybe those days have passed.
It is vital to keep pace with the changing regulatory and technology landscape to safeguard and advance business objectives. Working backwards by identifying and understanding future risks, predicting risks and acting ahead of competition, can make a company more robust
Wow, buzzword bingo in a single quote. Where's Weird Al when you need him? Right here!
This consultant must have been toning it down though. I would have a expected a "proven methodology" and "commitment to quality" in there somewhere, and maybe a "seamless integration" too.
The word filter is particularly egregious since that's a component you just buy. There's not even the excuse of "small dev team in a hurry" for that one. I have a feeling it's a related bug to the punctuation thing, where what they're running through the word filter isn't quite what you type. How they screw up "user-provided string" is a different question.
I wonder how man variations on "Planet'); DROP TABLE Players; --" there are by now.
Hint: no, stop making excuses for them, Hello Games was simply lying.
Each world is procedurally generated from a 64-bit key, plus some randomness (especially post-creation). If two players, each in their single-player game, go to the "same" planet, sure, it will look about the same but there's no unique server-side world. It's just two people at the same coordinates each of which independently generated a world from the same seed.
Sure, the worlds look sort-of the same, mostly, but there are going to be more differences than in a traditional single-player game or MMO, because the random elements are different in each person's single-player game.
My backup strategy is simple:
1. 8TB RAID 1 NAS for everyday use
2. Periodic backups of the NAS using rsync to a backup disk I keep offsite
3. Encrypted backups to Google Drive (slow, but FREE)
The problem with NAS is that if you ever get hit by a disaster or ransomware attack, you lose it all. You need a backup of your NAS data offsite and offline.
I am currently running the Western Digital Mirror Gen 2 which let's you plug in a USB 3.0 device, then use SSH to access the device, then use rsync to update your backup. Always, unmap the NAS from any systems before hand to prevent a ransom-ware attack.
rsync -aHAX source_dir dest_dir
The trick to keeping data safe if making lots and lots of copies. This is what cloud providers rely on.
After that, you could use near line storage like archival quality Blu-Rays 50GB or get an LTO3 tape drive and write 800GB (almost 1 TB).
I've always wondered about USB3.0 to UltraSCSI converters. Do these work?
That could be a good solution.
For those who have someone escaped the drama associated with NMS and want to learn what all the fuss is about, this review does a great job of explaining - not just listing the missing features, but showing the emotional impact it had on fans who were incredibly hyped for the game.
There are some scam games on Steam that are designed to last two hours to get past the refund limit.
No Man's Sky is one of these.
I think that may be accidental - at least, I don't credit the devs with the skill to cook that up. The problem here is that the game is missing nearly every promised feature, but there's no way to discover that until you leave the first planet. Then it all turns to shit. The timing, specifically, was likely a coincidence, but Hello Games definitely knew what they were shitting out.
Also, the game crashes frequently even on console, but it can go hours between crashes. For PC, we're used to that sort of shit, and while I think that's still worth a refund, you wouldn't get mass outrage. On the console OTOH, Just Works (TM) is the freaking point of console games.
Still, had the game not been missing almost every promised feature, I think the player base would have been content to wait for a patch to fix the crashes.
"Well, if you can't believe what you read in a comic book, what *can* you believe?!" -- Bullwinkle J. Moose