HNHacker News
TopNewBestAskShowJobs

hankman86

452 karma · joined July 6, 2021

submissionscomments
hankman86··on All public GitHub code was used in training Copilot
Regular people yes, but no problem for decently funded startups.
hankman86··on All public GitHub code was used in training Copilot
And in case of Copilot, the training data isn’t a moat anyhow. Last I looked, everyone could freely access GitHub public repositories.
hankman86··on All public GitHub code was used in training Copilot
I don’t think that your premise concerning “planetary-scale AI” (and the ability to pull it off) holds up. If Google and Microsoft are so dominant and had such an insurmountable head start, why are we seeing such an enormous number of AI startups? In fact, there are countless startups busy figuring out how to make AI work for software development. I’d even argue that copilot was not that expensive to build. I very much doubt that GitHub (or Microsoft for that matter) had a huge team working on this or has spent such a vast amount on hardware resources that they’d outcompete the rest of the market by virtue of their cash reserves. Any decently funded startup should be able to finance such as effort. Especially since in this case, the training data is cheap (and legal) to access for anyone.

Where Microsoft does have an “unfair advantage” is in their marketing and sales firepower. Replicating their B2B and B2C sales channels is indeed very expensive. GitHub will be able to monetise Copilot by some upselling campaign. Then again, startups regularly manage to break into markets that are supposedly locked down by the likes of Microsoft.

hankman86··on “I wish I could have licensed the Id source code releases as BSD”
I think one of the reasons for why the GPL as once more popular than other licenses has to do with the fact that it was created for the GNU operating system, basically a collection of simple command line utilities. No one would think of using these in other ways than to run them on the command line (or in a batch file), which is explicitly excluded from the “derivative work” concept of the GPL.

Things got complicated once people put libraries under the GPL, which is when all the legal uncertainties cropped up about what constitutes derivative work.

hankman86··on “I wish I could have licensed the Id source code releases as BSD”
That’s a fair argument to make, even though my counter point would be that first and foremost the (A)GPL excludes a community of developers who need to earn a living with their work. In fact, the FSF will call this “morally tainted”. That being said, the free software purists aren’t a particularly tolerant community.

And again, I actually like and endorse copyleft in the form of the LGPL. So basically a license that can co-exist with others and doesn’t force it’s ideology on other people and their work.

hankman86··on “I wish I could have licensed the Id source code releases as BSD”
You’re basically using the AGPL like a “freemium” upselling business model. I’ve got no issues with that, it’s your property after all. Just don’t tell the world that you sign up to the FSF nonsense about software freedom.

And be prepared that this may not work out for you. The AGPL is particularly nasty and even infects across network boundaries (not tested in court though). No one with a sane state of mind will even come close to AGPL software - unless they’re a not for-profit entity.

hankman86··on “I wish I could have licensed the Id source code releases as BSD”
Actually there is. The LGPL is sort of a middle ground. It still requires you to share changes that you may make to some library. But it won’t easily infect the rest of your stack, so it’s basically the GPL with the viral bits removed.
hankman86··on “I wish I could have licensed the Id source code releases as BSD”
Let’s face it: the GPL is becoming irrelevant and is displaced by permissive licenses. Projects using the GPL are increasingly held back and are losing favour among developers. Like LLVM is a very active and innovative platform, whereas GCC is essentially stuck in its original scope.

Why? Because the world is more complicated than the FSF ideologues want it to be. Developers do not collectively or exclusively want to work for free and live a life of poverty.

Not to mention that the GPL is simply too risky and expensive to use in any commercial context. There are countless lawyers consulting organisations on how to avoid the viral aspects of GPL-licensed code. And since case law is scarce, more often than not the advice will be: avoid the (A)GPL like the plague.

The only meaningful and morally acceptable “copyleft” license is the LGPL, which asks you to give back without being the license cancer that is the (A)GPL.

← PreviousPage 7 of 7