It simply forgets code exists during a port. It will port part of a function and ignore the rest, it will scan a whole file into context and then forget that a different codepath exists.
I would never rely on it for a 1:1 mapping of large features/code transformations. Small stuff sure, but beyond say a few large files it will miss things and you will be scratching your head for why it's not working.
Sometimes, it also tells you it is done, but if you look at the code, there's a bunch of placeholder comments in the style of "will implement this later if we figure out how to do it".
Indeed, all of the above.
It's impossible to just say "Here is the original file, here is the new file, port everything over" and think that'll be enough.
Maybe making a plan for each file and specifically tell it to port each specific function over would work, but at that point you're really just making a literal translation from one language to the other.
Is it a given that they need to unrealistically hype everything? To me it just seems like he's killing any and all credibility he had
Probably a bad long term strategy?
I mean other non-AI companies use hype too sure.. but it's maybe a little sprinkle of 1.1x on top aimed to highlight their best features. Here we're going full on 100x of reality
> To me it just seems like he's killing any and all credibility he had. Probably a bad long term strategy?
He's already got more money than God and there's an infinite supply of suckers who think wealth and skill/intelligence are correlated for him to keep feeding off of (see also Goop and Tesla, incredibly successful companies also run by wealthy hucksters). Sam Altman will be just fine.
It's not a given but Altman is a public figure for a reason while I don't know the names of any of the other CEOs off the top of my head. He talks a lot and when he talks, it's about AI. Even talking about the dangers of AI is hype because it implies it's an important topic to discuss now because it's imminent.
The article refers to the banality of evil in realation to Eichmann. There's actually been quite a bit of historical push back on this assertion, which in some ways has been used to rehabilitate Eichmann's image as a bureaucrat. Eichmann while not the chief architect, was definitely partly responsible for the Holocaust's "success" and actively climbed the nazi hierarchy by finding a niche to fill - exterminating jewish people.
I always thought "the banality of evil" wasn't about minimizing the horror of his actions. It's not saying "what he did wasn't so bad," but "these horrible actions were done not by an obvious villain, but by someone personally unremarkable."
In addition to the push back there's the fact that Hannah Arendt -- who coined the phrase "banality of evil" -- was also a lover of Martin Heidegger.
Heidegger was an enthusiastic Nazi and Arendt also defended him. Some people see the "banality of evil" book as essentially being a defense of Eichmann.
It should be in all standard encyclopedias, but it's certainly in Britannica and Wikipedia. Usually I like to cite Wikipedia, but I'll add Britannica in case people have conspiracy theories about Wikipedia. And you can read more about their romance in the other sources. The Slate article discusses her use of antisemitic sources in her books.
And people just ignore a number of very convincing anecdotes told to Lanzmann from Benjamin Murmelstein, someone who would know, including one with Eichmann personally helping trash the inside of a Vienna synagogue on Kristallnacht.
It's both Claude 4 Opus and the secret sauce that Claude Code has for UX (as well as Claude.md files for project/system rules and context) that is the killer I think. The describe, build, test cycle is very tight and produces consistently high quality results.
Aider feels a little clunky in comparison, which is understandable for a free product.
I think it’s also very nice that CC uses fancy search and replace for it’s edit actions. No waiting hours for the editor to scan over a completely regenerated file.
I recall watching a video on YouTube from the creator Paolo in Tokyo, and he mentioned that bread is now more popular than rice as a breakfast staple in Japan. Not sure how true it is though.
I live in Japan, and have lived here for the last 25 years. Yes, bread is far more popular for breakfast than rice is. If you go to a Japanese-style Inn, they will serve rice and fish and miso for a "traditional" breakfast, but at home, many people eat toast. There's been an increase in jams and spreads to put on toast, as well. My family here in Japan (I'm American, wife is Japanese, kids are both), we've always eaten bread and yogurt with milk nearly every single day.
PS -- We nearly always have rice with lunch and dinner, though. Japanese-grown. IMHO, it tastes very different from imported rice, and we HAVE tried.
I have never once trusted xcode to get provisioning profiles and certificates right.
It's always manual for me, at least that way xcode won't suddenly tell my app is not registered to a team and refuse to build.
I know it's not relevant to the discussion, but I want to voice publicly how much I loathe the build error system in XCode. How can they possibly think anyone will find their obtuse and downright impossible log system is helpful.
It simply forgets code exists during a port. It will port part of a function and ignore the rest, it will scan a whole file into context and then forget that a different codepath exists.
I would never rely on it for a 1:1 mapping of large features/code transformations. Small stuff sure, but beyond say a few large files it will miss things and you will be scratching your head for why it's not working.