SpaCy v3.0 Nightly
11–20 of 31 posts
Re: SpaCy v3.0 Nightly
#12Re: SpaCy v3.0 Nightly
#13What the heck does that mean? What is spaCy first of all.
This just tells me they're not to be taken seriously.
Re: SpaCy v3.0 Nightly
#14I generally ignore products who's front page talks as if the person reading already knows who they are and what they do. I have no idea what this is. Clicking on the front page it says, "spaCy v3.0 is going to be a huge release! It features new transformer-based pipelines that get spaCy’s accuracy right up to the current state-of-the-art" What the heck does that mean? What is spaCy first of all. This just tells me th…
Re: SpaCy v3.0 Nightly
#15I generally ignore products who's front page talks as if the person reading already knows who they are and what they do. I have no idea what this is. Clicking on the front page it says, "spaCy v3.0 is going to be a huge release! It features new transformer-based pipelines that get spaCy’s accuracy right up to the current state-of-the-art" What the heck does that mean? What is spaCy first of all. This just tells me th…
If I click back to the actual homepage[0], it says:
spaCy is a free, open-source library for advanced Natural Language Processing (NLP) in Python. It’s designed specifically for production use and helps you build applications that process and “understand” large volumes of text. It can be used to build information extraction or natural language understanding systems, or to pre-process text for deep learning.
Re: SpaCy v3.0 Nightly
#16I’m constantly blown away at how high quality SpaCy is with such a small team. Everything: from API design, to documentation, to education, to tool ecosystem. Congrats on the (preview) release and thank you for the great software. Exciting to see SpaCy pull transformers into the mix!
High quality what? Spacy doesn't has autocompletion and it's the 21st century, only a python package can achieve such prodigy
I'm gonna go for: "spyder"
Final answer
Re: SpaCy v3.0 Nightly
#17I generally ignore products who's front page talks as if the person reading already knows who they are and what they do. I have no idea what this is. Clicking on the front page it says, "spaCy v3.0 is going to be a huge release! It features new transformer-based pipelines that get spaCy’s accuracy right up to the current state-of-the-art" What the heck does that mean? What is spaCy first of all. This just tells me th…
Industrial-Strength Natural Language Processing in Python
Followed by some decent descriptions and code examples.
Re: SpaCy v3.0 Nightly
#18This release was SO much work! Glad to finally have it out. :beer:
The big impact for users will definitely be the transformer models and config system, but I want to talk about a feature I wasn't expecting to build until a few months ago: the new workflow system, spaCy Projects. :thread:
spaCy Projects was inspired by @DVCorg , and has an easy integration for DVC users. But it's also standalone: you can write a single YML file and spaCy will get your data, trigger your processing steps, and use remote cache. It even generates readmes: https://t.co/uRcfJWZlsQ?amp=1
The requirements that spaCy Projects handles are more general than spaCy. So why put it in the library? The case against it -- simple minimalism -- is pretty clear. The case for it is a bit more subtle.
We built spaCy Projects for the design-space it opens up for the rest of the library. If we can assume a workflow system (by giving it to you!), it's much easier to let things happen in separate steps. We can embrace approaches that would otherwise be awkward.
A good example is the way we've stream-lined the training utilities. spaCy used to have this awkward class, GoldParse. That's gone now: the training annotations are represented with the Doc class, and the training data is read in from DocBin format -- which is about 100x smaller.
Why didn't we ditch GoldParse sooner? Well, there's definitely a downside to reading data from a binary format. It adds an extra conversion step. But with the projects system, that's no longer such a big deal. We now have a conventional way to describe such multi-step workflows.
I think the impact will be especially big for the ecosystem. It's extremely standard in NLP to have a bunch of steps to run to build counts, lists, models etc. Previously every spaCy Universe project had to build and describe their own conventions. Now we have a standard.