Live data from Hacker News

A spellchecker used to be a major feat of software engineering (2008)

prog21.dadgum.com

11–20 of 210 posts

Re: A spellchecker used to be a major feat of software engineering (2008)

#11

I'd have liked more explanation of the actual solutions that programmers used at the time.

For the basic word list, possibly tries (https://en.wikipedia.org/wiki/Trie), DAGs (https://en.wikipedia.org/wiki/Directed_acyclic_graph#Data_co...), or Bloom filter (https://en.wikipedia.org/wiki/Bloom_filter)

Re: A spellchecker used to be a major feat of software engineering (2008)

#15
post #7

Given that spellcheckers are mostly stable tech, I wonder why Google’s spellchecker in Gmail, or even in Chrome in “enhanced” mode, is so bad. Even Microsoft Word, being a local app and everything, manages to work better than Google’s cloud-based offerings. That’s surely evidence that progress is far from being linear.

There have been some very specific issues I and others have noticed that lead me to believe the backend for Google’s cloud based spellchecker has changed from a traditional language model to some more generalized LLM-based system. It’s gotten distinctly more terrible a couple of times in the last few years.

Re: A spellchecker used to be a major feat of software engineering (2008)

#16
post #11

I'd have liked more explanation of the actual solutions that programmers used at the time.

For the basic word list, possibly tries ( https://en.wikipedia.org/wiki/Trie ), DAGs ( https://en.wikipedia.org/wiki/Directed_acyclic_graph#Data_co... ), or Bloom filter ( https://en.wikipedia.org/wiki/Bloom_filter )

according to https://en.wikipedia.org/wiki/Ispell ispell (1971) already used Levenshtein Distance (although from the article it is not stated if this already existed in the original version, or if it was added in later years).

Re: A spellchecker used to be a major feat of software engineering (2008)

#18
It is 2025 and the best spell checker is a search engine. Numerous time an application will not provide the correct word. Only solution is to try the word in a search engine and try using in a sentence if that fails.

In my opinion, this is where ML/AL local model, no internet required, would be the most beneficial today.

Even had to use a search engine with, "thoughts and opi" because I forgot how to spell opinion before posting this. In application spell checker was 100% useless with assisting me.

Re: A spellchecker used to be a major feat of software engineering (2008)

#19
Is there a reason why Apple's iPhone spellcheck is often really poor, significantly worse than both LLMs and just...human eyes?

I often find myself butchering the spelling of a word in a way where the correct answer is obvious to human eyes (probably because of "typoglycemia" [1]) and an AI LLM immediately understands what I meant to say, but Apple's spellcheck has "No Guesses Found."

Does anyone else have this experience?

1. https://www.dictionary.com/e/typoglycemia/

Re: A spellchecker used to be a major feat of software engineering (2008)

#20
One wild thing about the AI era is that tasks which once required specialized NLP expertise—rhyming/meter detection, grammar correction, sentiment analysis—can now be done by weak LLMs. Same APIs, different prompts. I’m surprised more people aren’t exploiting this.
Post reply on HN