spylls
Money
spylls | Money | |
---|---|---|
2 | 4 | |
270 | 2,684 | |
- | 0.3% | |
4.2 | 7.3 | |
about 1 month ago | 7 days ago | |
Python | Ruby | |
Mozilla Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
spylls
-
Why I Stopped Using Sorbet in All My Ruby Projects
In my experience of working on complicated algorithmic project (spylls spellchecker) in Python after 15+ years of Ruby, I really liked the gradual typing experience: you write dynamic code to get a grip of the logic, and then start to add typing here and there - and it does help to clarify design, catch accidental null possibility, and in general make inter-module API more visible.
-
Rebuilding the most popular spellchecker. Part 1
Currently, Spylls has ≈1.5k lines of library code in 14 files. It conforms (with some reservations) to all Hunspell's integrational tests. Those tests look like a set of files each, consisting of "test dictionary + what words should be considered good, what words should be considered bad, what should be suggested instead of the bad words", and there are 127 of such sets to pass. There are 2 thousand comment lines in the code, explaining thoroughly every detail of the algorithm and rendered at the Spylls documentation site; note that besides docstrings at the beginning of each class and method, there are also inline comments in code—that's why the documentation site uses custom theme with inline "Show code" feature.
Money
-
Keep Your Ruby Code Maintainable with Money-Rails
Many other options are available to customize this for your Ruby on Rails app. Check out the full details in the money and money-rails guides.
-
Why I Stopped Using Sorbet in All My Ruby Projects
For now I just try to use better objects, avoiding primitive datatypes in internal code (using the null object pattern or an option/maybe class can go a long way), and using gems that do the same, such as dry-rb and money.
-
[Production code] The previous dev thought it was ok to use floating point variables for money
Java has to have a modern money library by now? Ruby has one => https://github.com/RubyMoney/money
-
Currency Calculations in Ruby
Make sure to refer to the docs for more of the provided currency attributes, such as iso_code (which returns the international three-digit code of that currency) and decimal_mark (the char between the value and the fraction of the money data), among others.
What are some alternatives?
hunspell - The most popular spellchecking library.
Monetize - A library for converting various objects into `Money` objects.
JamSpell - Modern spell checking library - accurate, fast, multi-language
Plutus - A Ruby on Rails Engine which provides a double entry accounting system for your application
nspell - 📝 Hunspell compatible spell-checker
Wallet - A Ruby program to track your finances.
WeCantSpell.Hunspell - A port of Hunspell v1 for .NET and .NET Standard
Income Tax Estimation - Ruby library to calculate the income tax for any country
rbs_rails
DoubleEntry - A double-entry accounting system for Ruby applications.
angry-reviewer - Style corrector for academic writing and scientific papers at angryreviewer.com
money-rails - Integration of RubyMoney - Money with Rails