Nothing would make it “help get a little closer to making it a reality” if it’s not physically possible, and there’s a very strong argument that that’s the case. If nothing else, the maximum specific tensile strength allowed by covalent bonding - which is fundamental physics that we can’t change - combined with the reality of defects in a 36,000 km cable - is far below what’s needed to build a space elevator in Earth gravity. It might be possible to build a space elevator on the Moon or even (in the far future) on Mars, because their gravity is such that real materials could potentially do the job. But doing that involves bootstrapping an entire offworld industry, which is far beyond anything even the most advanced nations are capable of currently, let alone a technologically stunted oil state.

There’s no chance they’d actually succeed in building a space elevator. The Line is at least theoretically physically possible with current technology, even if it was always an obviously spectacularly bad idea. A space elevator is not.

https://en.wikipedia.org/wiki/...

Always interesting to see the fascist take. Oh wait... no it's not.

I agree. Questions like this often seem to come from people who don’t *want* to use AI, or perhaps are afraid of it for whatever reason, and they’re looking for reasons that they shouldn’t use it.

It was Andrej Karpathy, one of the world’s top AI engineers.

Description of the term: https://x.com/karpathy/status/...

About him: https://en.wikipedia.org/wiki/...

I’ve stopped arguing with people about it (mostly haha) for this reason. They’re either going to have to figure it soon enough without our help, or as you say be left behind.

This matches how I use it. I’ll add a few other points:

4. Writing the first core version of a service or UI. I’ll typically use close to 100% of those generated lines, and then continue building with LLM assistance where it makes sense. It makes a big difference to development velocity.
5. Finding bugs. If some bug isn’t obvious to me, provide the code to an LLM and describe the problem. Its success rate is high.
6. Working with tech I’m not particularly familiar with (an extension of your #3, i.e. learning)
7. Writing documentation.
8. Reverse engineering existing code, i.e. describe some code to me so I don’t have to dig through it in detail.
9. Writing unit tests.

What do you object to, her support for equality or her opposition to genocide? Or is it that a woman stated an opinion?

So, the functional equivalent of reasoning?

Are you saying that ChatGPT, Claude, Deepseek etc. “make heavy use of external tools” to write code? Because they all write pretty good code, up to a certain size of program. Certainly far better than the average human, who can’t code at all; or the average software developer, who isn’t really very good.

I also strongly prefer ASCII emoticons. The graphic ones aren't consistent across platforms, and often aren't readable enough on phone screens (even not counting that texting them from Android to iPhone or back tends to replace them with different ones with a similar theme or else ??'s.)

I always use a VPN when looking at the sky.

the NSA (in their role of protecting the nation's data infrastructure, not their role of spying on everyone -- two very different organizations within the NSA)

Or so the NSA would have you believe...

Cisco Advanced Malware Protection is their "hash transmitted/received files, compare with hashes of known malware" which has its own uses in this sort of environment.