colinmarc
Here's a random example from the Skyrim EULA:
[You may] use one copy of the Software for your personal, non-commercial use on a single home or portable console or computer.
...
[You agree not to] use or install the Software (or permit others to do same) on a network, for on-line use
...
Installation on a network server is strictly prohibited, and this Agreement shall not serve as a network license in any manner.It's a bit of a grey area, and it's not true that Nvidia needs to have a licensing deal. It's definitely against the license terms you get when you purchase a game through steam to run it on arbitrary hardware, but most (at least EU) courts would probably hold that if you own a game, you can run it on any hardware you have access to.
What happened was that when Nvidia just got started, they had an opt-out framework (for developers) instead of opt-in. At the time, some game developers felt like Nvidia was profiting off of their work unfairly, and posted publicly about it, and there was a decent-sized backlash.
However, in the meantime, other competing streaming platforms have gone with opt-out and there hasn't been much of an issue around it. I think most developers have come around to the idea that it increases game sales.
At $work we've been refreshing the Bun release page for days, wondering when they would push the fix. The PR with the change merged over 72 hours ago: https://github.com/oven-sh/bun/commit/ea6a2c7b7c98862627760d...
I'm not a security expert, but package managers seem uniquely vulnerable to MITM attacks.
I don't really see the point of spending $MM in tokens to create a software factory if you can't push security releases out in a timely fashion.
- Today, a lot of functionality still in Docker has been upstreamed into the (Linux) kernel, so containers can be much simpler (and rootless). Docker is still carrying around some of that cruft, which is what makes it slower and heavier than Podman.
- As a devex technology, Docker/containers have been massively successful, but not as infrastructure. Containers never became secure enough to run multitenant workloads without some other form of isolation, so they ended up being redundant with KVM (or gVisor, or a similar second layer) in production a lot of the time.
That second contradiction led to lots of inefficiency. For example, on Google App Engine, for years when you ran a deploy it would create a VM just to run a single container.
The very urgent uv/certifi/etc releases (and yet-to-be-done bun release) are about removing the compromised CAs as described here:
https://emudhra.we-have-a-problem.com/
In other words, that software bundled the compromised certs into the binary, so upgrading it is the only way to remove them.
This is about Go proactively blocking intermediates. Which shouldn't strictly be necessary as long as your OS has removed or distrusted the CAs (on my laptop, macOS has done that, although it seems like it did so in a way not all tools have access to; for example, rustls-platform-verifier respects it, but rustls-webpki still loads the bad CAs from the system trust store).
edit: forgot I can't use code blocks on HN
DevEx for developers who don't write code
GitHub Actions Feedback Survey
My point is more about up-front investment paying dividends. To speculate, it seems like the reward hacking is not there for long-term thinking.
Interface design is one of the things Claude is worst at in my experience (using it every day for the past year).
All software is broken, but LLMs seem to make the wrong compromises consistently when working in large codebases.
https://x.com/FlorianKluge/status/2041855675295318039
(Whether that's against the ToS is not clear.)
If you're unfamiliar, it's like tab-completion, but it has a context that includes the edits you've made in the last few seconds, and it can predict around the cursor.
The model isn't advanced enough to understand complex tasks, but it has more the feel of the "crafting gun" in Subnautica or other survival crafting games, if that analogy makes any sense.
Personally I hate working with a chatbot - it's low-bandwidth and rage-inducing. If I could imagine a perfect workflow, it would be something like me whispering my train of thought as I program, and then pointing a very fancy "autocomplete gun" at the code.
I agree with your premise, but you're still viewing this technology through the lens of "a successful product" versus "a successful piece of technology".
Plenty of open source projects stay open source and are popular without ever making any sales whatsoever. I'm not trying to project my own motivations on the Iroh team; they may want to build a product out of it. For me, though, the project has a lot of appeal already, because it exactly and excellently fulfills a technological need, not because they brought me in with a "it's x but for y" narrative.
I don't understand why HN seems so concerned about nailing down its "value proposition".