hunspell VS spylls

Hunspell seems popular as well. I believe it's the one used by Firefox and LibreOffice, and I think it's the system spell checker in MacOS already? 🤷‍♂️

Almost all browsers use the Hunspell library for spell checking. You should investigate what methods it uses for stemming and suggesting corrections. How does that algorithm work for non-English languages? The main variation you will see between browsers in spelling suggestions is the base dictionary that is used.

I don't think so. Looking at the Chromium source it appears to use Hunspell. This is an okay spell checker, but not AI based AFAIK, only "Morphological analysis, stemming and generation".

Are you familiar with Hunspell? Dictionaries are comprehensive enough to be part of different Office Suites, so I don't see them as constricted to autocorrect.

If you're using Linux or MacOS, you should try hunspell.

i prefer and use hunspell

One can implement Huntspell which is what all browsers use (for example when typing in text areas). Is very simple and is C++.

In my experience of working on complicated algorithmic project (spylls spellchecker) in Python after 15+ years of Ruby, I really liked the gradual typing experience: you write dynamic code to get a grip of the logic, and then start to add typing here and there - and it does help to clarify design, catch accidental null possibility, and in general make inter-module API more visible.

Currently, Spylls has ≈1.5k lines of library code in 14 files. It conforms (with some reservations) to all Hunspell's integrational tests. Those tests look like a set of files each, consisting of "test dictionary + what words should be considered good, what words should be considered bad, what should be suggested instead of the bad words", and there are 127 of such sets to pass. There are 2 thousand comment lines in the code, explaining thoroughly every detail of the algorithm and rendered at the Spylls documentation site; note that besides docstrings at the beginning of each class and method, there are also inline comments in code—that's why the documentation site uses custom theme with inline "Show code" feature.