@keithbostic.bsky.social
Exactly — Kaine said as much.
Even without that, the 8 sacrificial votes all came from people not up for reelection, or already retiring. Talk about bravery.
Even without that, the 8 sacrificial votes all came from people not up for reelection, or already retiring. Talk about bravery.
November 11, 2025 at 2:51 AM
Exactly — Kaine said as much.
Even without that, the 8 sacrificial votes all came from people not up for reelection, or already retiring. Talk about bravery.
Even without that, the 8 sacrificial votes all came from people not up for reelection, or already retiring. Talk about bravery.
But… well, are perfume companies failing us all because they keep serving up the same old scents that we like?
“Try this new perfume! It smells terrible!”
“Try this new perfume! It smells terrible!”
November 10, 2025 at 9:25 PM
But… well, are perfume companies failing us all because they keep serving up the same old scents that we like?
“Try this new perfume! It smells terrible!”
“Try this new perfume! It smells terrible!”
Look at the bright side: the world envisioned by OP is infinitely safer than ours. If every binary/system is different, a single attack vector for every machine on the planet is no longer possible.
November 10, 2025 at 2:38 AM
Look at the bright side: the world envisioned by OP is infinitely safer than ours. If every binary/system is different, a single attack vector for every machine on the planet is no longer possible.
I agree in principle (and ofc assembly has been successfully attacked), but that argument has never carried the day. Binaries & dependencies continue to grow in size, always have, maybe always will.
November 10, 2025 at 2:38 AM
I agree in principle (and ofc assembly has been successfully attacked), but that argument has never carried the day. Binaries & dependencies continue to grow in size, always have, maybe always will.
I think “code” is going to move up a descriptive layer, resulting in compression of what we’ll need to understand.
In the same way we don’t have to understand assembly, we won’t have to understand the new AI layer that will sit between us and the machine.
In the same way we don’t have to understand assembly, we won’t have to understand the new AI layer that will sit between us and the machine.
November 10, 2025 at 2:13 AM
I think “code” is going to move up a descriptive layer, resulting in compression of what we’ll need to understand.
In the same way we don’t have to understand assembly, we won’t have to understand the new AI layer that will sit between us and the machine.
In the same way we don’t have to understand assembly, we won’t have to understand the new AI layer that will sit between us and the machine.
I think AI is the way out of that trap. Programmers use functions with per-case branching instead of inline code to limit what a human has to understand. AI can understand it all without limit.
Memory size/costs are still real, though, unless run-time code caching has gotten better than I know.
Memory size/costs are still real, though, unless run-time code caching has gotten better than I know.
November 9, 2025 at 10:14 PM
I think AI is the way out of that trap. Programmers use functions with per-case branching instead of inline code to limit what a human has to understand. AI can understand it all without limit.
Memory size/costs are still real, though, unless run-time code caching has gotten better than I know.
Memory size/costs are still real, though, unless run-time code caching has gotten better than I know.
Obvious technical problems with that, but OK.
Aren't there economic reasons it's not likely?
Unless you're the vendor of both the legacy OS and the new AI platform, the legacy OS is just sitting there and it's a lot cheaper to use it than roll your own.
Aren't there economic reasons it's not likely?
Unless you're the vendor of both the legacy OS and the new AI platform, the legacy OS is just sitting there and it's a lot cheaper to use it than roll your own.
November 9, 2025 at 9:56 PM
Obvious technical problems with that, but OK.
Aren't there economic reasons it's not likely?
Unless you're the vendor of both the legacy OS and the new AI platform, the legacy OS is just sitting there and it's a lot cheaper to use it than roll your own.
Aren't there economic reasons it's not likely?
Unless you're the vendor of both the legacy OS and the new AI platform, the legacy OS is just sitting there and it's a lot cheaper to use it than roll your own.
There are some real-time instruction translators in the real world (Rosetta comes to mind), but yeah, it will be a paired or layered solution for some time, maybe forever.
I do agree with OP that bespoke/multiple systems is where we end up.
I do agree with OP that bespoke/multiple systems is where we end up.
November 9, 2025 at 9:42 PM
There are some real-time instruction translators in the real world (Rosetta comes to mind), but yeah, it will be a paired or layered solution for some time, maybe forever.
I do agree with OP that bespoke/multiple systems is where we end up.
I do agree with OP that bespoke/multiple systems is where we end up.
Yes, got it.
I read OP as suggesting a bespoke OS that runs alongside, or on top of, the traditional OS, not a new OS that runs all of your POSIX 1003.1 + games + Office applications.
I understand your objection now, and I agree OP was at least nodding to your reading.
I read OP as suggesting a bespoke OS that runs alongside, or on top of, the traditional OS, not a new OS that runs all of your POSIX 1003.1 + games + Office applications.
I understand your objection now, and I agree OP was at least nodding to your reading.
November 9, 2025 at 9:42 PM
Yes, got it.
I read OP as suggesting a bespoke OS that runs alongside, or on top of, the traditional OS, not a new OS that runs all of your POSIX 1003.1 + games + Office applications.
I understand your objection now, and I agree OP was at least nodding to your reading.
I read OP as suggesting a bespoke OS that runs alongside, or on top of, the traditional OS, not a new OS that runs all of your POSIX 1003.1 + games + Office applications.
I understand your objection now, and I agree OP was at least nodding to your reading.
Still confused.
A couple of examples, please?
A couple of examples, please?
November 9, 2025 at 9:16 PM
Still confused.
A couple of examples, please?
A couple of examples, please?
I would say the backing formats are reasonably well-defined already, and the AIs are happy to use whatever front-end API you like.
Where's the software incompatibility problem?
Where's the software incompatibility problem?
November 9, 2025 at 9:06 PM
I would say the backing formats are reasonably well-defined already, and the AIs are happy to use whatever front-end API you like.
Where's the software incompatibility problem?
Where's the software incompatibility problem?
We have real data: self-driving cars are safer than human drivers. People do die from autonomous cars, but overall fewer people will die if we switch to autonomous vehicles.
AI [repeat argument].
TBC, I'm fine being *wrong* about AI, but bring the data, don't cherry-pick a failure.
AI [repeat argument].
TBC, I'm fine being *wrong* about AI, but bring the data, don't cherry-pick a failure.
November 9, 2025 at 7:30 PM
We have real data: self-driving cars are safer than human drivers. People do die from autonomous cars, but overall fewer people will die if we switch to autonomous vehicles.
AI [repeat argument].
TBC, I'm fine being *wrong* about AI, but bring the data, don't cherry-pick a failure.
AI [repeat argument].
TBC, I'm fine being *wrong* about AI, but bring the data, don't cherry-pick a failure.
Explain please?
(Asking for a friend.)
(Asking for a friend.)
November 7, 2025 at 9:26 PM
Explain please?
(Asking for a friend.)
(Asking for a friend.)
A pretty calorie-dense lunch.
November 7, 2025 at 7:51 PM
A pretty calorie-dense lunch.