Fork me on GitHub
#clojure-uk
<
2020-02-19
>
dharrigan06:02:01

Good Morning!

dharrigan07:02:19

I think it's great that libraries are being encouraged to have their version bumped up to a 1 if appropriate

dharrigan07:02:52

I do actually meet resistance about some libraries that seem to be 0.0.1 alpha etc... even although they stable and have been for years

seancorfield07:02:24

It's a bit strange for me... years ago I asked about moving java.jdbc to 1.0.0 and the core team pushed back with all sorts of things they wanted fixed first.

seancorfield07:02:42

And now here we are moving everything to 1.0.x "as-is".

seancorfield07:02:32

I just pushed java.data to 1.0.64 and I've decided to move next.jdbc to that as well (1.0.375 will likely be the next release).

dharrigan07:02:48

I think this is where idealism meets reality. When working in a company that does software, often questions are raised about libraries used etc... and if they are all alpha, or 0.0.1 etc., the business does want to know why such a version...

dharrigan07:02:20

It's just another (rightly or wrongly) hurdle to jump over for adoption.

dharrigan07:02:08

so at least having a 1.0.0 version, which software people tend to think as being the first stable release (yes, I know semver etc.., can/is controversal) it does help in adoption

seancorfield07:02:25

I've never worked anywhere that cares about that -- or about putting alpha/beta libs in production -- but I know I'm in a weird minority.

👍 4
seancorfield07:02:36

SemVer is a pile of junk.

dharrigan07:02:53

