See also Children of my Hometown.
Ok, Fish shell is great: fewer config files–all in a centralized location, btw–, clean syntax. And it works right out of the box without any plugin! Once I figured out how to setup the
$PATH variable, I knew I will probably not look back.
There is now a JS api for Vega-Lite, and it looks quite awesome (i.e., compared to writing raw JSON specs).
How many of you are still using or even knowing the APL language? I remember that Jan de Leeuw played a bit with R to resurrect it at the REPL several years ago, and that Nick Cox used to use J in addition to Stata. Never used any of those two languages, but the APL book contains a lot of useful information on designing PL.
TIL about a lot if useful Lisp stuff on Paul Khuong’s old website: contents listed here.
Reading another of the excellent blog post by Alex Harsányi, More Timezone Lookup (loading and saving data), I thought it would be good if there were something like a “data.table” module available in Racket.
If you’re interested in design of experiments and analysis of variance, this textbook is the latest available online I am aware of.
Doom Emacs tweaks: Org Journal and Super Agenda. Nice post on BSAG website, as always. I personally don’t use Org agenda, although I keep a list of TODO items and web links in separate org files. I once started to keep a daily workbook, but I stopped after a few months. Maybe I should try again.
Doing Basic Ass Shit in Haskell: Nice resources on Haskell and functional programming. Each time I promise I will learn more Haskell than one-liner at the
ghci prompt, but each time I find myself too lazy, as always.
Compared to when I first restarted this site using Hugo, the number of static files has quite significantly increased:
| EN +------------------+------+ Pages | 1548 Paginator pages | 190 Non-page files | 0 Static files | 689 Processed images | 0 Aliases | 38 Sitemaps | 1 Cleaned | 0
Hot off the kitchen (yesterady’s evening and today’s lunch):
I don’t know any borders, and in each case two or three products from different continents were mixed.
Happy meal, from some days ago.
Tonight I’ll probably end up watching the last episode of Morden i Sandhamn (Season 7). I’m not sure what I’m going to put on the list of things to look at next, but I’ll try to find something as entertaining as Swedish or Danish TV shows.
Ease of learning vs relearning, by John Cook. Nice points, as always. I have just some minor concerns with the last paragraphs where the author says that the tidyverse is great beacuse of its consistency. First, pending some minor annoyances with the naming convention of formal arguments in base R functions–and recommended packages–, which I always called R’s language idiosyncrasies, I do not find base R that much inconsistent. Second, I disagree with the idea that the tidyverse comes with that much conceptual integrity, for what I used to see. Most importantly, there are so many dedicated functions in, e.g.,
dplyr, that it goes against the principle of compositionality that we use to like in functional and scripting languages. Finally, what used to be available in a short number of packages, but especially
base, is now scattered throughout several packages (
glue, etc.), so that I have a hard time believing that newcomers could find their way as easily as they would with base R only. Anyway, that’s my 2¢, and it is nowhere a critic of Hadley Wickham’s account to the R ecosystem.
Some interesting resources on Scheme by Philip Bewig, who you may know if you happen to spend some time on Programming Praxis. There are also nice Awk scripts lurking around on his site.
I love the design of Thomas Honeyman’s website. I yet have to find some more time to read (and grasp) his blog posts.
Functional and scripting languages are more concise than procedural and object- oriented languages; C is hard to beat when it comes to raw speed on large inputs, but performance differences over inputs of moderate size are less pronounced and allow even interpreted languages to be competitive; compiled strongly-typed languages, where more defects can be caught at compile time, are less prone to runtime failures than interpreted or weakly-typed languages. — A Comparative Study of Programming Languages in Rosetta Code