News for hackers. Stuff that matters.
Re:R Passes SAS in Scholarly Use by hadley on Thursday June 09, 2016 @03:01PM (#11871522)
JSON is often a pain because it's so hierarchical and un-dataframe like. I have a few notes on working with it here: http://r4ds.had.co.nz/hierarchy.html.

`ifelse()` is a nightmare of a function but I don't think double-evaluation is ever a problem.

There are two maintained web-clients: curl (low-level) and httr (high-level). And I think rvest does everything that nokogiri does.

Re:R Passes SAS in Scholarly Use by pollitos on Thursday June 09, 2016 @07:25PM (#11873149)
Thanks for the link on JSON and your packages, great work as always. I should clarify when I said we-client, I meant websockets client to consume feed. The last time I tried, the only R package (r-websockets) just crashed my Linux box and not maintained for several years. httr doesn't do websockets, as I understand. Seems likely a fundamental way to engineer/wrangle data into R.
Re:R Passes SAS in Scholarly Use by hadley on Thursday June 09, 2016 @09:39PM (#11873731)
You can do it with httpuv, but it might a bit clunky. I think better websockets support, and better async generally, is on the roadmap for the next year.
Re:R Passes SAS in Scholarly Use by pollitos on Thursday June 09, 2016 @11:38PM (#11874137)
For httpuv, author Joe Cheng advised cannot do a websocket-client. https://stackoverflow.com/questions/28120307/how-to-interact...

Looking forward to the improvements. Appreciate all your work in the field.