-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: should we cover JSON? #72
Comments
I think it could make a lot of sense to cover it in intermediate material, perhaps in the context of ETLing some data into structured format, not least of which because once you have JSON in your toolbox now basically every open web API is available to you. I would leave it out of novice because for it to make any sense you'd have to cover a lot of material, and because I think it's harder to teach in R than python (could be wrong). |
Completely agree with with @ljdursi, I think JSON in intermediate material would be useful to know, at the least to have some mention about. As for teaching in R vs Python, I don't really know. There are several R packages to work with JSON, but not sure how "teachable" they are. |
Maybe - intermediate. Depends a bit on personas... For basic usage both dplyr and pandas makes it really easy to read jsons without extensive knowledge of the format. I guess yaml. Will be talked about when we talk about markdown? |
As per #70, leave and focus on current content. Closing and adding "on hold" label. |
The text was updated successfully, but these errors were encountered: