This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (7)
- # beginners (109)
- # boot (5)
- # carry (2)
- # cider (25)
- # clara (6)
- # cljs-dev (86)
- # cljs-experience (19)
- # cljsrn (1)
- # clojure (183)
- # clojure-dev (7)
- # clojure-dusseldorf (7)
- # clojure-gamedev (2)
- # clojure-greece (32)
- # clojure-italy (2)
- # clojure-norway (1)
- # clojure-russia (228)
- # clojure-sg (3)
- # clojure-spec (38)
- # clojure-uk (104)
- # clojurebridge (1)
- # clojurescript (29)
- # community-development (9)
- # core-async (118)
- # core-matrix (20)
- # cursive (5)
- # datomic (140)
- # emacs (25)
- # figwheel (1)
- # hoplon (21)
- # jobs (4)
- # lein-figwheel (2)
- # luminus (10)
- # lumo (35)
- # off-topic (137)
- # om (31)
- # onyx (62)
- # pedestal (6)
- # reagent (25)
- # remote-jobs (1)
- # ring-swagger (11)
- # spacemacs (2)
- # test-check (17)
- # uncomplicate (10)
- # unrepl (1)
- # untangled (20)
- # vim (4)
- # yada (3)
@otfrom I tried org-jira-mode and most of the functionality doesn't work. I can't update 'tickets' from the mode and to be honest it's far too verbose for just a TODO and Pomodoro'ing. I'll stick to just copying the ticket number and desc to a normal org-mode TODO.
@maleghast the is no particular pub frequented after the TW dojo. A few people may go, but it's rare and self organised.
@jr0cket - Thanks 🙂 I am toying with emailing Yolina and asking if it's ok if I am a little late, and may have to bail at very short notice. I have a work meeting at the end of the day and there is a reasonable risk that it might turn into dinner and that I will need to be "around".
I do think the "Clojure is not fun to use" argument is very relative...i.e. it depends on where you came from. I found it more fun than Java (or Fortran or COBOL or C++) but Rubyists probably don't.
@agile_geek as an ex-rubyist i can state categorically that clojure is a lot more fun than ruby
@agile_geek - I tend to agree. As a polyglot programmer who started with (sharp intake of breath) PHP I am quite certain that I get more out of Clojure than I do out of any other language, but I do__ like Ruby and Python very much, so I can understand the writer's split feelings on the matter. What I would say is that I have experienced nothing but extreme, genuine friendliness, patience and generosity from the community, but I realise that this is one person's experience...
I, perhaps, have a lot more time for Ruby, still, becuase I stayed the Hell away from Rails, but I am not 100% sure about that
> Each of these has their most prominent mantra. For Clojure it’s “Simple vs. Easy” That’s not what Simple made Easy said at all
It says simple and easy are different things, simple is more important, and both is still best
to be fair he does go on to say > Clojure is not designed to be hard, to the contrary, I think a lot of thought has gone into making it easy to use as well, but when ease and simplicity are at odds, then simplicity always wins.
Anyway, I was not filled with any negative feelings at reading the article, apart from a sinking feeling that anyone feels the need to write (other) articles about how Language X is dying / dead.
i think there are some nice things about ruby @maleghast - it's pretty nice for a
[dynamically-typed, OO, mutable-state] language, but these days i think the fewer of those particular attributes your language has, the better. the good unix integrations in the stdlib still make it my goto choice for non-trivial scripting though
I felt the author of the blog I posted was quite balanced in his view...the original presenter of the talk that sparked this debate and the post, posted this https://blog.appcanary.com/2017/hard-isnt-simple-ruby-clojure.html which is also fairly written as he's caveating it with YMMV. I watched his talk too and it left me a little sad he'd struggled but he admitted he went back to "what was familiar to him" and that was more productive but he learned from Clojure.
@mccraigmccraig Yeah, I agree with you there. Being a jobbing developer for so much of my career I have had to accept that I sometimes need to take the "win" I can get... I've been trying to persuade my peers and / or subordinates to use Clojure for 6 years with no success... Sometimes it's more realistic to settle on Ruby simply to eliminate PHP from the discussion... 😉
I do think long and hard about the fact that if I hadn't had the chance to practice Clojure for years and then get paid to learn from a real set of projects in an org with real problems I'm not sure I would pick Clojure when I get my own startup off the ground.
I would probably have reduced the risk (as it would be spending my own money) and stuck with what I knew.
After all, as I always say, we are not paid to write code, we're paid to deliver value...although writing maintainable code is part of that.
that would have been a sane course of action for you @agile_geek - it would be extra risky to undertake an already risky venture with unfamiliar tools
@agile_geek - I REALLY understand that. If the work I am doing at the moment were about building a complex web application for the public to interact with it would not be Clojure-time for me, right now, it would be Python-time
Given that and the fact that when I make decisions in other's companies I think about what I'd do if it was my money I can completely understand why anyone would need a very compelling reason to adopt an unfamiliar language.
I like the “innovation credits” idea from http://mcfunley.com/choose-boring-technology
@glenjamin living for years in large enterprises and consultancies I've always been 'boring' about my tech choices...mostly it's worked although the headaches have sometimes occurred years down the line. I take a few more 'calculated' risks now but you're definitely 'spending your innovation tokens'
@maleghast fortunately i have rolling deployments and it's easy to rollback, so not too scary
though i do use most of the libs on your edge, with the notable exceptions of selmer and component
@mccraigmccraig lost a little love for selmer. I'd take a recommendation for something else in there.
dunno @dominicm - 99% of our html output is via a re-frame SPA, and the remainder is very simple and just plain hiccup - i haven't looked for any more sophisticated backend html rendering solution
@dominicm ditto at my current client...what is it about Selmer that you're not keen on?
https://github.com/yogthos/Selmer/issues/150 is one that I caught the other day which confused me.
FWIW, I am loving using Edge, starting from a dead stop and wanting to be able to quickly and easily create an API and some web-pages out of some prototype code (I already told @dominicm)
I never got on with Pedestal, and I never had the time to look at Hoplon and Luminus. I am curious about Arachne, but it's taking a long time to get to a place where I feel confident in investing any time in it.
For right now, Edge has up-sides for me, but I am not saying there aren't other choices or that it's perfect. 🙂
That having been said, I still think that for small, simple things, like a lightweight API that "does one thing well" there is a beautiful simplicity to Liberator with Bidi or Compojure (ymmv, I prefer Bidi) and a good JSON library like Cheshire... Sometimes a framework is too much, and I feel the same in other languages. I prefer to use Sinatra or even just plain Rack in Ruby and I like Flask or even Bottle in Python...
Also, the issue that @dominicm mentions aside, I am finding Selmer very productive / intuitive, fwiw...
@maleghast bidi+yada is also great for an API (that is in fact what my API is using)
Yeah, I am pro Yada, and on reflection I might well use it instead of Liberator in the future.
also yada is async and liberator isn't - and i try and avoid non-async things these days
Yes, I fundamentally like Selmer. I'm not entirely sure on the implementation yet though is all.
Yes, I like Yada's async-ness, but there are times / places where sync is not only not a risk but also required, so I don't mind that Liberator isn't...
well, transparent @dominicm until you realise that the pubsub lib you are using to feed your websockets uses a
Thread per subscription... then unhappiness
@mccraigmccraig I mean rather, yada doesn't care if you're using sync. It will happily block. You don't get some of the benefits of async, but c'est la vie.
We use Selmer at World Singles for all our HTML emails and quite a few small web apps. The tags/filters approach has proved pretty flexible for us (we've written several of our own).
We also use Hiccup for a couple of things (where we're transforming complex data structures to complex HTML at runtime).
Mostly we use Compojure for routing but one of our new projects uses Bidi and that has pros/cons but might cause us to switch other projects over in time.
And all our apps are Component-based, with a "standard" WebServer Component we've developed ourselves that wraps Ring/Jetty/http-kit (we pick the server type at startup).
The keyword tagging in Bidi allows for better separation of concerns. I'd have to ask my colleague to get more specific.
I'd want to write Bidi routes in some syntactic sugar tho' -- I find the bare usage a lot uglier than Compojure.
(I might be able to be more specific when I get to my desk and can look at code!)
@otfrom I would second @seancorfield on the Pros - being able to enumerate and reverse-lookup routes is really great. Also, Bidi does a great job of separating routes from "action" as ALL it does is routing, so you can change the way in which you are building resources without having your routes coupled to your logic. Well that bit makes me happy anyway... 😉
has anyone tried lacinia yet? I've not looked at it enough but it almost feels like liberator/yada:rest :: lacinia:graphql
@otfrom we've just added lacinia to one of the services in my client but I haven't had time to look at it.
@agile_geek I think you are adorable the way you refer to them as your client even though you are contractor scum there so it is just "work" 😉
@otfrom They are a client of my company and I work for my company in a manner that I determine....or as far as IR35 is concerned I do!
btw, having a really useful discussion (for me) on using lumo for day to day scripting