Fork me on GitHub
#clojure-uk
<
2021-03-16
>
dharrigan06:03:36

Good Morning!

Gulli09:03:48

Longshot but, is there somebody here living (or has lived) in Gibraltar?

jiriknesl09:03:10

I have been there for 7 weeks this spring and a friend of mine have lived there for a couple of years.

gcaban11:03:10

How was your stay in Gibraltar? Was it for work or just doing the digital nomad thing?

jiriknesl13:03:26

I loved it. When my kids will go to some secondary school, me and my wife will relocate there.

jiriknesl13:03:24

We have been there during the first UK lockdown. In the beginning, we wanted to stay just for 4 weeks but in the UK the situation was getting worse and worse, while on Gib, there were almost no cases, no deaths, so we have prolonged our stay until kids have returned to school.

gcaban13:03:49

sounds brilliant! Thanks for the tip, I might give a try.. 🙂

gcaban13:03:33

as soon as things open up of course

jiriknesl13:03:43

Now, when there’s almost no tourism, is the best time. Otherwise, Gib will be very expensive for a tourist. For living, it’s still cheaper than the UK (depends on place of course).

dharrigan15:03:26

I see that Java 16 is now out

dharrigan15:03:40

and with it, this the default value of the launcher option --illegal-access is now deny rather than permit.

dharrigan15:03:50

As a consequence, existing code that uses most internal classes, methods, or fields of the JDK will fail to run.

Conor16:03:00

You're going down for illegal access, perp. You'll be doing 25 to life in a supermax before you can say Oracle.

🧑‍⚖️ 3
mccraigmccraig17:03:59

just loaded our prod system with --illegal-access=warn and found a couple of SAX and X.509 accesses in clojure-1.10.1 which will presumably be fixed soon (if they aren't already fixed in 1.10.3) and then a couple in netty which are perhaps a bit more troublesome - especially if it's the netty i'm getting through yada/aleph

dharrigan17:03:26

Yeah, it's mostly the 3rd party libraries that will be at issue here.

dharrigan17:03:42

Maybe they'll be updated....in a few years....

mccraigmccraig17:03:14

there will presumably still be the --illegal-access=permit get-out-of-prison card to play ?

dharrigan17:03:38

Indeed, although the window for that being allowed becomes shorter each year

dharrigan17:03:56

With this change, the default value of the launcher option --illegal-access is now deny rather than permit. As a consequence, existing code that uses most internal classes, methods, or fields of the JDK will fail to run. Such code can be made to run on JDK 16 by specifying --illegal-access=permit. That option will, however, be removed in a future release.

mccraigmccraig17:03:33

well hopefully we'll have moved off of aleph by the time that day comes around 😅

dharrigan17:03:55

Has anyone here in the UK had their company sign a waiver to say that whatever software they do out-of-hours (like helping to support OS software, or writing their own stuff) does not belong to the company?)

Hugh Powell23:03:22

I haven't got them to sign a waiver, but have asked them to remove those clauses in the contracts I've signed (which they've mostly done). I'm not a lawyer so not sure if that is sufficient.

dharrigan07:03:12

sounds good!

alexlynham12:03:58

iirc i've got people to do that in the past or just get it in writing in an email

alexlynham12:03:21

their position would i don't think be tenable legally anyway cos if it's not related to their business then copyright is very strong in the uk in favour of the original creator's moral rights, you really do have to explicitly sign it away

alexlynham12:03:22

i write words for money as well so i tend to have to balance this across multiple clients at once and the blanket assumption you see in dev contracts is so different for how specifically worded transfer of copyright etc is worded for example in a contract you make with a publisher

alexlynham12:03:41

for some at invoice time, per piece of work you have to confirm that you sign it over

alexlynham12:03:08

so if you're working on software that's in a different area (so it's out of bounds for a no-compete claim) you're likely totally scot-free

alexlynham12:03:29

like i say, always worth explaining your position and getting an exemption or something in writing anyway :)

alexlynham12:03:18

never had an employer be arsey about it tbh, other than a big big big company, and that's just cos they couldn't change standard contract for any reason, so i figured they were honestly too much of a dinosaur to even clock what one employee does

dharrigan17:03:22

I'm looking to see if there is a boilerplate waiver I can reuse.