> Atmospheric entry (if that's what you mean) is irrelevant.
I think the OP meant that Earths magnetic field and atmosphere shields any terrestrial matter far more than than a bare asteroid that has no such protections, so it seems implausible at first glance that these things would develop or survive in open space rather than here.
Specifications are smaller than the full code, just as high level code is smaller than the functionally equivalent assembly. As we ascend the abstraction ladder the amount of reading a human needs to do decreases. I don't think this should really count as "back to square 1".
That has always been the perceived promise of higher-abstraction software specs: automated code generation from something higher-level, thus making programmers increasingly obsolete.
Among the RADs is Microsoft Visual Basic, which along with WinForms and SQL was supposed to make business programmers nearly obsolete, but instead became a new onramp into programming.
In particular, I'd like to highlight UML, which was supposed to mostly obsolete programming through auto-generated code from object-oriented class diagrams.[1] The promise was that "business domain experts" could model their domain via visual UML tooling, and the codegen would handle it from there. In practice, UML-built applications became maintenance nightmares.
In every one of these examples, the artifact that people made "instead of programming" became the de-facto programming language, needing to be maintained over time, abstracted, updated, consumed behind APIs, etc. -- and programmers had to be called in to manage the mess.
It's interesting that Spec4 can be auto-generated, then used to generate code. My question is - what do you do when you have (a) consumers depending on a stable API, and (b) requests for new features? Maybe hand the job to Claude Code or a human developer with a suite of unit tests to guarantee API compatibility, but at that point we're back to an agent (LLM or human) doing the work of programming, with the Spec4 code as the programming language being updated and maintained.
A single DGX Spark can service a whole department of mathematicians (or programmers), and you can cluster up to 4 of them them to fit very large models like GLM-5 and quants of Kimi K2.5. This is nearing frontier-level model size.
I understand the value proposition of the frontier cloud models, but we're not as far off from self-hosting as you think, and it's becoming more viable for domain-specific models.
Does a warrant ever expire? How long can they monitor you once the warrant is issued? Do they ever have to notify you or anyone else that you were being monitored and they found no criminal conduct? Don't you see the potential for abuse here?
All of these questions, and more, are answered by examining what happens with phone taps. Phone taps, which historically were treated precisely the same, and further, there was only ever one phone company in a region back then.
All legislative change is interpreted by courts. So to answer your questions:
# look to see how the legislation is written for phone taps
# know that this new legislation is changing things, the code is being modified
# now look at judicial decisions, and you will have your answer
Seeing as you have no idea how other warrants work, when they expire, you're really just looking for the worst case scenario, without even attempting to see what would happen, and has happened for 100+ years.
Of course vibe coding is going to be a headache if you have very particular aesthetic constraints around both the code and UX, and you aren't capable of clearly and explicitly explaining those constraints (which is often hard to do for aesthetics).
There are some good points here to improve harnesses around development and deployment though, like a deployment agent should ask if there is an existing S3 bucket instead of assuming it has to set everything up. Deployment these days is unnecessarily complicated in general, IMO.
> They'll be thinking "Of all possible things we could talk about, why this??"
Sure, but the point is that they should just say that, and the person who raised the issue must then explain why it's worth their time. Maybe there's an important point they're trying to make, maybe not.
you can put He in a closed loop system and still use it for cooling, by using it as the thermodynamic working fluid, and then selecting any other fluid as the heat carrier?
That's not clear actually. It's been awhile since I watched the video on the ASML EUV system for etching wafers, but from my recollection, the UV light ablates away layers of wafers and so particles of silicon presumably contaminate the noble gas that's flowing over it. I don't think a closed loop is possible in the existing setups.
High thermal conductivity, inertness, and low absorption of the EUV wavelength used are the primary characteristics needed, and purity is needed to eliminate contamination of numerous ultrasensitive stages. AI summarized it as follows:
EUV tools require ultra‑high‑purity helium, typically grade 9N (99.9999999%) or better, with strict ppb‑level limits on: Nitrogen, Oxygen, Moisture, Hydrocarbons, Refractory compounds, Particulates.
How helium is used:
- Cooling the EUV plasma source
- Purging and protecting optics
- Maintaining inert, ultra‑clean environments
- Leak detection
I think the OP meant that Earths magnetic field and atmosphere shields any terrestrial matter far more than than a bare asteroid that has no such protections, so it seems implausible at first glance that these things would develop or survive in open space rather than here.
reply