This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-26
Channels
- # aws (1)
- # beginners (50)
- # boot (32)
- # chestnut (2)
- # cider (14)
- # clara (23)
- # cljs-dev (131)
- # cljsrn (44)
- # clojure (133)
- # clojure-belgium (3)
- # clojure-denmark (4)
- # clojure-dev (6)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-russia (95)
- # clojure-spec (59)
- # clojure-uk (14)
- # clojurescript (157)
- # cursive (26)
- # data-science (1)
- # datomic (160)
- # devops (5)
- # dirac (80)
- # emacs (2)
- # graphql (2)
- # jobs (2)
- # lein-figwheel (1)
- # lumo (9)
- # off-topic (151)
- # onyx (2)
- # parinfer (2)
- # pedestal (5)
- # perun (2)
- # re-frame (60)
- # reagent (3)
- # remote-jobs (1)
- # test-check (3)
- # uncomplicate (11)
- # yada (1)
@dnolen there is an issue with my patch from CLJS-1886 (already merged), here https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/core.cljs#L5559, it should be (implements? APersistentVector v), otherwise the iterator optimization for subvecs is never used
not sure if this is relevant, I was just compiling dirac tests against pretty recent master version (from last week) and noticed new warnings (not present in 1.9.562: https://gist.github.com/darwin/936829b27b73a91aa4dec0e9286671b8
btw the code which might be responsible for it looks quite innocent: https://github.com/nathanmarz/specter/blob/cfb191e1cd4be66b09d8e4f671a4890372a32cef/src/clj/com/rpl/specter/impl.cljc#L425
or maybe there are more places where they could produce such code: https://github.com/nathanmarz/specter/blob/cfb191e1cd4be66b09d8e4f671a4890372a32cef/src/clj/com/rpl/specter/impl.cljc#L688-L698 don’t have time to further investigate it
there’s already a minor ticket open for this issue which mentions naming a field default
I’m probably going to close the ticket because I’m starting to believe the expectation is not reasonable
@U060FKQPN the issue is interop w/ external JS stuff
well, I could imagine that generating [“default”] for accessing them would fix the warning and didn’t break anything
also closure compiler pass will rewrite them back to .default if they are not reserved or don’t contain wild chars
I have a post ready to go covering the new :protocol-impl-recur-with-target
warning. (Thinking it might help reduce confusion for those who encounter it.)
@dnolen @mfikes I wonder if it would be valuable for the ClojureScript website to have its own blog where we’d post release announcements & cover these new features / changes
I could probably dedicate some time to writing a post from time to time
I suppose David’s release email has been acting like a changelog. But, yeah, this release has lots of good stuff warranting coverage. 🙂
@anmonteiro Are you thinking of maybe something like http://elm-lang.org/blog ?
yeah, most Facebook OSS projects also have a blog, e.g. React, React Native, Flow, Jest
case in point: https://facebook.github.io/react/blog/
I bet the community would find that kind of stuff useful. I’d be willing to write for such a thing as well.
I find that a lot of people read my blog (probably yours too, but I don’t have those metrics) whenever we post about ClojureScript
@alexmiller thoughts? Clojure doesn’t really have it’s own blog outside of the Cognitect one
I’m just advocating for an official “source of truth” 🙂
I’ve taken to copying any news-ish stuff over to the clojure site
same could be done for cljs
I’d be happy to do the magic later today if wanted
anyone could PR an addition to that
sounds great 👍
@alexmiller you mean add a new tab right?
I have also been putting changlog release stuff at https://clojure.org/community/devchangelog
@dnolen well, could be put in a couple places
@alexmiller I just mean only you have the power to add the news
tab we need right?
could be top nav
I can just replicate what’s on clojure site
we reduced top nav menu items on cljs site as the left image is longer (due to “Script”)
but seems like there is room
Here is the content of the post I have queued. I could see perhaps smaller versions, lacking typical post images, and perhaps using a less personal tone, on an official ClojureScript blog, where such posts delve into new features as contributors find time to write such posts. https://gist.github.com/mfikes/41cc3911e8f2c15ec005df7ed256ec33
@mfikes I think for releases probably the thing to call out is the big story if there is one
in this case I would say compile/runtime performance and cache safe spec are probably the things worth talking about
^:const
subtleties and recur
alignment is interesting but probably a bit too esoteric for most users
Exactly. The length of the post I’ve drafted above goes into too much detail for a general official ClojureScript blog.
@anmonteiro @mfikes if either of you feel like drafting something for the release be my guest 🙂
https://clojurescript.org/news/news -> David Nolen
Is that set up for PRs? (Otherwise I’ll just draft up a few paragraphs about the upcoming release for review.)
re prs, yes
@anmonteiro this is kind of a weird artifact of how the templates are set up. the news index page shows the content of the most recent post but the author of the index page itself
I remember messing with this on the clojure site too, let me see if I can fix
not a big deal, but I thought I’d mention anyway
@anmonteiro should be fixed in a few minutes
Draft. Of course feel free to heavily edit: https://github.com/clojure/clojurescript-site/pull/90
will news contain release posts, like those on the mailing list?
i asked @alexmiller earlier if it would make sense to show release posts like this: http://cljs.github.io/news
Up to y'all
@mfikes Here is a few concrete stuff that I think can be interesting/useful to users:
- sort, shuffle is now 30-40% faster (thanks to to-array optimization)
- apply is 200-400% faster
- You can use js/Promise and many more ES featurs and have GCC generate polyfills (new :rewrite-polyfills option)
- defmulti is now much faster in case of a "miss" (200-1000%)
- set and map equivalence is 100-200% faster
- reduce on sets and maps is now ~100% faster
New:
- new language options ES-2017, ES-next
^ this is so good, I know all the fixes by looking at it but couldn’t have remembered all of them together
I feel like this may be easier to collaborate https://oasis.sandstorm.io/shared/PrJgZNOzy7954FKVSC06E2LTkES0j-SEsHsS1o9QvZg
@shaunlebron I think it’s probably simpler to just copy and paste w/ minor edits whatever @mfikes comes up with for the release post
afaik a lot of people are reading news letters these days, do we need one exclusively for ClojureScript?
loving the movement on news here 👍 site definitely needs something for it
@roman01la but not having news on an official site seems weird yeah?
@shaunlebron having a blog is great, newsletter could be a nice addition to that
It could have links to other blog posts on the web as well as learning materials references and promos for trainings or something
That's basically React's newsletter
@shaunlebron I'm not saying cljs should not have a blog :)
so a newsletter would just be a blog that covers community activity rather than only compiler development?
I would like to see that too 👍
I think I could take care of this, I'm reading all those resources every week anyway. Could just put them together
a newsletter sounds like something that the community should do to me
yes newsletter is an interesting idea but I don’t think we need to be directly involved
All I'm saying is that it would probably have more reach if people know its kind of "official" newsletter
that seems to fit the purpose of the site, if it was updated as a separate newsletter page
or news vs community news
@mfikes might not be able to review until later, so looking more like a morning release at this point
@dnolen docstring ticket adding fn-invoke-direct
to cljs.js
‘s API https://dev.clojure.org/jira/browse/CLJS-2130