diff options
Diffstat (limited to 'TODOs.md')
| -rw-r--r-- | TODOs.md | 16 |
1 files changed, 13 insertions, 3 deletions
@@ -7,7 +7,7 @@ - [ ] hierarquical tree view, per branch and per commit - [ ] show notes in commit -- [ ] `tarballs/` folder, with `.tar.gz`, `.tar.gz.sha256` and `.tar.gz.sig` files +- [ ] `tarballs/` folder, with `.tar.xz` and `.tar.xz.asc` files - [ ] generate tarballs for all tags and all branches - [ ] SHA in log - [ ] `.patch` files (with `git format-patch --stdout -1 $SHA`), raw view @@ -33,12 +33,22 @@ Benchmark on (stagit): # Decisions -## TODO Perl vs C {#decision-d349b5be-3e00-4e00-a110-0eb7f402d4ab} +## DONE Perl vs C {#decision-d349b5be-3e00-4e00-a110-0eb7f402d4ab} +- DONE in 2021-05-28 - TODO in 2021-03-06 --- -FIXME +Instead of Perl vs C, it became Perl vs Rust, and I've chosen Rust. + +I choose Rust over C because it is a higher-level language than C is. +It allows me to produce binaries and libraries without extra dependencies (unlike C++'s `libstdc++`), and I can deal with memory management without reference counting (unlike Nim) or garbage collection (unlike D). + +I'm favoring Rust as a C-like tool because it allows me to write code that transcends the language barries: with C/Rust code, a `.so` library can be consumed by any programming language on any environment. +The binary application that will be the CLI could be written in any language, also, but it is done so in Rust for convenience. + +So the question of Perl vs C now is becoming applicable only on more specific scenarios: when having a `libsomething.so` isn't worth anything. +This isn't the case for this library. # Resources |