JamSpell VS languagetool

There is, for example, a curious evaluation table provided by a modern ML-based spellchecker JamSpell. According to it, JamSpell is awesome—while Hunspell is a mere 0.03% better than dummy ("fix nothing") spellchecker... Which doesn't ring true, somehow!

That's a huge topic, which I am planning to cover towards the end of the article series please like and subscribe, but in short: yes, my opinion is that spellchecking is actually a "machine learning problem in disguise", and most of existing dictionaries are more a roundabout way of storing something-not-unlike-models than analytical data.

But ML approach will raise a question of data availability. What good your "deep learning OSS spellchecker" will do if there aren't good (and open) models for it which cover as much languages as existing Hunspell dictionaries do? And what if adding a bunch of new words requires laborous model retraining? It is not unsolvable, but non-trivial.

I believe all the giants have something like this inside (I don't think spelling correction in Google search bar is handled with Hunspell, right?), but it is much harder to do as an open tool, ready to embedding into other software.

There are a notable attempts, though: JamSpell for one (https://github.com/bakwc/JamSpell), which has an open "free" models, and more precise commercial ones; source code is open (maybe also only for using "simplistic" models, haven't dug deeper).

Obviously, there are open-source spellcheckers other than Hunspell. GNU aspell (that at one point was superseded by Hunspell, but still holds its ground in English suggestion quality), to name one of the older ones; but also there are novel approaches, like SymSpell, claiming to be "1 million times faster" or ML-based JamSpell, claiming to be much more accurate.

Great tool, thanks for sharing. If you are open to suggestions, I would love to have spellcheck in it.

https://github.com/languagetool-org/languagetool

I don't know of a "global" function, but what you use depends largely on where you're doing your writing. It's possible to spellcheck markdown and html files from a terminal with aspell and to find the correct spelling of partial words with look. Some apps, like Grammarcheck can offer you close to global spellcheck. Apps like LanguageTool offer browser addons to check grammar and spelling.

Proofread for spelling, grammar, and punctuation errors (Grammarly, Hemingway Editor, LanguageTool),

Please re-read the wiki thoroughly, line-by-line, format your resume to the wiki guidelines, verify that each of your bullet points begin with a strong action verb and follow the STAR (Situation, Task, Action, and Result) or XYZ (Accomplished D as Measured by Y, by Doing Z) methods, proofread, revise, and repost your resume.

LanguageTool - I liked using Grammarly to check my writing, but it is not great for privacy considering it sends off everything you write to Grammarly servers. LanguageTool is a great open source alternative that you can run locally.

On extensions, for example, I use LanguageTool [1], which is similar to Grammarly. It could be configured with a local server, although I have a “premium” account which sends data to a 3rd party server. I trust this extension to verify my messages on HN, but I can't trust it to have access to my banking account. This is an example of a really useful extension that I'll never be able to fully trust because it has access to all websites, and it sends all that I write to another server.

In fairness, Firefox's advantage has been that Mozilla has a trustworthy manual review process for the “recommended” extensions.

[1] https://languagetool.org/