[00:00] (0.00s)
Hey everyone, welcome back to the
[00:01] (1.28s)
channel. My name is John and this is
[00:02] (2.56s)
your modern tech breakdown. Today I'm
[00:04] (4.48s)
looking into OpenAI's latest delay and
[00:06] (6.48s)
releasing its openweight model. Let's
[00:08] (8.24s)
jump into it.
[00:20] (20.40s)
All right, for the second time in as
[00:21] (21.84s)
many months, Sam Alman has delayed the
[00:23] (23.68s)
release of OpenAI's open weights model.
[00:26] (26.00s)
this time saying that the company needs
[00:27] (27.68s)
additional time to run safety tests and
[00:29] (29.44s)
review high-risisk areas. And notably,
[00:31] (31.68s)
he did not give a timeline for when that
[00:33] (33.52s)
work would be done. Now, if you believe
[00:35] (35.44s)
that they are delaying their release for
[00:37] (37.20s)
safety tests, I have a bridge to sell
[00:39] (39.12s)
you. But let's have some fun speculating
[00:41] (41.12s)
on what the real reason is. So, if you
[00:43] (43.20s)
recall, this model was supposed to come
[00:44] (44.72s)
out back in June, but it was delayed
[00:46] (46.48s)
then with Sam saying at the time, we're
[00:48] (48.48s)
going to take our time with the open
[00:50] (50.32s)
model. So, if you've been in a pressure
[00:52] (52.56s)
situation like Sam is in, you'll know
[00:54] (54.64s)
that when the team comes to you needing
[00:56] (56.56s)
more time, your first question is going
[00:58] (58.64s)
to be, well, if it can't be done on
[01:00] (60.72s)
time, when can it be done? And if you
[01:03] (63.04s)
read Sam's comment closely on the first
[01:05] (65.28s)
delay, he said, expect it later this
[01:07] (67.76s)
summer, but not June. So, I highly doubt
[01:10] (70.08s)
Sam made this time frame by himself.
[01:12] (72.32s)
This was clearly something that was
[01:13] (73.68s)
discussed inside OpenAI. So, I think we
[01:16] (76.32s)
can assume that as recently as June,
[01:18] (78.08s)
people inside OpenAI believed they could
[01:20] (80.48s)
release this open model in July or
[01:22] (82.24s)
August. But now, if we look at Sam's
[01:23] (83.92s)
comments on this latest delay, Sam did
[01:26] (86.16s)
not give a timeline this time. So, it
[01:28] (88.00s)
seems possible to me that the team has
[01:29] (89.68s)
blown through the first extended time
[01:31] (91.44s)
frame and hasn't made the progress that
[01:33] (93.20s)
they expected to make. Now, what kind of
[01:35] (95.36s)
activities could they be working on that
[01:37] (97.20s)
are hard to predict how long they're
[01:38] (98.64s)
going to take? I would speculate that
[01:40] (100.24s)
OpenAI may be working on improving the
[01:42] (102.32s)
model's performance against benchmarks,
[01:44] (104.16s)
so-called benchmark hacking. Obviously,
[01:46] (106.64s)
I don't know this to be true, but OpenAI
[01:49] (109.04s)
has had a reputation as having the best
[01:51] (111.44s)
models, and they've been fairly crafty
[01:53] (113.52s)
with their bragging about performance
[01:55] (115.20s)
against benchmarks. In fact, I covered
[01:57] (117.52s)
in the past where back in December of
[01:59] (119.84s)
2024, it came out that OpenAI had been
[02:02] (122.96s)
financially supporting the work of the
[02:04] (124.56s)
nonprofit Epic AI to create the Frontier
[02:08] (128.24s)
Math benchmark. And apparently, there
[02:10] (130.08s)
was a handshake deal where OpenAI agreed
[02:12] (132.56s)
not to train their models directly on
[02:14] (134.48s)
the answers to this benchmark. And I
[02:16] (136.56s)
guess we're just all supposed to take
[02:17] (137.76s)
their word for it that they didn't. But
[02:19] (139.92s)
clearly, benchmark performance is
[02:21] (141.76s)
important to OpenAI and its reputation.
[02:24] (144.16s)
And if I had to guess, I think they are
[02:26] (146.72s)
busy trying to tweak this model to
[02:28] (148.48s)
perform better on some benchmarks, which
[02:30] (150.96s)
really doesn't make the model any more
[02:32] (152.56s)
useful. It's really just getting the
[02:34] (154.32s)
model to memorize some answers for the
[02:36] (156.08s)
evaluation. But before any OpenAI
[02:38] (158.16s)
lawyers come after me, I obviously have
[02:39] (159.76s)
zero evidence that this is what is going
[02:41] (161.36s)
on. It just seems to fit the situation
[02:43] (163.12s)
nicely and could be plausible. So, for
[02:45] (165.60s)
now, this is my guess on what's causing
[02:47] (167.52s)
this delay for OpenAI. But what do you
[02:49] (169.84s)
think? Do you have a better explanation
[02:51] (171.36s)
for this shifting timeline? Leave a
[02:52] (172.96s)
comment down below. As always, thanks
[02:54] (174.56s)
for watching. Please like, comment, and
[02:56] (176.00s)
subscribe.