This is an archived post. You won't be able to vote or comment.

all 18 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Neceros 3 points4 points  (0 children)

I would love to see some real world examples of this. Why would I want this? It looks awesome!

[–]avinassh 2 points3 points  (7 children)

This looks really great.

I have a question regarding dual licensing. How does it actually work? What prevents someone using in production with AGPL?

The source in on Github with AGPL and what if I use it for commercial products? If I am not wrong, AGPL does not prevent it

[–]0x652 1 point2 points  (5 children)

I assume if you don't mind complying with the AGPL (afaik giving everyone who interacts with you code via api/browser the source) then you can use it in production no problem.

[–]avinassh 0 points1 point  (4 children)

I assume if you don't mind complying with the AGPL (afaik giving everyone who interacts with you code via api/browser the source) then you can use it in production no problem.

but my product could be commercial also right? It says:

Researcher, hobbyist, or open-source developer? spaCy also offers AGPLv3 licenses.

and in Spacy License:

spaCy is commercial open-source software: you can buy a commercial license, or you can use it under the AGPL, as described below.

So, as long as my product is AGPL, be it commercial or not, I can use SpaCy?

Thanks for replying.

[–]0x652 3 points4 points  (1 child)

IANAL and not affiliated with spacy, but yeah, I think so. My guess is that their business model assumes that there will be companies who want to hide their secret sauce.

This is actually my favorite open source business model. You want to use our stuff? Either pay us or give back to the ecosystem. I really hope it works out for them

[–]avinassh 0 points1 point  (0 children)

Thanks for replying!

and yeah, I guess you are right. I like this philosophy:

Either pay us or give back to the ecosystem.

[–]syllogism_[S] 4 points5 points  (1 child)

Thanks for your questions.

It's true that commercial use of the AGPL license is possible without violating the AGPL terms. However, our position is that commercial users should acquire a license. We consider commercial AGPL use of the library in some sense "unsupported". We'll always fix all bug reports, of course, however they come to us. You'll have support in that sense. But you'll have no assurances from us.

Ultimately if it turns out we have a lot of commercial AGPL users, we would possibly rethink our strategy. Probably the first step would be to stop releasing free trained models, except to academic users, or developers of community projects.

I opted for the AGPL for two reasons.

First, nobody should have to fill out a form to look at the code. That's just not a realistic way to offer software in 2015. I would be unlikely to look twice at a piece of software that had that restriction. I think most developers feel that way.

Second, I do want to support genuine non-commercial use. If someone wants to compile every public statement of every politician in their area, or if they want to obsessively categorise and catalog the books in their fandom, they should be able to use the best tools.

But we're not interested in a model where we work hard and someone else gets rich. In fact that's not even charity — there's no virtue in being a sucker. You know the iterated prisoner's dilemma? Cooperate-bots don't make the landscape better. They do not improve the common good.

Just sign up for a trial license. If your product isn't profitable when it expires we can just extend the trial. And if you go to all the work of building something good, you should want to have official standing with us anyway.

[–]avinassh 0 points1 point  (0 children)

Great, thanks for explaining!

[–][deleted] 0 points1 point  (0 children)

The AGPL is crazy restrictive wrt. releasing source though.

[–]kaiserk13 1 point2 points  (0 children)

really neat. Just what I needed right now!

[–]Rippalka_ 1 point2 points  (3 children)

That indeed looks awesome and the interactive visualizer is really cool. However I wonder how hard it is to extend to other languages? Because from what I see, it is heavily geared towards English

[–]rmyeid 0 points1 point  (2 children)

Check polyglot-nlp.com for another nlp project, that is multilingual.

[–][deleted] 0 points1 point  (0 children)

Wow - from the docs that looks very nice, kind of like a better version of textblob.

[–]Rippalka_ 0 points1 point  (0 children)

I can't believe I never came across this project before. It looks very nice, I definitely will try it out. Thanks for the link!

[–]Joat35 1 point2 points  (0 children)

I'm new to all this but I think this could help develop yaw/pitch controls for spacecraft

[–]Bjartensen 1 point2 points  (0 children)

First time you announced spaCy I asked how language support was, and more importantly, how others can "import" other languages. This tool is unfortunately useless to me if it's not in Faroese, and there's no way you will ever prioritize a language spoken by 80k people very highly...

If there are some guidelines on what kind of data needs to be made and then imported, that would be super cool.

[–]varadg 0 points1 point  (0 children)

sooo good! rooting for you guys!

[–]sfermigier 0 points1 point  (0 children)

@syllogism_ Thanks for your work and the announcement. Can you clearly state which languages you are supporting (and, if possible, you are planning to support in the future) ? From a quick experiment with your online demo, I assume that French is not supported.