什么是string_score，String Scoring Algorithm packaged for NodeJS
- Free - MIT License
- Fast - fastest that I can find, often drastically faster… run the tests yourself
- Small - We are talking (520 Bytes)
- Portable - Works in 100% of the browsers I’ve tested on multiple platforms
- Tested - Not everyone writes tests (silly people). Testing using Qunit
- Proper - Passes jslint as well as meets the coding practices and principles of opinionated developers :-)
- Fuzzyable - Optional parameter for fuzziness (allows mismatched info to still score the string)
Check it out http://joshaven.com/string_score
npm install --save string_score require("string_score");
(results are for example only… I may change the scoring algorithm without updating examples)
"hello world".score("axl") //=> 0 "hello world".score("ow") //=> 0.35454545454545455 // Single letter match "hello world".score("e") //=>0.1090909090909091 // Single letter match plus bonuses for beginning of word and beginning of phrase "hello world".score("h") //=>0.5363636363636364 "hello world".score("he") //=>0.5727272727272728 "hello world".score("hel") //=>0.6090909090909091 "hello world".score("hell") //=>0.6454545454545455 "hello world".score("hello") //=>0.6818181818181818 /* ... */ "hello world".score("hello worl") //=>0.8636363636363635 "hello world".score("hello world") //=> 1 // Using a "1" in place of an "l" is a mismatch unless the score is fuzzy "hello world".score("hello wor1") //=>0 "hello world".score("hello wor1",0.5) //=>0.6081818181818182 (fuzzy) // Finding a match in a shorter string is more significant. 'Hello'.score('h') //=>0.52 'He'.score('h') //=>0.6249999999999999 // Same case matches better than wrong case 'Hello'.score('h') //=>0.52 'Hello'.score('H') //=>0.5800000000000001 // Acronyms are given a little more weight "Hillsdale Michigan".score("HiMi") > "Hillsdale Michigan".score("Hills") "Hillsdale Michigan".score("HiMi") < "Hillsdale Michigan".score("Hillsd")
Fully functional in the 100% of the tested browsers:
- Firefox 3 & Newer (Mac & Windows)
- Safari 4 & Newer (Mac & Windows)
- IE: 7 & Newer (Windows) **
- Chrome: 2 & Newer (Windows)
- Opera: 9.64 & Newer (Windows)
** IE 7 fails (stop running this script message) with 4000 iterations of the benchmark test. All other browsers tested survived this test, and in fact survive a larger number of iterations. The benchmark that is causing IE to choke is: 4000 iterations of 446 character string scoring a 70 character match.
string_score.js is faster and smaller and does more than any other scripts that I am aware. Tests for liquidmetal.js or quicksilver.js are included in my test suite for direct comparison.
The test: 4000 iterations of 446 character string scoring a 70-character match
- Firefox 3.6 (805ms)
- Firefox 4 (245ms)
- Chrome 9 (268ms)
- Safari 5 (259ms)
- Firefox 3.6 (1578ms)
- Firefox 4 (853ms)
- Chrome 9 (339ms)
- Safari 5 (996ms)
- Firefox 3.6 (3300ms)
- Firefox 4 (1994ms)
- Chrome 9 (2835ms)
- Safari 5 (3252ms)
- Firefox 4 (OUCH! I am not sure it heats up my laptop and asks if I want to stop the script… fuzzy_string, nice idea but it doesn’t like large strings matches.)
** Tests run with jQuery 1.5 on Mac Book Pro 2.4GHz Core 2 Duo running Snow Leopard *** quicksilver & string_score both use the same test file because they are used in the same way, LiquidMetal has to be called differently so the test file was modified to work with the LiquidMetal Syntax.
Please notify me of any ports so I can have them listed here. Please also keep track of the string score version that you have ported from. For example, in your readme include a note like: ported from version 0.2
The tests located in the tests folder rely on the files located in the tests folder.
Author Joshaven Potter
Thank you Lachie Cox and Quicksilver for inspiration.
###Contributors Contributing Members: https://github.com/joshaven/string_score/network/members
Licensed under the MIT license.