These are so old, but I (still) often find them laugh-out-loud amusing :-)
https://despair.com/products/apathy
No offense is meant :-). This next one is an apt description of me when I was
super-obsessed with clojure startup time:
https://despair.com/collections/retired/products/stupidity
I'm t
I assume you are forced to use XML (if you are choosing the format, I
wholeheartedly recommend EDN!). If you /do/ control the choice of XML/EDN but
want to interoperate with other languages, check out:
https://github.com/edn-format/edn/wiki/Implementations - maybe you could use
EDN anyhow if y
I finally moved one of my clojure projects from 1.10.0-RC1 to 1.10.0 and
encountered some very strange behaviour. Code that had previously compiled
fine under 1.8.0, 1.9.0, and 1.10.0-RC1 no longer compiled under 1.10.0 with
the following error:
Execution error (IllegalArgumentException) at bu
Thank you, it does help. I almost went the monorepo route but for some reason
thought I'd have one project.clj file with one giant list of dependencies.
Having a monorepo but with different dependency sets makes a ton of sense and I
think would have been much easier to manage.
‐‐‐ Origina
Very cool! By the way, thanks for all the work you have put in to compliment.
Sometimes it's hard to know when/how to thank people. I myself am all too
often guilty of, "Thanks, can I have a new feature or bug fix?"
You, Mr. Emerick, Mr. Batsov -- and many others -- thanks!
I'd start a thank
This is somewhat of a retrospective -- so please bear with me. I've had the
privilege of working on a clojure project for a couple of years now, and have
accumulated some 15-20k lines of clojure code. I'm taking a little time to
look back over what has worked for me and what hasn't in terms of
I agree :-). For me the cost/benefit decision is easy -- I'm using it in a new
interop-heavy project. I posted it here in case others who used cider-nrepl
based tooling may also potentially benefit -- if enough interest maybe I'd take
the extra time to publish it as a library.
Often times I h
you're referring to the new Java syntax of
'var x = new blah();' -- I think that's mainly a reaction to
HowStill>>>>...
I'd almost argue what we do in Clojure is more like gradual typing -- I start
to type for performance/interop reasons (numerical comp
ou want when
> using some of the more byzantine java libraries.
>
> (All of the above works in Cursive, I'm not sure about how it works in CIDER,
> but I assume it's equivalent).
>
> --Aaron
>
> On Tue, Oct 16, 2018 at 8:30 PM 'somewhat-functional-programm
It's not really:
(jvm (var.method))
but
(jvm (JavaType:method var))
Because the completion engines get "JavaType:" as a prefix, they can look up
the type via reflection and present a list of methods for *just* that type.
‐‐‐ Original Message ‐‐‐
On Wednesday, October 17, 2018 4:34 AM, Di
I appreciate your detailed response, and you've certainly done great work with
Cursive. I always recommend it to any Java programmer who is starting to learn
Clojure. I will start to more seriously weigh the pros and consadditional of
switching away from emacs. The cult of emacs has had a str
narrow
down to the exact type I'm using for the reasons we agree on -- simply is
painful to work with.
> On Tue, Oct 16, 2018 at 1:26 PM 'somewhat-functional-programmer' via Clojure
> wrote:
>
>> I apologize for diving into a solution in my first email -- let me give a
Comments inline...
‐‐‐ Original Message ‐‐‐
On Tuesday, October 16, 2018 3:47 PM, 'Tatu Tarvainen' via Clojure
wrote:
> Nice. I like the syntax, I'll try it out.
Thanks -- let me know if the boot command doesn't work... I had to update boot
on one of my boxes to get it to work ("boot
I apologize for diving into a solution in my first email -- let me give a
little more of the background as to what I am trying to accomplish.
I'm proposing an additional syntax for Java interop for the purpose of allowing
support for more precise code-completion of Java fields and methods in Clo
I'd like to share an idea and prototype code for better Java code completion in
CIDER. While my main development environment is CIDER, the small modifications
I made to support this idea were both to cider-nrepl and compliment -- which
are both used by other Clojure tooling besides CIDER -- so
Thanks -- I had seen some Clojure startup benchmarks in relation to Java 9:
https://mjg123.github.io/2017/10/04/AppCDS-and-Clojure.html. I did try these
on one of my projects that uses a lot of Clojure library deps and I went from
~11 second startup to ~5 (both were AOT/direct linking compiled)
Appreciate the pointer towards Lumo and Planck -- I've tried Lumo though not
Planck. I have used Clojurescript at work (not for scripting but for webapps)
and it's been more challenging for me only because I am not as familiar with
the Javascript ecosystem as I am the Java ecosystem.
What I've
ost:
>>
>> Anyhow, thanks again for the video link, always a treat to watch a Rich
>> Hickey Clojure talk that I hadn't seen before.
>>
>> ‐‐‐ Original Message ‐‐‐
>> On April 4, 2018 3:23 AM, 'André' via Clojure
>> wrote
some of the motivation of why not extending existing
>> Lisp->Java integrations, like Kawa and ABCL:
>>
>> https://www.youtube.com/watch?v=cPNkH-7PRTk, around 3:25
>>
>> On 04/02/2018 05:53 PM, 'somewhat-functional-programmer' via Clojure wrote:
>>
&g
I've recently come across Kawa Scheme and am very intrigued by it. It's Java
integration is superb like Clojure and it's very fast. Has anyone here used it
to build something?
So far I've only tried it with small toy programs. Things I like about it:
- Starts up very quickly
- Java method
20 matches
Mail list logo
