This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-31
Channels
- # beginners (9)
- # boot (38)
- # cider (7)
- # cljs-dev (181)
- # cljsrn (49)
- # clojure (136)
- # clojure-italy (44)
- # clojure-losangeles (1)
- # clojure-news (1)
- # clojure-russia (3)
- # clojure-sanfrancisco (1)
- # clojure-serbia (2)
- # clojure-spec (28)
- # clojure-uk (41)
- # clojure-ukraine (1)
- # clojurescript (103)
- # core-async (6)
- # core-logic (46)
- # cursive (5)
- # data-science (8)
- # datascript (6)
- # datomic (5)
- # emacs (35)
- # events (3)
- # jobs (2)
- # jobs-rus (2)
- # juxt (6)
- # lumo (7)
- # off-topic (101)
- # om (6)
- # onyx (6)
- # parinfer (38)
- # pedestal (5)
- # perun (1)
- # planck (4)
- # protorepl (4)
- # re-frame (62)
- # reagent (20)
- # remote-jobs (1)
- # ring-swagger (1)
- # spacemacs (16)
- # unrepl (43)
- # vim (13)
@stathissideris haven't used pandas much, we definitely don't have that much in the way of datasets atm. otoh not keen to add too much boilerplate or go too OO on this (YMMV)
I found using core.matrix.dataset fairly excruciating
for any operations having to extracts rows or columns and faff about before recreating a dataset, all quite slow
plain seqs and transducers ftw I say
I agree that idiomatic clojure is preferable, and the main advantage I can see in datasets saving some memory because you don’t have to keep repeating the keys (column names) for each row as you do with maps.
…but this either a non-issue because of laziness/streaming, and can be overcome with records
…worst case, we could write something that behaves like a clojure map but has the memory characteristics of a dataset
I guess it depends on what exactly you are doing - and how you think you need to do it. Apparently this is a case of YMMV, ¯\(ツ)/¯