Hacker News new | past | comments | ask | show | jobs | submit login

The plugin author should definitely be blamed for this. But I think that the root problem is with the `teacher` npm package. An issue[0] was also opened just 6 days ago raising doubts about using http.

[0] https://github.com/vesln/teacher/issues/4




No, the root problem is using an online service for spellchecking when every other decent editor does it locally.


The Plugin Author is a Principal PM on Visual Studio..


That makes this even more shocking. But, after seeing Microsoft's recent stance on privacy in general with things like Windows 10, maybe this is just par for the course.


This is my thinking too. The use of HTTP is bad, but the real issue is trusting a third party with large amounts of potentially very sensitive information. Especially when the service in question was designed for people checking the spelling and grammar of their blog posts, something designed to be shared anyway.


Online spell checkers are better along many axis. For example they can spell check names in the news and slang that's likely not in an offline dictionary


Why can't you just add those names and slangs to the dictionary?


Because an online service can dedicate 10TB of disk space to spell checking, while your laptop with a 512GB SSD won't like to store >100MB for the spellchecker.


If you had 100Mb of data I strongly suspect it'd return too many false positives - the likelihood of a string being in there would be too high. A spellchecker isn't very useful if it knows "Donald Trumo" is a real name.

For reference, the hunspell dictionary file used in apps like Libre Office and Firefox is about 400kb. That's effectively the whole of the English language.


Look up "bloom filter" and the computer science of spellcheck.

You are off by a factor of 1000 or more for cost of spellcheck


I think "the cloud" is making people forget how simple some common features actually are. The default assumption seems to be that it needs to be in the cloud because it's too hard to do locally.


Besides the good points made by other commenters, I'll raise you another one: want to trade space? How about cutting out some of that fat modern software comes with? Change the configuration language from XML to JSON and you'll suddenly have space for 10 spellcheckers. Cut out that pointless high-resolution banner and you'll have space for 10 more.


> Change the configuration language from XML to JSON and you'll suddenly have space for 10 spellcheckers.

Change it from JSON to YAML or canonical s-expressions and you'll have room for even more …


> spell check names in the news and slang

Very useful features for writing code.


You'll probably have more luck raising issues on an "official" Microsoft repo: https://github.com/Microsoft/vscode-spell-check/issues/33




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: