If more people are able to step back and think about the potential growth for the next 5-10 years, then I think the discussion would be very different.
I am grateful to be able to witness all these amazing progress play out, but am also concerned about the wide ranging implications.
This is what the kids call “cope”, but it comes from a very real place of fear and insecurity.
Not the kind of insecurity you get from your parents mind you, but the kind where you’re not sure you’re going to be able to preserve your way of life.
Sorry but I think you have it the other way around.
The ones against it understand fully what the tech means for them and their loved ones. Even if the tech doesn't deliver on all of its original promises (which is looking more and more unlikely), it still has enough capabilities to severely affect the lives of a large portion of the population.
I would argue that the ones who are inhaling "copium" are the ones who are hyping the tech. They are coping/hoping that if the tech partially delivers what it promises, they get to continue to live their lives the same way, or even an improved version. Unless they already have underground private bunkers with a self-sustained ecosystem, they are in for a rude awakening. Because at some point they are going to need to go out and go grocery shopping.
There is a massive difference between a result like this when it's a research project and when it's being pushed by billion dollar companies as the solution to all of humanities problems.
In business, as a product, results are all that matter.
As a research and development efforts it's exciting and interesting as a milestone on the path to something revolutionary.
But I don't think it's ready to deliver value. Building a compiler that almost works is of no business value.
Noone can correctly quantify what these models can and can't do. That leads to the people in charge completely overselling them (automating all white collar jobs, doing all software engineering, etc) and the people threatened by those statements firing back when these models inevitably fail at doing what was promised.
They are very capable but it's very hard to explain to what degree. It is even harder to quantify what they will be able to do in the future and what inherent limits exist. Again leading to the people benefiting from it to claim that there are no limits.
Truth is that we just don't know. And there are too few good folks out there that are actually reasonable about it because the ones that know are working on the tech and benefit from more hype. Karpathy is one of the few that left the rocket and gives a still optimistic but reasonable perspective.
Ah, two megapixel-PNG screenshots of console text (one hidpi too!), and of some IDE showing also text (plus a lot of empty space)... Great great job, everyone.
It really can replace human engineers. Mistakes and all. I've definitely written an "example" that I didn't actually test only to find out it doesn't work
I wonder if it feels the same embarrassment and shame I do too
They had GCC to use as an oracle/source of truth. Humans intervened multiple times. Clearly writing C compilers is a huge part of its training data—the literal definition of training on test data.
Wake me up when a model trained only on data through the year 1950 can write a C compiler.
The anti-AI crowd proves that they do need replacing as programmers since it was user error. Opus 4.6/ChatGPT 5.3 xhigh is superior to the vast majority of programmers. Talk about grasping for straws.
This will do the rounds on the front page of reddit with no mention of the users c library paths having issues as the root cause despite the clear error message stating that.
Seems like a nothingburger? Mostly a spammy GitHub thread of people not reading the rest of the responses.
> Works if you supply the correct include path(s)
> Can confirm, works fine:
> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
> (I followed the instructions in the BUILDING_LINUX.txt file in the repo and got the kernel built for RISC-V. You can find the build I made here if someone is just interested in the binaries)
>> Works if you supply the correct include path(s)
The location of Standard C headers do not need to be supplied to a conformant compiler.
>> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
This is not a good implementation decision for a compiler which is not the C compiler distributed with the OS. Even though Standard C headers have well-defined names and public contracts, how they are defined is very much compiler specific.
It is wild that this is getting flagged!
This is hilarious. But the compiler itself is working, it's just that the path to the stdlib isn't being passed properly
https://github.com/anthropics/claudes-c-compiler/issues/1#is...
The negativity around the lack of perfection for something that was literal fiction fiction just some years ago is amazing.
If more people are able to step back and think about the potential growth for the next 5-10 years, then I think the discussion would be very different.
I am grateful to be able to witness all these amazing progress play out, but am also concerned about the wide ranging implications.
This is what the kids call “cope”, but it comes from a very real place of fear and insecurity.
Not the kind of insecurity you get from your parents mind you, but the kind where you’re not sure you’re going to be able to preserve your way of life.
[delayed]
Sorry but I think you have it the other way around.
The ones against it understand fully what the tech means for them and their loved ones. Even if the tech doesn't deliver on all of its original promises (which is looking more and more unlikely), it still has enough capabilities to severely affect the lives of a large portion of the population.
I would argue that the ones who are inhaling "copium" are the ones who are hyping the tech. They are coping/hoping that if the tech partially delivers what it promises, they get to continue to live their lives the same way, or even an improved version. Unless they already have underground private bunkers with a self-sustained ecosystem, they are in for a rude awakening. Because at some point they are going to need to go out and go grocery shopping.
There is a massive difference between a result like this when it's a research project and when it's being pushed by billion dollar companies as the solution to all of humanities problems.
In business, as a product, results are all that matter.
As a research and development efforts it's exciting and interesting as a milestone on the path to something revolutionary.
But I don't think it's ready to deliver value. Building a compiler that almost works is of no business value.
The negativity is around the unceasing hype machine.
Noone can correctly quantify what these models can and can't do. That leads to the people in charge completely overselling them (automating all white collar jobs, doing all software engineering, etc) and the people threatened by those statements firing back when these models inevitably fail at doing what was promised.
They are very capable but it's very hard to explain to what degree. It is even harder to quantify what they will be able to do in the future and what inherent limits exist. Again leading to the people benefiting from it to claim that there are no limits.
Truth is that we just don't know. And there are too few good folks out there that are actually reasonable about it because the ones that know are working on the tech and benefit from more hype. Karpathy is one of the few that left the rocket and gives a still optimistic but reasonable perspective.
It’s a fear response.
No.
While there are many comments which are in reaction to other comments:
Some people hype up LLMs without admitting any downsides. So, naturally, others get irritated with that.
Some people anti-hype LLMs without admitting any upsides. So, naturally, others get irritated with that.
I want people to write comments which are measured and reasonable.
Schadenfreude predates AI by millenia. Humans gonna human.
I think it’s a good antidote to the hype train. These things are impressive but still limited, solely hearing about the hype is also a problem.
Ah, two megapixel-PNG screenshots of console text (one hidpi too!), and of some IDE showing also text (plus a lot of empty space)... Great great job, everyone.
It really can replace human engineers. Mistakes and all. I've definitely written an "example" that I didn't actually test only to find out it doesn't work
I wonder if it feels the same embarrassment and shame I do too
They had GCC to use as an oracle/source of truth. Humans intervened multiple times. Clearly writing C compilers is a huge part of its training data—the literal definition of training on test data.
Wake me up when a model trained only on data through the year 1950 can write a C compiler.
Would appreciate unflagging this.
Why is this flagged?
The anti-AI crowd proves that they do need replacing as programmers since it was user error. Opus 4.6/ChatGPT 5.3 xhigh is superior to the vast majority of programmers. Talk about grasping for straws.
They're literally following the first few lines of the README exactly as instructed by Claude. I don't think it's unreasonable to point out the issue
This will do the rounds on the front page of reddit with no mention of the users c library paths having issues as the root cause despite the clear error message stating that.
Seems like a nothingburger? Mostly a spammy GitHub thread of people not reading the rest of the responses.
> Works if you supply the correct include path(s)
> Can confirm, works fine:
> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
> (I followed the instructions in the BUILDING_LINUX.txt file in the repo and got the kernel built for RISC-V. You can find the build I made here if someone is just interested in the binaries)
>> Works if you supply the correct include path(s)
The location of Standard C headers do not need to be supplied to a conformant compiler.
>> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
This is not a good implementation decision for a compiler which is not the C compiler distributed with the OS. Even though Standard C headers have well-defined names and public contracts, how they are defined is very much compiler specific.
So this defect is a "somethingburger."