This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aatree (3)
- # alda (8)
- # avi (21)
- # beginners (37)
- # boot (193)
- # cbus (1)
- # cider (29)
- # cljs-dev (8)
- # cljsjs (3)
- # cljsrn (20)
- # clojure (76)
- # clojure-dev (13)
- # clojure-miami (20)
- # clojure-portugal (2)
- # clojure-russia (220)
- # clojure-sg (2)
- # clojurebridge (5)
- # clojurescript (94)
- # community-development (14)
- # conf-proposals (110)
- # core-async (12)
- # cursive (12)
- # datascript (6)
- # datomic (14)
- # dirac (72)
- # emacs (49)
- # hoplon (86)
- # jobs (33)
- # jobs-discuss (1)
- # ldnclj (6)
- # lein-figwheel (1)
- # off-topic (56)
- # om (139)
- # onyx (29)
- # pedestal (17)
- # proton (23)
- # re-frame (45)
- # reagent (35)
- # ring-swagger (4)
- # test-check (1)
- # testing (8)
- # yada (11)
sitting in on this channel really makes me worry that I didn’t consider my proposal well enough
2 proposals are ok
3 proposals - I prefer you'd check with me first (ghadi, I think all of yours would be fair game )
And don't submit more than 3 :)
I have my personal preferences but I will recuse myself :)
it's the 2nd-to-best day to work on proposals
tomorrow being the best of course
@alexmiller: I really don't need you to encourage my procrastination, do I? 😼
given that tagged literals were the least important ranked feature, it seems ripe for a conference talk
@ghadi: that's a great idea
I'm starting to think we need a ghadi-conf
heh, riiiiiight. I think I'm leaning towards the parsing virtual machine one. I have actual working code for it.
that way you'll finish it :)
Here are my two ideas: 1 - Bootstrapped CLJS for fun + teaching 2 - Paradigms for Asynchrony; Rx, CSP, async/await, Promises any thoughts?
Oh, I already submitted mine, but I'd like to get feedback from here: what does everybody think about a ClojureScript on Amazon Lambda talk, including a case study?
I was looking at it really closely as part of an arch proposal a few months ago but couldn’t find a lot of information out there
yeah, the main thing is that Clojure startup time in a lambda environment can be pretty rough.
I was looking at it in a context in which the lambda job would take a couple of minutes to run anyways so the startup time wouldn’t be as big of an issue
just very demand-driven, so didn’t want to have to deal with autoscaling resources myself
but I’ve never given a talk like this before so I don’t really know if I made a very good proposal or not
the more VMs clojure can run on the better. 😉 are you going to Go bytecode or transpiling?
at the moment it would be more accurate to say that clojure code is passed into an interpreter and executed with the compiler in its current state
these are questions I haven’t spent a lot of time thinking about yet as I’m still focused on the core data structures and interpreter loop
@jaredly: about #1, I submitted the same, putting in some Spark as well 😉
we are on the same wave length about this I guess we should join forces
I submitted yesterday so let's see how it goes 😄
Okay, here is the first draft of my Experience Report abstract about the development of Braid:
Slack is a popular chat application that was spun out of the development of an online game. Braid is taking the opposite approach - beginning life as a chat application that will evolve into a full-blown virtual reality and gaming platform. Braid is an open-source group chat application for teams and communities designed to promote productive conversations. For rapid development and flexibility, Braid is leveraging Clojure, Compojure, Sente, core.async, ClojureScript, Om, Datomic and PostgreSQL. And with its innovative approach to conversation management, Braid is anything but an IRC clone.
@meow: Did you get it submitted before the CFP ended?
@shaun-mahood: It ends tomorrow. Haven't submitted yet, still working on it.
Oh good - I got an email and misread it, thinking that it already ended.
@meow: Feedback on the clarity of the message. I'm not sure what I would get from attending your talk - is it an overview of the app, the design, the code, how you used the libraries, the plan to evolve?
I picked the wrong talk at the Conj based on the abstract not quite reflecting what the talk was and have been kicking myself since, so don't want anyone to do the same for yours.
A also think it might be good to have something about the community development aspect and how it grew out of the needs of the Clojure Slack community (if that's still the case).
Yeah, I'm not happy with it. Struggling with it. Can't come up with the right angle yet.
Sorry, pulled away for a second. Gonna try and come up with some ideas that might help.
It's tough because I haven't written any code for Braid (yet). I use it every day since it became open source, stress-test the heck out of it, demand features like a two-year old, and have contributed to many of the Github issues. All the code has been written by @rafd and @jamesnvc, who aren't able to attend Clojure/west.
Do either of them have any thoughts? Maybe some parts of the code that were interesting, or unique challenges?
I think I would be more comfortable if I came up with an Experience Report from my point-of-view.
I've presented at tech conferences in the past but it was always about code I had written.
Yeah that makes sense. One of the many awesome things that I heard at the Conj was "talk driven development" - not sure what your plans are for the next couple of months, but I'm guessing that whatever this proposal ends up as will contribute to it. What do you want to be working on?
My proposal has effectively prioritized a lot of my free time for building some specific things that I want to present, but I also find interesting and will be of great value to my workplace. Try and think of what angle of Braid might do that for you - is it the front end, back end, the design, getting features in, the general community?
Slack is a popular chat application that was spun out of the development of an online game. Braid is an open-source group chat application for teams and communities designed to promote productive conversations and aiming to replace Slack for open source communities. For rapid development and flexibility, Braid is leveraging Clojure, Compojure, Sente, core.async, ClojureScript, Om, Datomic and PostgreSQL. And with its innovative approach to conversation management, Braid is anything but an IRC clone. <Magical last sentence>
And then replace
<Magical last sentence> with your purpose statement - here's how it's evolving to become a full-blown virtual reality and gaming platform; here's how we used these powerful technologies to create something great; here's how ....
Here is my bio:
Unrelated, one of my goals for this year is to get Clojure/CLJS working as my primary AutoCAD development language at work
I think a link or more info on your 3D clojure stuff would be interesting on your bio - it might help people go "oh, that guy!" when reading it. I know I saw a bunch of your stuff online before I knew who you were so other people might too.
Did you watch this conj video? https://www.youtube.com/watch?v=uk3A41U0iO4 Used OpenSCAD driven by Clojure too.
I forked scad-clj and changed it / added to it https://github.com/pkobrien/scad-clj
Really good presentation, I missed it at the Conj.
What are you using now instead of OpenSCAD?
From my perspective, the interesting part about it is a different way of looking at conversations
Mostly want to give an Experience Report from my point of view as a user/abuser of Braid.
And getting more of the community involved is important to me and something I'm trying to shepherd.
What do you think is going to change between now and April? you could focus on the experience of developing and driving that change (from the entire Braid team's perspective)
haha, it was pretty good — having only two users before you, it definitely helped us think about it from a different perspective
Off for the day, will gladly give more feedback tomorrow if there's any more needed. Enjoy the last minute prep time, it's usually the only time I get anything done.