I have the opposite sense. The AI labs have been allowed to vacuum up the entire history of human knowledge because we as a society expect it to have a net benefit. They should be glad that they're still allowed to operate. Don't like it build another planet with it's own history etc.
Uhm, I'm not a programmer but why isn't this a good look? I would want my engineers to fix problems that they notice in passing. (Edit: the "unnecessary work" angle is what irked me in the article)
Good SWEs get a feel for the minimum amount of changes to fix something. Fewer changes usually minimizes the chance for new problems to pop up.
Junior SWEs usually try to do too much.
This. There should be 2 PRs. The core fix, the the unrelated fixes. Because I guarantee sometimes those unrelated fixes will cause regressions so they have to be scrutinized too.
Issues are automatically closed after being inactive for too long. It's also true that many issues that are filed there have nothing to do with Claude Code proper. To conclude, these numbers (either many open, or many closed, or any relationship between them) a-priori mean nothing either way.
Thanks. I'm not a programmer so I can't understand what is happening in the kernel by looking at the changelog, so I'll ask: Are the problems remediated structurally so that nothing like it can occur in the future, rather than just patching it up? Are there "lessons learned" that are being applied and documented here (like, "this problem looks like it's shape transports to other subsystems as well, let's fix them all in a disciplined way")?
I can't comment specifically on the Linux kernel piece, but I want to point out, broadly, that security has generally been an afterthought, and very little gets invested into it in terms of time and money - as a general rule.
Multiply that behavior times the number of commercial and mobile and b2b apps over 50+ years, and that's where we are.
There will likely be many more leaks, and hacks, and outages. And then in trying to be proactive to fix old systems, that will cause new proactive outages, and then eventually many things will be better.
But, it's going to take a lot of time and investment, and a lot of (majority) of currently unsupported devices will have to be complete replaced / scrapped / ewaste. On the scale of Nation-State initiatives.
This is across all operating systems, firmware, software and devices of all kinds, etc.
LLMs to security are like a bomb went off. We still have to wait for things to fall over before the dust will even clear enough to see what we have to work with.
I thought Carbon for composable stood well on it's own marketing. As did Argon, for impervious. Next to one another the pair comes off utterly cockeyed and sleazy.
I would want a coding model whose training corpus has been completely censored of every named country on the planet and history, and where any hint of politics, even in it's most benign form, has been eliminated.
Tired of tribalism, even if emergent and unintentional. Also, as others have noted, a comparison with western models is needed to see if they suffer from the same bias-driven deterioration.
I understand the desire for something like this, but it's very naive. Different countries had unimaginably different histories which directly propagate to different cultures and values. *This is not natively bad thing*.
The problem arises when people bring in normativity when talking about these differences. It's okay to acknowledge that other people are different than you. This is a good thing. I don't want a grey homogenous world.
I think that's aspirational, whereas the censoring of training data can reasonably be operationalized. Whether it'll work out in practice and produce something of value, I have no clue. [Edit: sorry, I see what you mean. Yes, I concede that rebuttal.]
Tangentially: The costs could be justified even if it doesn't turn into profit, no? Because if the price of good, robust software plummets, then that itself would be a a solid return on investment for the world.
Assuming they can achieve funding without IPO probably yes. But if they can't there's always the dilemma that "if [good guys] won't do it then [bad guys] will". I'd like to think that the leadership at anthropic is principled even if the actions of the company as a whole has been less than stellar morally speaking. I'd be curious to see their moral calculus transparently laid out in public.
This is weird. I can't think of a better compliment that is simultaneously safer. They'll always trail on data generation then, no? So I can't see the point. Best case for moonshot they get to lie about benchmarks that are gamed regardless, is how I see it.
I find the language less impervious than has been suggested generally, but that it's reasoning is astonishingly, unbelievably bad. Not sure why the focus has been only on language, am I the only one seeing this?
My impression from working with claude code far more than is good for my sanity is that Claude's human comprehensibility is fractally messed-up. On more superficial levels, this looks more like a "language" thing: it has all these obnoxious lexical tics and so on. But the more time you spend with it, the more you notice it's similarly messed up on deeper and deeper levels. I think that's what you're seeing.
This gets into interesting weeds. It might get to a point where to actually "upskill" it might have to start sounding less and less human, "less and less agreeable to humans" being a waypoint to that ...
... to where, at some point, it might even begin to construct semantic loadings (heh) that are completely ininteligible to us while still superficially sounding like something we'd recognize.-
This is basically what I believe, too. Its outputs are generally syntactically correct human-language sentences, but semantically, and especially at higher levels of abstraction, it is no longer correct to think of them as human language.
I'm feeling this too. Like how many times in a day do I have to see "that changes what I told you earlier" before I just want to put this thing in the trash and forget about it.
reply