Clojurians Log v2
ldnclj
I feel your pain @gjnoonan - truly I feel it
Good morning.
good morns
Morning peeps
morning
Morning
[OT] I will have to chose a pension provider for my company and for myself soon. Does anybody have any recommendations or methods and techniques to find a good/appropriate one?
Good morning
@pupeno: No. But I too would like to know.
I read all the Re-Frame docs last night. Holy poops. it seems so simple.
xlevus: yeah. I’d be afraid of being one of those cases of beautiful when simple, horrible when complex. I can see an app turning into a mess of events that you have no idea where they are coming from.
xlevus: shameless plug: https://carouselapps.com/prerenderer 😉
Yeah, I saw that yesterday. Nice work.
But, for what I plan on doing, it isn't necessary. Yay gamedev.
xlevus: where you at the ClojureScript workshop?
No
Ok. Someone else was talking about gamedev in clojurescript there.
I still haven't really written anything in clojure yet :/ Mostly just been reading docs, busy with other stuff, and changing my mind on what I want to write more often than a dice on a steep incline
It'll get to the bottom soon... I'm sure.
You think there’s a bottom?
One can hope.
What are you changing your mind about?
what to work on. I have an idea for a SAAS product. I could probably finish it in 6 months if I stuck into it, took some time off, and did it in python, but I don't like Python any more. So I want do it in Clj, but I sort of need to get a little more comfortable with the language. So my current idea is a small game. Which I could then use to dogfood the SAAS.
I know what you mean as I’m transitioning my company to Clojure.
@pupeno: fancy doing an experience report on how this went in a few months once you’ve got further into it?
Sure.
My transitioning the company to Clojure seems to be a long endeavour, got one dev on my side and now he loves it, 3 more to go. Will get there in the end.
Cool.
Maybe it could be a panel of companies that transitioned or are transitioning.
This year ClojureX would be too soon for me, I think.
related: This recent episode by Anthony Marcar on Cognicast is pretty good, he talks about how he started a clojure team at walmart labs http://blog.cognitect.com/cognicast/087
@pupeno: that’s what I was thinking..one for a SkillsMatter talk next year?
Yeah, that could work.
hi @pupeno I'm having a chat with Skillsmatter tomorrow about running a panel to debate "State of Clojure" Is mass adopting happening
Am hoping to get a good panel, with relevant people, not just from the clojure community
happy to sync up / discuss
me too.
@jonpither sounds good. I see resistance in bank I'm working for mainly due to the 'we can't get developers for that from our outsourcing partners’ argument.
guess they just need better outsourcing partners
@xlevus: that would cost more per ‘unit’ (unit is the new euphemism for ‘resource’ which is the old way of insulting people!)
Developers are a fungible commodity to these organisations.
True
So true. Clj accentuates the problem as better devs become better - so dealing with managers who see devs as commodities is harder. Harder because the CLJ devs become harder to yank out, and they are more expensive
At least when you're wading in concrete, everyone is going at the same pace
@jonpither: these managers are measuring the wrong thing…measure value defined as features delivered (and their ROI) compared with cost of dev team…might get a completely different result!
it's so hard not to get taken for granted. Success becomes the norm, and people get used to it
…on the other hand as I want to set up a biz of my own sometime soon…I hope they don’t do this. Never hurts to have competitive advantage.
yeah
@jonpither: Here’s a question for the ‘State of Clojure’ panel…do we (as a Community) want mass adoption?
great one :simple_smile:
It'll be a fab panel
What would be the downsides to Mass Adoption?
Python pretty much made it to mass adoption, and yet developers for it, competent or not, are still hard to find
@xlevus: reputational damage to the language if quality of development drops?
Playing Devil’s advocate here
Yeah, perhaps
Java has suffered from this a lot
The language isn’t horrific but the swarm of poor quality developers and their code has given it a bad rep in recent years. It used to be the ‘cool kid’ on the block
yeah java was the cool kid :simple_smile: fun times
@agile_geek: you can't deny what your saying I think. Once the mass outsource companies pick up a lang, quality will drop
enjoying the chat. but I have to hit the underground
@jonpither: seeing this already in Scala!
lets chat about the panel again on here tomorrow
Java without semicolons
@jonpither: catch u later
but, even if quality drops, the language still seems to lead to much simpler code.
I guess you can't bill by SLOC when you require half as many lines
@xlevus: will it? I’ve seen procedural code jammed into Java methods in classes that have no relation to each other…why would we not see massive functions in one namespace?
Good point.
@xlevus: I like your optimism but I think mass adoption may not be all good.
ultimately, whatever happens happens, and we just have to deal with it
well, it’s really possible to write horrible clojure code
i don’t think we want mass adoption, and I doubt it will happen anyway ^^
but I would hope for larger adoption to a degree
@quentin: I’m with u on all of those comments 😄
at least large enough to have more work opportunities with clojure
but in any case, using clojure now is useful to me already, so I am pretty happy with that :simple_smile:
I personally think the biggest barrier to entry is the steep learning curve, not just the language but the lack of a standard framework meaning you have to invest quite some time into researching and trying different libs.
agreed
you can have some decision paralysis when choosing your tooling
plus the libs/tools are evolving quite rapidly
And some of them, you look at, and go "This is like, 100 lines. This surely can't do what I want"
@agile_geek: i disagree about java - i think the language is pretty horrific - it makes it very hard to produce abstractions and makes you pointlessly type a lot
com.company.department.unit.user.functionality
com.company.department.unit.user.functionality.FactoryBuilderInterfaceDecoratorFactoryFactory
+1
@mccraigmccraig: +1
and don't forget you can write horrible code in any language.
"idiomatic" is the key word I think,.... and I suspect Clojure programmers are keen on doing that... and not just hack away till something that kinda works
I think the closest thing I've seen to Java's namespaces of finger-fatigue in Clojure are the Taoensso libraries.
and they really irk me, because I can't spell it for the life of me.
@xlevus: i have that problem too :simple_smile:
Maybe I should open a ticket. See how many +1's it gets
@xlevus: I have the same thought everytime I require one of those!
@mccraigmccraig true but my point is when it was written noone foresaw this. saw Yodit complaining on twitter about everything ending up being a 'Stuart Sierra Component' whether it needed life cycle or not. The Clojure equivalent of Spring for everything? I guess my point is everything gets abused at some point and the more Clojure moves to mass adoption the more this will happen.
Facebook down, I think they’re having trouble rendering React on the server, @pupeno give them a hand. 😛
@agile_geek: i don't think we have enough dimensions hers. there are two metrics for a given language - 1. how inevitable terrible code is and 2. how possible elegant code is where the worst case is [1,0] and the best [0,1] ... i would put java at [0.8, 0.4] and clojure at [0.5, 0.7]
i have high hopes that lux will be a [0.4, 0.9] but they will probably be dashed because everything is terrible
the worst case in clojure could easily get a lower value I think
oh lux is on jvm as well
damn
@quentin: not for long i think - iirc he has a plan to bootstrap it and provide minimal platform shims, though my memory may be deceiving me
good :simple_smile:
@mccraigmccraig I agree. Although I think the reason we are less likely to see massive imperative style funcs in one namespace, etc will be more to do with the outsourcers not adopting it than the two factors u mention...but I may just be scarred forever from working in that world for too long 😉
@agile_geek: there will always be massive imperative style funcs ... i don't care that the outsourcers can fuck things up, as long as one is not forced to do so, and it's easy to do things elegantly