slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

site: faq: history: cleanup

Browse Source
This commit is contained in:
Simon Michael 2016-02-18 10:09:14 -08:00
parent 8370d2ec63
commit bd84942349
1 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
site/faq.md
View File

@ -28,21 +28,23 @@ I couldn't expect John to start over - at that time he was not the Haskell fan h
So in 2007 I began experimenting. So in 2007 I began experimenting.
I built a toy parser in a few different languages, and it was easiest in Haskell. I built a toy parser in a few different languages, and it was easiest in Haskell.
I kept tinkering. Goals included: I kept tinkering. Goals included:
(a) to get better at Haskell by building something useful to me,
(b) to learn how well Haskell could work for real-world applications, - to get better at Haskell by building something useful to me,
and as increasingly time passed, - to learn how well Haskell could work for real-world applications,
(c) to provide a new implementation with a greater focus on ease of use, simpler - and eventually: to provide a new implementation focussing more on
features, absence of user-visible bugs, and high-quality documentation and web presence. ease of use, absence of user-visible bugs, and high-quality documentation and web presence.
Also to experiment with new user interfaces, APIs, etc. Also to experiment with new user interfaces, APIs, etc.
Before too long I had a tool that was useful to me. With Ledger still installed, Before too long I had a tool that was useful to me. With Ledger still installed,
and by maintaining high compatibility, I now had two tools with different strengths, and by maintaining high compatibility, I now had two tools with different strengths,
each providing a comparison for the other in case of confusion or suspected bugs, each providing a comparison for the other in case of confusion or suspected bugs,
which was itself quite valuable. which was itself quite valuable.
Later the Ledger project revived and attracted more contributors. I have Happily, the Ledger project later revived and has attracted new active contributors.
remained active in that community, sharing discoveries and design discussions, I have remained active in that community, sharing discoveries and
and happily we have seen many ideas travelling in both directions. design discussions, and we have seen many ideas travelling in both directions.
hledger shared #ledger's IRC channel until 2014, when I added
[#hledger](irc://irc.freenode.net/#hledger) to allow us more space.
I think having independent but compatible implementations has been I think having independent but compatible implementations has been
quite helpful for troubleshooting, exploring the design space, and quite helpful for troubleshooting, exploring the design space, and
@ -52,7 +54,7 @@ the [ledger-cli.org](http://ledger-cli.org) site,
[LedgerTips](http://twitter.com/LedgerTips), [LedgerTips](http://twitter.com/LedgerTips),
IRC support on #ledger, IRC support on #ledger,
and now [plaintextaccounting.org](http://plaintextaccounting.org). and now [plaintextaccounting.org](http://plaintextaccounting.org).
In 2014 I added a [#hledger](irc://irc.freenode.net/#hledger) channel to allow more hledger-specific discussion.
### Future ? ### Future ?