Thanks Timothy for detailed insight, especially point #4.
In my case I usually use AWS for deployment.
AWS marketplace allows Azul Zing on Ubuntu at $0.2/hr ( $144 /month/ec2
instance + $10 flat fees = $1738 annually) for instances like
i3.xlarge (30GB RAM, 4 CPU core), which is workable for
Hi,
I've been an enthusiastic Clojure tinkerer for a few years now--it's a
great language!--but only recently began using it professionally, where
I've stumbled into a strong disagreement over the use of protocols vs.
multimethods for single dispatch polymorphism. I had always assumed that
pro
I've worked on several projects where Zing was considered as a solution to
a few problems (normally GC pauses due to really large heaps). But in the
end we never trailed it, due to a few factors:
1) Zing isn't super cheap, it's not that expensive in the grand scheme of
things, but it's an addition
IBM Java likewise has not excited very much conversation here. Perhaps
because Java is "write once, run anywhere"! The various implementations of
Java have their strong and weak points, but they will run Clojure in any
case.
--
You received this message because you are subscribed to the Goog
The simplest workaround I found in the bug report you have shared here, is
to configure Java to change the keystore type from pkcs12 to jks by simply
editing the file `/etc/java-11-openjdk/security/java.security` and changing
"keystore.type=pkcs12" to "keystore.type=jks" as it is explained in the
oh, it seems that fix is for yet another ubuntu ca-certs java bug, I hadn't
expected there were more
On Mon, May 21, 2018 at 1:25 PM Andy Fingerhut
wrote:
> Thanks, Justin.
>
> I tried the commands you suggested on an Ubuntu 18.04 LTS system, and
> 'lein repl' still fails the same way afterwards
Thanks, Justin.
I tried the commands you suggested on an Ubuntu 18.04 LTS system, and 'lein
repl' still fails the same way afterwards when using Ubuntu's OpenJDK
installation (and still succeeds when using Oracle's JDK installation).
Andy
On Mon, May 21, 2018 at 1:04 PM, Justin Smith wrote:
>
On Monday, 21 May 2018 20:22:21 UTC+1, Andy Fingerhut wrote:
>
> Is there some other command you would recommend to force reinstall of
> ca-certs that might work?
>
> Specifically on the ca-certs thing, there is a bug filed with Ubuntu, and
it looks like it should be fixed fairly soon;
https://bu
I should have been more specific. Just uninstalling leaves old configs
around, and fixing this requires a full purge of the package.
these are my steps on a debian system:
$ sudo dpkg --purge --force-depends ca-certificates-java
$ sudo apt-get install ca-certificates-java
sourced from this stac
Jesús:
Agreed that this issue is frustrating. It doesn't necessarily help you
here, but realize that this issue appears like it might be unique to Ubuntu
18.04's OpenJDK installations.
This issue did not occur with earlier versions of Ubuntu that I am aware of.
Andy
On Mon, May 21, 2018 at 10:2
Justin, I have tried doing these commands on an Ubuntu 18.04 LTS system
(which I believe is Debian based):
% sudo apt-get --reinstall install ca-certificates
% sudo apt-get --reinstall install ca-certificates-java
Afterwards, the command "lein repl" still fails when using Ubuntu's
OpenJDK8 or Ope
this is a problem with your distribution's config for installing the vm, on
debian based systems it can be fixed by forcing reinstall of ca-certs, it
does not require an oracle vm
On Mon, May 21, 2018 at 10:30 AM Jesús Gómez wrote:
> I followed the Getting Started guide and nothing worked well,
I followed the Getting Started guide and nothing worked well, except
for the boot with nix installation.
The clj tools Linux instructions failed the same way the lein one
failed: Error with some certs [1]
I've been told that this problem could be solved if I install Oracle
Java instead of using Op
As of Clojure 1.9, the Clojure jar depends on two additional libraries
(spec.alpha and core.specs.alpha). Using only the clojure jar is thus not
sufficient.
There are several ways to handle this, as described on the
https://clojure.org/guides/getting_started page.
1. Use the new command line
Jesús Gómez wrote:
> Simply: 1.7 works but 1.9 not.
> Test:
> $ # Download Clojure 1.7, 1.8 and 1.9 jars
> $ seq 7 9 | xargs -L1 -I% wget
http://repo1.maven.org/maven2/org/clojure/clojure/1.%.0/clojure-1.%.0.jar
> $ seq 7 9 | xargs -L1 -I% java -jar clojure-1.%.0.jar -e '"1.%.0 is
Working"'
> "1
Simply: 1.7 works but 1.9 not.
Test:
$ # Download Clojure 1.7, 1.8 and 1.9 jars
$ seq 7 9 | xargs -L1 -I% wget
http://repo1.maven.org/maven2/org/clojure/clojure/1.%.0/clojure-1.%.0.jar
$ seq 7 9 | xargs -L1 -I% java -jar clojure-1.%.0.jar -e '"1.%.0 is
Working"'
"1.7.0 is Working"
"1.8.0 is Wor
Strange ! nobody using it ?
I saw the Rich Hickey's testimony on their site
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patie
17 matches
Mail list logo