Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
zverok
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
Presentation on APL Style and approach to coding (2017)
(sway.office.com)
1 points
by
zverok
6y ago
|
0 comments
32.
▲
The Second Wave of Instagram Poetry Is Here
(bustle.com)
1 points
by
zverok
6y ago
|
0 comments
33.
▲
Rebuilding the spellchecker, pt.4: Introduction to suggest algorithm
(zverok.github.io)
5 points
by
zverok
6y ago
|
0 comments
34.
▲
by
zverok
6y ago
That's a huge topic, which I am planning to cover towards the end of the article series <s>please like and subscribe</s>, but in short: yes, my opinion is that spellchecking is actually a "machine learning problem
35.
▲
by
zverok
6y ago
I believe that LanguageTool[0] is the closest open-source counterpart to Grammarly. Though, in my experience, it is not a half as useful... But multilinugal and open-source. I have a distant dream of doing to it what I did to Hunspell (writ
36.
▲
by
zverok
6y ago
Ah, indeed :) I just googled the first one for "symspell+js"
37.
▲
by
zverok
6y ago
> I wish there was a similar project written in Ruby. Hehe... Actually, Ruby is my primary language, but I have chosen Python for this project for a complicated set of reasons I tried to explain[0] in the first article. > If I recall
38.
▲
by
zverok
6y ago
Thanks!
39.
▲
by
zverok
6y ago
For what I know (I've mentioned it in the first part[0]), the nspell[1] is the most close to "port (some) of Hunspell", and typo.js[2] ports even less (but might be enough for some, we used it in my previous company: it uses
40.
▲
Rebuilding the spellchecker
(zverok.github.io)
151 points
by
zverok
6y ago
|
24 comments
41.
▲
Rebuilding the spellchecker, pt.2: Just look in the dictionary, they said
(zverok.github.io)
9 points
by
zverok
6y ago
|
0 comments
42.
▲
Rebuilding the most popular spellchecker. Part 1 (Groking Hunspell)
(zverok.github.io)
13 points
by
zverok
6y ago
|
1 comments
43.
▲
by
zverok
6y ago
(not the OP here, but the author of the linked reference) The value of the link, as opposed to previous discussions, is not "Ruby 3.0 is out", but the very structured list of changes, provided with reasoning behind the change, exa
44.
▲
by
zverok
6y ago
(author here) I noticed the thing about flatten an hour ago and fixed it (somehow thought +/, is "reduce 2 times", then understood it is flatten + reduce, and my lib already had flatten, so it was easy to fix). As for "i