I thought Bazel was just a build system, not a package manager.
tatterdemalion
Not always. Prototyping can be valuable in many circumstances when you don't know the shape you'd like the code to take. Sometimes you need to try something before you know if it's right. I'd rather throw away prototype code written by an LLM than code I had to write the hard way.
I don't think it's very hard to understand. It reduces the up-front cost of development.
That is the point. By making smaller PRs, you inevitably end up with dependencies between them. So you'd like to stack them.
Yea if you don't explicitly give it direction on how to keep the code maintainable, it will gladly just spew shit into the same file until you have 10K LOC in it.
Maybe I'm just ignorant about this, but it feels a bit "gatekeepy" to outlaw answering questions about the law itself. Like... so I can't use an LLM to help do taxes? Or if I'm served a confusing legal document, I have to pay an expensive attorney to understand the legalese? I can't even just get a rough idea from an LLM first?
EDIT: Also I've literally had a professional accountant send me a ChatGPT conversation they had because they didn't know tax law well enough. I feel like if anything that should be outlawed. Professionals should actually have to know shit and know how to research primary sources.
No because your code is shit; you would be helping us reach singularity faster.
Where's Light Yagami when you need him?
Don't worry. I notel anyone you have this.
I'm pretty sure by "they" he meant Democrats.
Is he drunk in that interview, or does he just always sound like that?
In the case of Rust, it makes sense both as a UX win and a way to abstract certain requirements of the build system. Languages don't agree on how to do things like linking packages into a binary or versioning packages. If Rust left all of that unspecified, we'd probably have multiple competing package managers and ecosystems.