![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
TODO: Software
Dec. 18th, 2014 09:02 pmMy personal project & open source journey has been longish and somewhat varied. I'm going to be trying to bring it to a point and either tie off or continue development with one major project.
Rust
- Rust log-piper to postgres for my rpis
- Finish Rust WAV parser - maybe?
Haskell
- Card Catalog in Haskell - I need to understand how to make a CRUD app in Haskell.
Common Lisp
- a config file parser, rev to to the latest edition of the config file
- finish up some more generic support packages that will help the CL community.
- continue working on my BI database system (it's a fun & hard algorithmic challenge)
Of all those, I want to only be developing the Common Lisp BI system by July. My prior open-source (Quicklisp) Lisp work will be maintained with bugfixes, but I don't plan to do future feature on them. The BI work is interesting and encompasses a large segment of computer science, from compilers to algorithms.
Looking forward, I've roughly picked Scala as my "future" language, for future for-pay work, along with trying to learn it & the Play Framework in such a fashion that I can quickly gin up side projects/bootstrap income with Scala/Play. I've basically had it with dynamic languages: the system in Common Lisp is a disaster if there aren't lots of automated tests. Same for Python, Perl, etc. This isn't a big deal if you're doing it every day, but for the long-running projects, it's murder to pick something up after 3 months and understand what's going on.
Scala seems okay, I guess. It's statically typed and has a big commercial end of things. Which is cool. I'd rather use Haskell, but Scala clearly has the better financing and industrial tooling around it. Same for Rust, but I'm also not 100% sure Rust jobs will exist when I next look for work (hopefully quite a ways off!).
Rust
- Rust log-piper to postgres for my rpis
- Finish Rust WAV parser - maybe?
Haskell
- Card Catalog in Haskell - I need to understand how to make a CRUD app in Haskell.
Common Lisp
- a config file parser, rev to to the latest edition of the config file
- finish up some more generic support packages that will help the CL community.
- continue working on my BI database system (it's a fun & hard algorithmic challenge)
Of all those, I want to only be developing the Common Lisp BI system by July. My prior open-source (Quicklisp) Lisp work will be maintained with bugfixes, but I don't plan to do future feature on them. The BI work is interesting and encompasses a large segment of computer science, from compilers to algorithms.
Looking forward, I've roughly picked Scala as my "future" language, for future for-pay work, along with trying to learn it & the Play Framework in such a fashion that I can quickly gin up side projects/bootstrap income with Scala/Play. I've basically had it with dynamic languages: the system in Common Lisp is a disaster if there aren't lots of automated tests. Same for Python, Perl, etc. This isn't a big deal if you're doing it every day, but for the long-running projects, it's murder to pick something up after 3 months and understand what's going on.
Scala seems okay, I guess. It's statically typed and has a big commercial end of things. Which is cool. I'd rather use Haskell, but Scala clearly has the better financing and industrial tooling around it. Same for Rust, but I'm also not 100% sure Rust jobs will exist when I next look for work (hopefully quite a ways off!).
