For example, an occupied self-driving car better be closer to its destination than a large fire / volcano / etc.
910 karma · joined July 13, 2009
For example, an occupied self-driving car better be closer to its destination than a large fire / volcano / etc.
Can Alberta apply it to oil and gas companies too?
Maybe they should ask an AI to create one!
The promise could be re-interpreted in some funny ways. For example, Count Binface didn't specify when nationalizing Adele would occur.
They could create another[0] special case in UK copyright law with a minor twist: Instead of eventually entering the public domain, the copyright of Adele's works would transfer to the UK government which would donate any proceeds to a charity that builds affordable homes.
Silly, but it'd mean two promises kept.
[0] https://neverlandofficial.com/discover/peter-pan-copyright/
I didn't describe such qualities of C in my previous post. At all.
And to be clear, I didn't mean "devs who learned how to program in the 1990s". I meant "devs who were active in the 1990s", which would have mostly been devs who came up in the 1970s and 1980s (where learning BASIC, then assembly was common).
I also made no claim about first languages in my previous statement. I only said there was a likely progression from assembly to C or C++ (for a C++ dev).
My point was, the talent pool in the 1990s would be able to handle the downsides of C++, and the upsides would have been a bonus. Whereas modern devs aren't used to the downsides, thus C++ is a step back for them.
What I should have added is that for devs in the 1990s, there would have been very few large legacy C++ codebases.
Time has moved on.
More importantly, a typical 1990s C++ dev was likely someone who learned assembly, then C or C++. Meaning they already knew how to control hardware / memory allocation, and C++ was just a new set of abstraction tools. It was a step forward for them.
To modern devs, C++ is a step backwards. And a tough one at that.
without sharing tech to make the ASI, you'd hope humanity could work together to determine how to align an AI for our common benefit.
Not 100% apt, but close enough.
My bet is something _like_ assembly, but not assembly.
That being said, I think humans will still program for fun. Just like we paint portraiture in a world with cameras.
I'm happy to see this acknowledged, and hope it's a sign that they appreciate the difficulties of winter driving.
Meanwhile American police are consistently depicted as trigger happy, shooting at any minor provocation.
If an over-the-air patch can have that kind of impact, then what happens if security is compromised and that power is used for ill?
It's messy. But I'd much rather that than need to ask "What would Pierre Trudeau think of this situation?"
"This Hour has 22 Minutes" had a great sketch where both a Francophone (Gavin Crawford impersonating Chantal Hebert) and an Anglo (I forget who) were stumbling over proper nouns from the opposite language. The joke was that both were trying too hard to pronounce things "properly". It came off as inauthentic and awkward.
Even then, I don't understand why being a landlord to the place were AI is trained would be financially exciting... Wouldn't investing in NVIDIA make a lot more sense?
What is the minimum amount of aggression necessary to evolve sentience? What is the maximum amount of aggression in an interstellar space-faring species? Where is humanity on that scale?
A super-aggressive species would likely self-annihilate before possessing sufficient energy to travel interstellar distances... So the jury's still out on us.
Soon LLMs will be able to write Fortran in any language!
You could also inherit a massive codebase old enough to need a prostate exam that was written by many people who wanted to prove just how much of the language spec they could use.
If selecting a job mostly under the Veil of Ignorance, I'll take a large legacy C project over C++ any day.
"Here's a bug report, fix it."
"Here's a bug report, an explanation of what's triggering it, fix it."
"Here's a bug report, an explanation of what's triggering it, and ideas for what needs to change in code, fix it."
"Here's a bug report, an explanation of what's triggering it, and an exact plan for changing it, fix it."
If I have to spoon-feed as much as the last case, then I might as well just do it. The second last case is about the level of a fresh-hire who is still ramping up and would still be considered a drain under Brook's Law.
I suppose the other axis is: How much do I dread performing the resultant code review?
Put them together and you have a "spoon-fed / dread" graph of AI programmer performance.
There's a difference between an executed image and a display-only image.
At a certain point, judgment requires technical knowledge.
Were I to write a scripting language, trivial export to .so files would be a primary design goal.
Never used the service though.
Zero support for any legislation other than Canadian Separation. Be a poison pill.
And that's the non-violent response.