Comment Re:Microsoft being Microsoft. (Score 4, Insightful) 125
The evil for which we hate Microsoft is also the reason that we all know the name. They won't ever stop being evil because that's exactly how they maintain their wealth and power.
The evil for which we hate Microsoft is also the reason that we all know the name. They won't ever stop being evil because that's exactly how they maintain their wealth and power.
They're finally going to unleash a Bob / Clippy mashup that does something.
Hilarious stories await us.
Sad ones too.
They forked SailfishOS to create a domestic OS to avoid these kinds of problems.
Russian linux devs still contribute to that tree though Linus banned their ethnicity from his tree.
Since we're all speculating, probably their phone is clunky and some Generals kept their iPhones against advice or orders because they're more featureful and convenient.
We'll hear eventually.
offering an encrypted cloud and had no way of taking backup
Which is, of course, nonsense. Nothing stops you from making a copy of encrypted data. What sucks is that for a backup, you likely can't do incremental.
That site is blocking VPN clients (sus) but here's another one you can pick up at CVS:
https://www.cvs.com/shop/ijoy-...
Imagine how much jet fuel was wasted on being stupid.
This is an example of "sometimes you can be too careful".
In your case it might simply be that there was not enough of this kind of tasks in the training data.
Exactly, we would have had cataclysmic earthquakes if the summary were correct.
The poles have shifted dramatically in recent decades and the field has weakened substantially leading to bright auroras in Florida and Hawaii at low KP numbers.
Models have the North Pole arriving at the Bay of Bengal sooner than anybody would expect. Christmas will be awkward until we change our vocabulary..
Except for trivial cases I don't think that is really true yet.
I agree in general, but not with this strong phrasing. I've let AI build a good amount of non-trivial code. But my consistent experience is that it works best when guided by an experienced coder who can correct it, and when implementing well-known algorithms rather than coming up with novel solutions.
Example: I let it write up a quadtree implementation in a language for which there was no ready solution online. It took 2-3 correcting prompts to get a good result. I could've done it myself but it would've likely taken a few hours to get it all right instead of the half or so hour it took with AI. The important part for me was that there's nothing unknown in how to implement a quadtree. All the AI needs to do is take the 100s of existing implementations and translate them into a different language.
so some coders are becoming modern day Luddites
True but too simplified. The Luddites had an entirely different motivation: The fact that factories now employed women and children at very low rates meant that the men lost their status in the family as bread winners and head of household. That was a major social disruption, which we don't have with AI.
I'd compare it more to teamsters or wagoners when cars became common. Your job is threatened by a different way of doing the same thing, a way to which your skills don't cleanly transition. Some choose to pick up the new tech, some want the old ways to persist.
In the end, coachmen became chauffeurs, because rich people prefer to be driven around oder driving themselves, no matter if it's a horse or an engine doing the pulling. But much fewer teamsters and wagoners became truck drivers.
Well I don't know, I am not a lawyer. I know that there ARE laws that penalize malicious code, like the Computer Fraud and Abuse act, and that there is a legal concept of "protestware" that draws a distinction between a bug that causes data loss and intentional sabotage. And there are also license terms that disavow responsibility for any damages that may or may not hold up if intentional sabotage is established.
But all of this is outside of my domain. I was speaking generally, that there are laws against malicious software writing/distribution in general.
Based on what I read of this story, it sure sounds like intentional sabotage to me. An instruction to an AI that orders it to destroy data sounds like a "weaponized prompt" to me. It's one thing to say "this software might have bugs or not even work at all, and those bugs might cause harm, so that's your risk to take." It is quite another to deliberately code malicious prompts as a trap with the intent of harming those who fall into it. I don't think someone can do that and say "well my hands are clean because I said you use this software at your own risk." Even if the law is gray in this area because AI is new and emerging, the social principle here is pretty clear.
Very similar here.
Somebody said the new movie has a fifty year old baby as a main character which is supposedly their key demographic.
The original star wars movies had many elements that drew in audiences at the time, including a plot about a mystical force that was guiding a new hero on a path to save the galaxy from overwhelmingly oppressive tyranny. The events were significant and the family-tie shockers injected some drama and so they were good.
But "Star Wars: The Last Flop" lost the thread. Instead of a plot that was even more epic and had even more galactic significance, it just doubled-down on the family drama and kind of lumbered around, getting us nowhere new. There was plenty more to dislike in terms of how they ruined character arks and pushed a political agenda that did not sit well with much of the audience.
Ever since then, the franchise has been sliding downhill. I read summaries of the other movies and shows and they all sounded equivalently vapid. I think I am not alone in this opinion.
You are familiar with the idea that the tool should match the job? And in particular, that some tools are very poor fits for some jobs, but that doesn't make them bad tools (since they are intended for a different job)?
MongoDB exists solely to remind us that some tools are not right for any job.
As it turns out, there are laws against deploying malicious code, too.
And for similar reasons.
IN MY OPINION anyone interested in improving himself should not rule out becoming pure energy. -- Jack Handley, The New Mexican, 1988.