I mean, this is what the GPL and (to a lesser extent) the LGPL encourage. For-profit companies will look on the viral nature of those licenses in horror, and try to distance themselves from anything that uses them.
Nano is GPL, Pico is Apache-2.0. Apple are going to choose pico given how similar the editors are, there's no real downside to going with Pico.
As a vi-guy, who's even edited files used cat, tail, head and ed in extremis on a DECstation when Ultrix crashed and wouldn't boot, I admit that I don't really care either way :)
> Apple are going to choose pico given how similar the editors are, there's no real downside to going with Pico.
This comment has me seething, so I should probably stop before I say something that I'll regret. But I want you to know that this couldn't be more wrong.
Nano is GPL, Pico is Apache-2.0. Apple are going to choose pico given how similar the editors are, there's no real downside to going with Pico.
As a vi-guy, who's even edited files used cat, tail, head and ed in extremis on a DECstation when Ultrix crashed and wouldn't boot, I admit that I don't really care either way :)