I mean, he didn't leave, but he did build the next new thing (git). It's just that it was so incredibly useful for everybody else, as well as for the other thing he already invented which was incredibly useful for everybody else.
Wonder how long it will take the American public to designate the US Govt a threat to national security, and using AI to assemble their own autonomous civilian defense robots to protect the public from the government-approved population suppression robots.
Flipside: how much RAM and storage do you need? What do you need it for?
What are you going to fill it with? Vibe code? Porn? Pirated movies? One man's treasure is another's trash I suppose.
FWIW I didn't downvote you, I don't have much use for a Rust compiler at all, let alone a toy one written in PHP.
"It's time to end this madness" - this is like trying to shut the barn doors after the horses have bolted and are on a cruise ship that's already sailed, drinking martinis by the pool.
People are having fun with a new way to code, trying things out they couldn't have ever done before. It's been just over a year since Claude code was launched, blowing the doors off all of the other coding models. Compared to the years of hype around cryptocoins and all the GPU cycles wasted on that, this is a bresh of fresh air for many people.
The costly process probably explains why they just started injecting ads in my plan where there previously weren't any.
And also explains why rather than be leveraged into a more expensive plan to help them pay for their containers, I cancelled my subscription. Not like there's more than 1% content there worth paying for these days anyway.
Im using UE5 which is arguably GUI heavier than Unity.
You can get around a lot of the GUI-heavy stuff by using C++ in preference to Blueprint, and/or developing some tools to help you decompile/recompile Blueprints.
It has a pretty cool remote control plugin you can install which can be used to simplify a lot of test cases through automation.
I have a relatively large amount of experience with UE4/UE5 and C++ though, so it's probably not for the absolute beginner or the faint of heart.
Presumably the article is more referring to turbulence at a macro scale. If the air is so turbulent that the compressor blades stall because of it, well, we have bigger problems.
100% - the number of times you will need to use a super optimized memcpy() in real life versus the benefit you can get from looking at and writing basic versions of it for different CPU's is very slim.
Then you'll have a much better idea of when to _really_ use one that depends on intrinsics, is optimized etc, and how to benchmark them ... those are the real skills.
Interesting, I started playing a little with Codex yesterday and it did find some bugs Claude already knew about it, and seemed pretty matter of fact about it. I might have to point it at some of the harder bugs and see how it goes.
I fired up Codex yesterday and asked it to do a security review on an UE5 project i'm working on with Claude. It found some things that Claude already knew about. But nothing made me feel confident it could _write_ UE5 C++ code as well as Claude. I guess it's worth a shot testing it on a minor feature, but what other people are saying here gels with my experience as well.
reply