As a story, yes. But Terminator failed on a basic premise: Skynet becoming self-aware.
The future seems more like Blindsight [1]: hyper-intelligent, completely unconscious systems outperform, out-manipulate, and out-compete human beings purely through automated efficiency.
Careful! Some of the scenes you would think as CGI are actually using practical effects. Even a couple of scenes with liquid metal on screen were using models.
The app on your Mac today isn't a rewrite of the legendary Mac OS 7.2.1 Graphing Calculator, but an acquired app based on Curvus Pro introduced in OSX Tiger.
The first one has a legendary backstory.
2 devs snuck into Apple after their project was canceled:
https://www.pacifict.com/Story/
“We looked at each other, took a deep breath, and launched the application. The monitor burst into flames. We calmly carried it outside to avoid setting off smoke detectors, plugged in another monitor, and tried again.”
Grapher.app is different from Graphing Calculator. It came via an acquisition. All the details are here if you want to read the backstory (assuming the info is correct: https://en.wikipedia.org/wiki/Grapher)
Feels like it might be pertinent to share more details than simply the error code. What country? How are you connecting? Anything out of the ordinary with your setup that might be the cause?
I actually write prompts like that when I'm not under pressure. Claude will sometimes completely ignore your feelings, and sometimes give a little comment, which I just find refreshing in the middle of otherwise often boring sessions. And it does not have an effect on the actual result.
It does not think at all. It vibes based on its training and any additional bolted on constraints. It is a quite simple automation that only works by huge amount of existing data.
Modern man has grown quite dumb. He only seems to be able to "invent" by massive scaling things that are decades or centuries old..
Why is it bittersweet? Carpenters probably didn't cry when their tools improved.
It will be bittersweet when there's no human needed at the wheel but IMHO we are far, far from that. These models/agents are just mimicking human text and need guidance because they often get lost or stuck.
Carpenters would have cried if all their work was reduced to shoving the logs into CNC machines.
Yes there is still human input but it requires comparatively no skill or depth and it gets easier by the month. If I were lobotimized today I'd still be able to function as half-assed architect to AIs anyway.
When was the last time you read fighting distractions/getting "in the zone"/complaint about open space offices thread or comment? They used to be a weekly feature on HN frontpage.
But it's not like "shoving the logs into CNC machines". You have to understand what they are doing and point them into the right direction. LLMs very often lack common sense once you move out of easy things.
> Yes there is still human input but it requires comparatively no skill or depth and it gets easier by the month. If I were lobotimized today I'd still be able to function as half-assed architect to AIs anyway.
Hard doubt, software engineering is so much more than just literal coding and typing. At least for many of us, the coding/typing part is the easy stuff, everything around that is where the actual engineering happens. If I were lobotomized, maybe I'd get ~10% done today as the day before, if I'm lucky. Even with my full mental capabilities, the agents end up on wild goose-chases unless I'm very specific with what I want, and even sometimes ignoring things if they're too complicated/takes too long, so a bit of thinking is still required to get the right prompts.
And considering how subjective programming is, since it's a creative endeavour after all, I'm not that worried somehow all programmers will be unemployed in just some years.
> When was the last time
Frequency of something doesn't tell you how big of an issue something is, for all we know, HN community (or even the moderators) could have been tired of all the circular conversations where nothing new is being said, and downvote it. Doesn't really tell us much.
Use whatever labels you want, apply charitable reading and I'm sure even you could understand what I mean here. Clearly there are at least two sorts of tasks (or used to anyways) in "software engineering" as a whole, one more mechanical and one more about thinking.
Coding is literally writing code, instructions in plain text that control the behavior of computer. That implies knowing which instructions to write.
But creating software is much more than that. Just like writing an essay involves more than just typing words. Other activities include: Architecture, Requirements analysis, Debugging, Testing, Integration,…
I think carpenters might cry if a company went around shoving every single piece of carpentry they could find into a machine, and then when you press a button on that machine, a chair comes out, and then they go around saying that this machine will replace carpenters forever, and they made this machine with no help from other carpenters, and furniture makers all went "who needs carpenters anymore, lets just use the chair machine"
Software isn't solved. 'Coding' is, according to the people of Claude.
Coding (programming) is a tedious and expensive part of software engineering. There's other parts AI isn't doing, such as understanding and refining requirements, and delivery + accountability.
> Coding (programming) is a tedious and expensive part of software engineering.
Why is that? Coding, for me, is kinda relaxing, and the fun part of developing software. Gathering requirements, especially in a corporate settings, is the tedious part and the most time consuming.
For those unaware, this line is from the movie Terminator 2:
* https://www.youtube.com/watch?v=pJ4Ol9Tb1D0
* https://en.wikipedia.org/wiki/Terminator_2:_Judgment_Day
I clicked on the post expecting it to be something from T2 and wondered why I was reading something about emulation.
That movie has aged incredibly well!
As a story, yes. But Terminator failed on a basic premise: Skynet becoming self-aware.
The future seems more like Blindsight [1]: hyper-intelligent, completely unconscious systems outperform, out-manipulate, and out-compete human beings purely through automated efficiency.
[1] https://en.wikipedia.org/wiki/Blindsight_(Watts_novel)
Isn't that Accelerando?
Resolution-wise it hasn't due to the extensive use of early CGI.
What do you mean? The cgi is great, even today. They obviously put a lot of work and effort into it
Careful! Some of the scenes you would think as CGI are actually using practical effects. Even a couple of scenes with liquid metal on screen were using models.
That CGI looks quite OK, and even surpasses much of "modern" CGI. Have you ever seen "Flash"?
This is considering the effects were done in 1990.
The ILM documentary on Disney+ talks about the techniques on that movie, super interesting documentary in general.
'PowerPC DRC' appears to be the code in mame that translates PowerPC machine code into native host machine code (Dynamic Recompilation Core).
https://github.com/mamedev/mame/blob/master/src/devices/cpu/...
I thought it was about Renaud' song _Laisse béton_
https://genius.com/Renaud-laisse-beton-lyrics
The blog mentions a Graphing Calculator. Not sure if it shares code, but macOS still ships with an app to draw graphs, Grapher.app
The app on your Mac today isn't a rewrite of the legendary Mac OS 7.2.1 Graphing Calculator, but an acquired app based on Curvus Pro introduced in OSX Tiger.
The first one has a legendary backstory. 2 devs snuck into Apple after their project was canceled: https://www.pacifict.com/Story/
Curvus Pro: https://macintoshgarden.org/apps/curvus-pro
Thanks for sharing the links. Love this part!
“We looked at each other, took a deep breath, and launched the application. The monitor burst into flames. We calmly carried it outside to avoid setting off smoke detectors, plugged in another monitor, and tried again.”
Grapher.app is different from Graphing Calculator. It came via an acquisition. All the details are here if you want to read the backstory (assuming the info is correct: https://en.wikipedia.org/wiki/Grapher)
403 forbidden
Feels like it might be pertinent to share more details than simply the error code. What country? How are you connecting? Anything out of the ordinary with your setup that might be the cause?
I also see that error code, from Europe.
Perhaps it blocks any non-USA connection.
Singapore - 223.119.20.232
I also get 403 Forbidden, from EU, nothing special about my setup
Works for me fine
https://web.archive.org/web/20260618094143/https://rbelmont....
Asta la vista baby
Hasta* (it’s spanish)
It doesn't sound like it has an H at the beginning. Shame it hasta be like that.
A perfect example of a coding agent guided by a human with domain knowledge.
"I does not boot and it makes me sad"
I actually write prompts like that when I'm not under pressure. Claude will sometimes completely ignore your feelings, and sometimes give a little comment, which I just find refreshing in the middle of otherwise often boring sessions. And it does not have an effect on the actual result.
Codex overuses the word "quickly". I'm tempted to check what happens if I tell him to do it slowly.
It's bittersweet, isn't it. Software is solved, but at a terrible cost.
How is it solved? LLMs cannot think new things, they can only cobble something together if it's in their training set.
New things are made by cobbling together existing things.
I am not sure if claude had powerpc scripts in its training.
It does not think at all. It vibes based on its training and any additional bolted on constraints. It is a quite simple automation that only works by huge amount of existing data.
Modern man has grown quite dumb. He only seems to be able to "invent" by massive scaling things that are decades or centuries old..
That "only" part used to be the hardest. Getting the ideas was never the hard part. I think someone here even wrote an essay on that.
Why is it bittersweet? Carpenters probably didn't cry when their tools improved.
It will be bittersweet when there's no human needed at the wheel but IMHO we are far, far from that. These models/agents are just mimicking human text and need guidance because they often get lost or stuck.
Carpenters would have cried if all their work was reduced to shoving the logs into CNC machines.
Yes there is still human input but it requires comparatively no skill or depth and it gets easier by the month. If I were lobotimized today I'd still be able to function as half-assed architect to AIs anyway.
When was the last time you read fighting distractions/getting "in the zone"/complaint about open space offices thread or comment? They used to be a weekly feature on HN frontpage.
But it's not like "shoving the logs into CNC machines". You have to understand what they are doing and point them into the right direction. LLMs very often lack common sense once you move out of easy things.
Yes you have to understand when the log stuck in CNC machine, if you want to put the carpentry analogy to its extreme.
> Yes there is still human input but it requires comparatively no skill or depth and it gets easier by the month. If I were lobotimized today I'd still be able to function as half-assed architect to AIs anyway.
Hard doubt, software engineering is so much more than just literal coding and typing. At least for many of us, the coding/typing part is the easy stuff, everything around that is where the actual engineering happens. If I were lobotomized, maybe I'd get ~10% done today as the day before, if I'm lucky. Even with my full mental capabilities, the agents end up on wild goose-chases unless I'm very specific with what I want, and even sometimes ignoring things if they're too complicated/takes too long, so a bit of thinking is still required to get the right prompts.
And considering how subjective programming is, since it's a creative endeavour after all, I'm not that worried somehow all programmers will be unemployed in just some years.
> When was the last time
Frequency of something doesn't tell you how big of an issue something is, for all we know, HN community (or even the moderators) could have been tired of all the circular conversations where nothing new is being said, and downvote it. Doesn't really tell us much.
Honestly conflating coding with typing tells me your idea of coding is very different to what I used to do.
Use whatever labels you want, apply charitable reading and I'm sure even you could understand what I mean here. Clearly there are at least two sorts of tasks (or used to anyways) in "software engineering" as a whole, one more mechanical and one more about thinking.
Coding is literally writing code, instructions in plain text that control the behavior of computer. That implies knowing which instructions to write.
But creating software is much more than that. Just like writing an essay involves more than just typing words. Other activities include: Architecture, Requirements analysis, Debugging, Testing, Integration,…
I think carpenters might cry if a company went around shoving every single piece of carpentry they could find into a machine, and then when you press a button on that machine, a chair comes out, and then they go around saying that this machine will replace carpenters forever, and they made this machine with no help from other carpenters, and furniture makers all went "who needs carpenters anymore, lets just use the chair machine"
The real problem is we built the genie in the lamp or the monkey's paw: it's a machine that gives you what you ask for!
Software isn't solved. 'Coding' is, according to the people of Claude.
Coding (programming) is a tedious and expensive part of software engineering. There's other parts AI isn't doing, such as understanding and refining requirements, and delivery + accountability.
> Coding (programming) is a tedious and expensive part of software engineering.
Why is that? Coding, for me, is kinda relaxing, and the fun part of developing software. Gathering requirements, especially in a corporate settings, is the tedious part and the most time consuming.
The cost is not terrible, calm down.