I hope the people who need to read this do, but I am far from sanguine
NIST proposes barring some of the most nonsensical password rules arstechnica.com/?p=2052508
I had forgotten that you need to set the DB_INDEX_COMPRESSION_INHERITANCE parameter to inherit index compression from the tablespace. Yet again, @connor_mc_d to the rescue:
connor-mcdonald.com/2020/10/…
Roger retweeted
Join Kothanda Umamageswaran and Jia Shi to learn how Oracle’s next-generation Exadata cloud can provide extreme performance for #AI, analytics, and mission-critical workloads at any scale. xitter.cf/i/broadcasts/1OdJrjDQl…
Jia Shi is always worth listening to
Our #Exadata Exascale event is almost here! Register today to learn how our next-generation Exadata cloud can provide extreme performance for AI, analytics, and mission-critical workloads at any scale. social.ora.cl/60189OwbI
This ->
Unpopular opinion: We will not achieve AGI any time soon and @leopoldasch's prediction is way off.
Here's why:
1 - The Straight Line Fallacy
One of the most common mistakes in predicting technological advancements is assuming that progress will continue in a straight line. This belief doesn’t account for the possibility of an "AI winter," a period where advancements slow down or stop due to unexpected technical challenges or diminishing returns.
History shows us that progress doesn’t happen in straight lines. Look at the transition from horses to cars. It wasn’t a smooth, continuous progression. There were bursts of rapid development followed by long periods where nothing much happened. The same can happen with AI. In physics, we've seen significant slowdowns despite continuous efforts.
Similarly, in medicine, the fight against cancer has not progressed in a straight line; breakthroughs are followed by long periods of incremental progress or even setbacks.
2 - The AGI Definition Problem
First, we don’t even have a clear definition of AGI.
Leopold’s statements highlight this confusion: On one hand, he says it’s "strikingly plausible that by 2027, models will be able to do the work of an AI researcher/engineer." On the other hand, he claims, "We are on course for AGI by 2027."
These are vastly different capabilities. The lack of a clear definition muddles the discussion.
3 - The Compute Problem
Even if we assume that all we need to achieve AGI is more compute power, we face significant hurdles. The production of GPUs and other essential components is already hitting resource limits.
The environmental impact of the massive energy consumption required for training these models could lead to regulatory restrictions. So, even if more compute is all we need, who’s to say we’ll have enough of it?
4 - The Limits of Current AI
@ylecun often points out that current LLMs, despite their impressive capabilities, are fundamentally limited.
They don’t understand the real world, they often generate incorrect information, and they can’t plan or reason beyond their training data. These are not minor issues—they’re fundamental gaps that more data and compute power alone won’t fix.
Final Point: The Influence of Corporate Hype
There’s another, less talked about aspect of the AGI debate: corporate hype. The talk of AGI has been hijacked by corporations looking to benefit from millions of $ of free marketing the term generates.
Don't fall for the hype.
---
Let me be clear that this is not an attack on Leopold (awesome guy) but my personal opinion on the subject.
Roger retweeted
The maximum number of columns in a table in Oracle Database 23ai increases from 1,000 => 4,096
To allow this first you must set the parameter
MAX_COLUMNS = EXTENDED
@connor_mc_d shows you how youtube.com/watch?v=7KS7cN2Z…
Nowhere near enough of the coverage has been over the hero who chose a multi cloud solution - that is literally the only thing that saved them from catastrophe.
Google Cloud accidentally nukes customer account, causes two weeks of downtime trib.al/3vtuNfI
Roger retweeted
In today's episode of "Multilingual Engine/JavaScript" offers _so many new possibilities to do cool things_" I would like to present to you: creating GraphQL endpoints in Oracle Database 23ai. martincarstenbach.com/2024/0…
Oh, the memories! Z80 was the first assembler I learnt (followed by Motorola 68008)
apple.news/AvrKEqu4rRTi-Km2B…
Roger retweeted
Looking for an new job as C developer?
careers.oracle.com/jobs/#en/…
Please share!
#JSON #Databases #coding #job
Oracle: New blog post from Andy Rivenes on how to know when the Exadata column cache kicks in:
blogs.oracle.com/in-memory/p…
The reason that SQL is pronounced Sequel is, "we had to change the name of our language from SEQUEL to SQL ... because of a legal challenge that came from ... Hawker Siddeley ... SEQUEL was their registered trademark."
It started as Structured English Query Language. They removed the vowels from SEQUEL to get SQL.
See mcjones.org/System_R/SQL_Reu…
Now you know.













