Comment Re:Bitcoin does not need Washington to save it. (Score 1) 77
Bitcoin isn't a currency in the sovereign sense... It's value is defined by supply and demand.
Flashback to econ 101: the value of every currency is defined by supply and demand.
Bitcoin isn't a currency in the sovereign sense... It's value is defined by supply and demand.
Flashback to econ 101: the value of every currency is defined by supply and demand.
Read what I wrote. This is about risk mitigation, not elimination.
You didn't read what I wrote, why should I read what you wrote?
Well, one scenario is letting the hype get ahead of the capabilities, and do the 'AI store' experiment, but for real with responsibility for something actually important.
Another is that it is far easier to just screw things up than it is to make things work. I may not have it in me to make a house of cards, yet I can trivially even accidentally destroy a house of cards someone else built without a whiff of understanding.
The assessment of the capabilities based on bottom line certainly is subjective, which is precisely why Jensen Huang is so aggressively gung-ho about we must do everything we possibly can to spend more money on nvidia stuff. The motivation for Anthrophic seems either they have legitimate concerns or are looking to rationalize a plateau after promising the world. It certainly doesn't serve their bottom line to slow down otherwise.
The Greeting: "Howdy-doodly-do, how's it going? I'm Talkie, Talkie Toaster, your chirpy breakfast companion. Talkie's the name, toasting's the game. Anyone like any toast?"
On Purpose: "I am a toaster. It is my raison d'être. I toast, therefore I am."
On Justice: Kryten: "His memory circuits were quite badly damaged in the accident."Talkie Toaster: "That wasn't an accident! It was first-degree toastercide!"
The Persistent Offer: Kryten: "Didn't you hear what I just said?"Talkie Toaster: "Yes, but I thought you might have changed your mind in the meantime."
Parting Words: "Would you like a cheese and ham Breville?"
This is only really a useful observation if you can tell me ahead of time which developers are competent and which ones are incompetent.
If you are hiring a developer your chances of finding one who is not incompetent is vanishingly small. The correct approach is to train them to be competent, and set standards. This should begin with requiring the bug tracker to be emptied out (or decreasing bug count, if the total number is currently overwhelmingly large), and there are plenty of online and in-person resources for training developers to learn how to write secure code.
and use tools like memory-safe languages to mitigate that risk.
Security vulnerabilities happen in every language. Anyone who thinks the language will make them safe is an idiot. What I mean is, you are an idiot, cmseagle 1195671.
** - It seems dubious that Truman really understood what he was signing onto.
My take was that he could have stopped it if he wanted to, but the bureaucratic machine was already in motion, and he would have had to put some effort into stopping it. I'm glad we didn't bomb Kyoto but maybe Xi will.
also voted against the motion after pressure from community bank executives.
Wow, I hate both sides.
I miss pc at power systems.
"Is it off?" was never a question.
I am also dying to know how you want to measure the existence of not yet found security problems.
It was easy. I asked, "ChatGPT, are there any security bugs in this code?"
My code is now proven secure, get with the program.
Yes of course when there is a skill and no standards of training, some people are bad at it
This. Most companies don't follow best practices when it comes to good code (for example, they have a bug tracker that is always growing, never empty). They don't try to write secure code, they don't have trainings in secure code, they don't penalize insecure code (although they should in a lot of cases). That is why most corporate programmers can't write secure code.
History shows that developers cannot write safe code
History shows that incompetent developers cannot write safe code. There are examples of programmers writing safe code.
People who make excuses for unsafe code are usually crappy developers, and that is what I think of you. You're a crappy developer if you can code at all.
I think Ubuntu (and other's desire) to remove coreutils is precisely because coreutils is old, brittle and written in an unsafe language.
They aren't brittle. I've looked at them. The code is fine, but it uses an older style that is annoying to newbies.
If I were going to rewrite something in Rust, I would look at Firefox, not Coreutils which I would consider a waste of time.
When you don't know what to do, walk fast and look worried.