I haven't used dash/s/f much, but from what I see they do try to bring a
more "flat" style of APIs, following the style of Clojure. There are a
lot of utility functions in there too (like extra abstractions on top of
the basics that the authors found to be useful). So when you ask the
core library to be more like f.el, you'll have to specify what exactly
you'd like to see changed: rename existing functions dealing with files
to start with file-* or to add new ones. Then we can work out some sort
of policy to adopt (or not) such changes.
I think the crux of the issue regarding existing Emacs lisp would be "should all file related apis start with file- ?"
If we decide the answer is yes (as advised by the coding conventions) we could start by simply aliasing the existing API that does not follow this convention. That'd mean `copy-alist` would be aliased as `alist-copy`, do you think people would be strongly against this?
I think I was not clear enough:
- I propose to alias (not rename) existing functions dealing with files to start with file-
- I propose to extend this to most emacs topics (except maybe the "touchy" ones)
- I propose to extend some of these topics with functions that looks like good additions
For example s.el contains a lot of IMHO obvious functions that emacs could include easily under a proper namespace that would probably not offend anyone.
Philippe