I worked for a few financial institutions in my time that did tend to have many eyes on software and what is used (justifiably so, this is people's money!) and even although nothing formal is defined, there was some talk about which libraries to choose.

dharrigan07:02:35

oooh, sorry, tiny chat today! the kid - he's alive!!! time to fetch, water and feed him!

seancorfield07:02:48

Hahaha... and I'm off to bed!

marcus08:02:09

Morning guys!

dominicm08:02:48

I've used a very simple SemVer-compatible scheme for a while. 0.x.0 or 1.x.0 Leading 0 means unstable/alpha, middle number is release count. That's it.

Conor08:02:36

All I can say re: library version changes is "about time"

dominicm08:02:14

I think a lot would have been solved by just being upfront about the version policy tbh

rickmoynihan09:02:38

I must say I’m not entirely wild about the pointless version change across so many libraries. It’s not a big deal or anything, but it feels like arbitrary churn to me.

marcus09:02:41

> I must say I’m not entirely wild about the pointless version change across so many libraries. It’s not a big deal or anything, but it feels like arbitrary churn to me. It looks like a formality.. People that give more importance to the stable nature of the library won’t mind the version change, and people that give semver more importance will feel more comfortable using a 1.x.x lib… so it may seem good for the community in general.. 🙂

rickmoynihan09:02:03

It is, but I review a lot of clojure projects — so when dependencies change I have to check what actually occurred in the library, to see if there are any other consequences of the change. As not all libraries are purely accretive. For example I experienced some breakages recently upgrading some ring dependencies that were supposed to be purely accretive; but subtly weren’t. Overall I agree with the policy and direction, it just creates busy work downstream.

marcus11:02:53

:thumbsup:

dharrigan09:02:03

I think it's great - but as pointed out, it is optional to upgrade - if you're happy to keep with the version you have, no problemo! 🙂

dharrigan09:02:47

(for me, atm, the only update to my libraries is core async 🙂 )

acron09:02:12

Did I miss something? Who's encouraging libraries to move to 1.x.x ?

rickmoynihan09:02:34

see #announcements

dominicm09:02:38

All the core clojure libraries are now 1.0 if they are stable

rickmoynihan10:02:15

It’s interesting that spec.alpha is still on 0.2.176 and hasn’t been upgraded to 1.0. Obviously I understand why in that the design isn’t quite right; but spec.alpha is stable and shouldn’t see breaking changes it’s just not compatible with spec2

dharrigan10:02:20

Maybe Alex hasn't got round to that yet - or maybe he forgot 🙂

dharrigan10:02:28

Or maybe, like you hint, it's special 🙂

rickmoynihan10:02:15

It’s certainly special 🙂 It’s a dependency of clojure itself which isn’t alpha.

thomas10:02:19

yup, looks like a pineapple to me.

🍍 16
Aleksander11:02:05

and this is the technology that powers self-driving cars?

Conor11:02:24

The fully self-driving car is a mirage that will always be 20 years over the horizon

dharrigan11:02:29

I don't get it - I already have a self driving car, as in (my)self driving it

dharrigan11:02:53

bit dodgy at times, but mostly reliable

😂 8
3Jane11:02:16

you'll age at some point

3Jane11:02:35

even people who are great at driving could use a self-driving car as they get older.

mccraigmccraig11:02:41

the big question @conor.p.farrell is which of fusion power and self-driving cars will we get first

dharrigan11:02:50

I thought that's what having kids was for? For driving me around when I'm old(er) and (more) decrepit?

dharrigan11:02:30

Then it'll be (him)self driving (the) car 🙂

3Jane11:02:25

Well, as long as they live with you. Most people in the west don't.

dharrigan11:02:41

I intend for him to live with me fooorrevvaar

dharrigan11:02:27

but anyhoo, will be moot point - by 2030 all forms of motorised vehicular transport will be banned and we'll be using teleporters - just like in star trek 🙂

3Jane11:02:47

I'm a big fan of anything that is enabling greater self-sufficiency for young/old/people with temporary or permanent disabilities. I just wish it wasn't done in the spirit of startups, move fast and break things.

3Jane11:02:51

Teleports would be 👌

3Jane11:02:02

Re-wild the transport network!

mccraigmccraig11:02:00

create-a-copy then destroy-the-original : what could possibly go wrong ?

mccraigmccraig11:02:01

or, alternatively, tear spacetime a new one and send yourself through : what could possibly go wrong ?

3Jane11:02:19

now you're making me think: how would human checksums look like

Conor11:02:31

Neither @mccraigmccraig, I'm afraid

dharrigan11:02:33

I read once that in order to create a teleporter, it would require more energy output than the entire universe has produced todate.

3Jane11:02:04

pneumatic tubes then.

dharrigan11:02:18

ha! just like futurama!

Conor11:02:23

It's well known that the internet is a series of tubes

3Jane11:02:38

apparently it was possible to send a person in one of those containers

Edward Hughes18:02:56

Well of course. You don't think all those Looney Tunes animators were lying to us when they had characters shunted around as a gag, did you? 😉

3Jane11:02:04

it'd be just like taking the tube, but at least you wouldn't have to avoid eye contact with other passengers

dharrigan11:02:46

take my money! do it now!

3Jane11:02:47

is it the lack of eye contact that is so exciting? XD

3Jane11:02:56

guys, we can now print animations. that's it, that's the end of internet. https://twitter.com/ThamKhaiMeng/status/1229634431377342464

alexlynham12:02:38

I wrote a short story once where we had ubiqitous teleporters to the extent that most buildings didn’t have lifts and it comes out that 1 in like, 10 million uses the person doesn’t walk out the other side & also it turns out the energy req’d is waves hand partly due to destroying the thing entering it, & this causes a global political crisis cos people are so reliant on the tech

alexlynham12:02:10

“what, you mean I kill myself rather than use the stairs??” was I believe a line from it, it was a black comedy and I was young

3Jane12:02:52

> 1 in like, 10 million uses the person doesn’t walk out the other side tracks with car journeys

3Jane12:02:10

(...actually I may have misread the data, but I'm now curious to see what the rate is irl 😄 )

3Jane12:02:15

iow: life is a black comedy

3Jane12:02:13

in other words, sorry

👍 4
dharrigan12:02:44

what a very clever idea (the augmented reality for charts in newspapers)

Rachel Westmacott13:02:23

RCFOTD:

clojure.core/lazy-cat
([& colls])
Expands to code which yields a lazy sequence of the concatenation
  of the supplied colls.  Each coll expr is not evaluated until it is
  needed. 

  (lazy-cat xs ys zs) === (concat (lazy-seq xs) (lazy-seq ys) (lazy-seq zs))

nyantocat 8
🎉 4
Rachel Westmacott13:02:50

favourite function name evarrrr!!!!

rickmoynihan15:02:37

It’s a good one… Though I’m also partial to future-cancelled? for the existential angst it invokes. 😀

😁 4
morning 4
dharrigan16:02:32

Well, for what's it's worth, I present to you https://twitter.com/rcfotd

💪 8
8
aw_yeah 4
🐦 4
guy17:02:49

looks good! However iirc clojure peeps don't really like other people using their clojure symbol (if its the same one as on the website)

dharrigan17:02:46

Yes. Will change.

👍 4
dharrigan16:02:01

It's most definitely a work in progress, so...be gentle 🙂

dharrigan16:02:07

and the source code you can chuckle at here: https://git.sr.ht/~dharrigan/rcfotd

marcus08:02:31

I've always found that when people would ask me questions abut my code is when I learn the most.. With that in mind (no other intention than the academic one) and with all my respect.. .. I am asking if you are using (def system nil) for something specific.. for my first thought was that there is declare that would save you the nil binding, but then I saw it doesn't seem system is used anywhere else from (-main).. Anyway, just saying.. you can tell me to pipe down and I'd be happy (is what people end up doing 😁 )

dharrigan08:02:06

No problem. A hang-over from other code. It's used at line 40 where it's stored in the namespace for ease of use later (although I don't use it later, so it could be removed :-))

dharrigan08:02:10

Code review 🙂

dotemacs18:02:15

Mad points for using http://sr.ht @dharrigan 🙂

dharrigan08:02:09

diversity is good 🙂