This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-06-10
Channels
- # admin-announcements (50)
- # beginners (4)
- # boot (31)
- # cider (25)
- # clojure (120)
- # clojure-brasil (1)
- # clojure-germany (2)
- # clojure-india (9)
- # clojure-italy (6)
- # clojure-japan (104)
- # clojure-nl (13)
- # clojure-norway (1)
- # clojure-russia (6)
- # clojure-sg (23)
- # clojure-spain (37)
- # clojure-turkiye (2)
- # clojurescript (115)
- # core-matrix (1)
- # datomic (63)
- # editors (32)
- # euroclojure (56)
- # events (6)
- # ldnclj (71)
- # off-topic (27)
- # onyx (7)
- # overtone (2)
- # reading-clojure (16)
- # reagent (5)
- # slack-help (10)
Short post about REPLs def
s and vars (CLJS-934): http://blog.fikesfarm.com/posts/2015-06-09-def-vars-in-clojurescript-repls.html
@mfikes: I guess you probably saw this already - I no longer need to pay to put my own iOS apps on my own device, hooray!
@cfleming: Yes. That should encourage more developers. Spent a month or two developing my first app in the simulator only before I convinced myself I was gonna ultimately ship it. I wonder how many potential apps died early owing to that barrier.
@mfikes: Yeah, I suspect that Apple realised that maybe raising the bar to entry wasn’t a good idea.
@cfleming: On the shipping side, the $99 often becomes silly compared to the 30% cut. But that a whole different side of the equation. Thinking of some 14-yo kid who wants to mess around developing on a spare iOS device, but doesn’t have or want to spend the money. I think its a great move on Apple’s part.
@mfikes: I wonder if it’s the first step towards opening distribution completely.
@mfikes: Right, if $99 is probably not a big deal once you’re up and running but it’s off-putting for experimentation - I think it’ll help them increase mindshare.
@mfikes: it sounds crazy but they’re 50% of the way there letting anyone build and run arbitrary code on their device
The big problem is the reviewers and the need to somehow pay for them if they open the doors. Hrm.
I suspect that this change is probably as far as they need to go to be honest. I suspect that having to pay $99 to distribute probably helps keep some of the dross out of the App Store.
It’s interesting that it opens up the possibility of distributing OSS apps via Github to anyone not afraid of building them.
I suspect the build+install step can probably be automated pretty comprehensively and made quite slick for even relatively non-technical users if anyone cares enough to do so.
@cfleming: exactly. And at that point, why not just let people sideload?
@mfikes I actually never did any iOS stuff simply because I didn't have $99 to spend on it. I think it's great that they're open sourcing it.
@mfikes: nice post!
@mfikes: little nitpick haha: the pre
tags have a slightly different grey as background color than the code
tags inside of them
@martinklepsch: Perhaps it is a Cryogen default. @maria ’s is doing the same http://mneise.github.io/posts/2015-06-08-week-2.html
@maria: I fixed my Cryogen blog code formatting colors with this in screen.css
pre {
background-color: #f0f0f0;
}
By the way Cryogen is an awesome static blog engine written in Clojure. I recommend it
I’ve seen Cryogen, and it looks pretty neat. Talking about static site generators: @podviaznikov built one as set of composable boot tasks: https://github.com/hashobject/perun
@mfikes: I was wondering if this would be something worth fixing in cryogen? I couldn’t find the responsible code at a quick glance though
@martinklepsch: yeah. I suspect my setup adheres to the default setup fairly closely. I added an extra bit to my screen.css
file.
@martinklepsch: I'll log a ticket against Cryogen.
@martinklepsch: Perhaps it is no longer relevant: https://github.com/cryogen-project/cryogen/blob/master/src/leiningen/new/cryogen/css/screen.css#L120
that would explain why I didn’t see a cause for two different colors (https://github.com/cryogen-project/cryogen/commit/308132bef66842928839f17521387f20f98d3e7e)
TL;DR for those interested in Cryogen: You write 2015-06-10-post-title.md files, run lein ring server
to preview locally, then tar
up public
tree and toss it on a web server.
Nice, thanks for the summary, that's useful.
…for people like me who are too lazy to click on the Github link, anyway.
static sites are the best
actually also as a deployment “frame” for cljs apps
@cfleming: the Cursive enhancements to ClojureScript are great! I think if you’re not going to actually resolve js/foo
you should not warn about it. Similarly for property access (. foo -bar)
@mfikes: thanks for letting me know about the code formatting colours, didn’t even notice that they were slightly off
anyone noticed that figwheel and the latest clojurescript don't work together - figwheel keeps waiting for a browser to connect?
@colin.yates: Seems to work well for me.
@akiva - hmmm, I did a vein clean then a lein figwheel and while the app works, hot re-loading CSS or CLJS doesn't. Oh well, knowing it works for somebody at least means I will poke around a bit more - thanks!
@colin.yates: similarly no issues here w/ "lein new figwheel" + bumping everything to latest
thanks @jackjames. It is amazing how annoying it is having gotten used to figwheel to have to manually reload the page 😉
@colin.yates: i'd rather just throw my whole project out and start over lol
heh — yes, figwheel changes the game. i gave it a quick shoutout to that effect @ http://derekslager.com/blog/posts/2015/06/five-years-of-google-closure.ashx
I started fooling with figwheel in my spare time, and now doing "real" work where I have to reload/reenter data is awful.
bhauman has a post where he builds a figwheel-esque workflow in plain old js @ http://rigsomelight.com/2015/06/09/straightforward-live-functional-javascript-building-the-yome-widget.html
yeah, so it turns out that commenting out the figwheel connect code in order to cut a deploy disables figwheel . My bad.
@nullptr: Thanks for that link. I had been just thinking today how I need to get rid of the write/reload cycle in my current JS/React project...
anyone using cljc + schema in with success?
for some daft reason, i get undefined var errors for schema’s vars
i’ve unpacked the schema jar and confirmed that the vars are where they should be. all the rest of the code in the project is fine
robert-stuttaford: i did this, but didn’t do anything advanced https://github.com/clojure/clojurescript/wiki/Dependencies#using-libraries-directly
yeah, we have an existing project using cljx. and a cljx file has all the schemas. when converted to cljc, though, it complains that it can’t find schema’s vars
with the cljx variant, though, it’s all fine
@dnolen: any thoughts on how i might debug?
next step is to switch on the verbose mode of the compiler and see what that says
I'm trying to get a sense of the download footprint for a clojurescript website. I want to use it for a pretty simple mobile website.
Anybody have any success getting a <100K footprint?
Or I guess another way to ask it is, what's the approximate minimum footprint of cljs with advanced optimizations, dead code removal, etc?
Good question…let's say no for now, just so I can get a sense.
My memory is that cljs apps benefit a lot from gzip -- lots of repeated ".call(...)"
I know his blog posts almost universally quote payload sizes, as it's something to be proud of for all that cljs provides
Oh, cool! Going to pull up his posts now.
jeff.terrell: I just gzipped an advanced mode slug with React and Om and my own stuff + browser repl... got exactly alejandro 's numbers
Hi Alejandro
OK, that's not bad…that could work.
I'm wondering how much of that is React/Om, too, which we won't need on the project we're evaluating.
Just started a clean release build on the mies
template, gonna see what those numbers look like.
Hi! I'm looking for an out of the box pretty printer for cljs. Which one do you use ? https://github.com/brandonbloom/fipp ?
Ha, good point about the dead code removal.
Yeah, if I'm reading this right, we have 105K unzipped, and 27K zipped. OK, I think this will work, fantastic.
Thanks for the help ya'll!
jprudent: https://github.com/clojure/clojurescript/commit/d0dedcb155d2c742e11d50ec79c54e5c8c4b8e73
@alejandro: Thanks, I'll upgrade my cljs. Many thanks again
@jeff.terrell: ClojureScript starts at ~20k gzipped and goes up from there.
@robert-stuttaford: don’t know enough about schema to offer any guidance
thanks @dnolen. it’s rather odd. i’ll dig and see what i can find
@dnolen: Yeah, it actually does attempt to resolve those accesses but without type info it’s tough. I’m going to have to look harder at how the JS resolution works, which is more or less the same problem.
@mfikes: re: calling functions over websockets it's a protocol between browser/server; it sends a message with a symbol identifying the var of the function to call. immediately returns a channel where the response will be put. The magic is that you can return a function or core.async channel and through the magic of serializing/deserializing edn, it gets a uuid to be referenced later
hey ericnormand! and michaelklishin!
was wondering if we’d see a clojurewerkzer in here
@mfikes: it's not very long, just took a little work to make it work reliably
hi robert!
are you doing a datomic course soon?
just an informal hangout on friday
i’ve done a questionnaire and got some good questions to talk about
at least half i don’t know the answer to, which is great
you had better get reading
are you coming to strange loop?
@mfikes: just read more context; to clarify: I'm not printing out functions and reading them back in. Printing out a tagged literal and creating a lambda from it on the other end. tagged literal just says it's a function and its uuid.
i am not 😞
Cape Town is far from everything!
@ericnormand: ahh. Makes sense :)
@robert-stuttaford: can't be more than a 24hour flight 😉
@dnolen Thanks. 20k is awesome! And thanks, by the way, for all your work to make this possible. :-)