Just out of curiosity - did you by any chance warm up the JVM to
make sure that the fib function was JIT'd before you did this
benchmark?
On Feb 23, 5:46 pm, Raffael Cavallaro raffaelcavall...@gmail.com
wrote:
On Feb 23, 2:51 pm, Stephen C. Gilardi squee...@mac.com wrote:
The fibs
Very interesting ideas, everyone... thanks a lot for the input.
Yeah, I recognize that each case is going to be different - I guess I
was just looking for suggestions on how to manage it. Which I found...
Comp and partial look particularly interesting. Thanks!
-Luke
On Feb 25, 5:09 pm, Kevin
The biggest barrier to using Clojure in an enterprise environment is
that enterprise projects are typically built and maintained by 100s of
replaceable code-monkeys and consultants, all of which understand Java
and almost none of which understand Lisp of any kind, let alone
Clojure.
To be
Oh, I agree with you 100%.
I outlined why I wouldn't use Clojure in a project self-described as
enterprise, but at risk of ranting I didn't get into how I consider
the word enterprise synonymous with bloated, bureaucracy-bound,
over-engineered, unoriginal and above all /expensive/ ball of tar.
Ok, sorry for posting this. I figured it out myself.
Turns out that my eratosthenes function took much, much longer on
primes and near-primes than it does on the average number. And, of
course, the numbers that pass through the wheel factorization filter
are just that.
So the good news is that
Well! You learn something new every day.
Ironically, I knew about octal, but back in the day when I was
learning Java, the book I was reading didn't have a typeface that
distinguished O and 0 very well, and since I never had to use them I
never was corrected. Interesting.
Thanks!
On Mar 12,
Excellent... this is the first release of a Clojure IDE that hasn't
immediately proven itself unusable as I put it through its paces.
I expect this will become my main platform for Clojure development.
Thanks!
-Luke
On Apr 6, 8:43 pm, Eric Thorsen ethor...@enclojure.org wrote:
There is a new
To me, major version numbers means no more nor less than a marker
pointing to a stable, consistent release that can be easily referred
to consistently by everyone. It doesn't mean that there can't be
major, breaking changes for 2.0 (or even 1.5, whatever). I don't even
care what features are in
My .02 on the version control issue:
All of them work. Some are easier to use than others. There are
successful projects that use just about all of them. It's personal
preference. Rich is going to be doing most the contributing, let him
choose the VCS.
Period.
On Apr 17, 4:29 pm, Laurent
Cool... I actually did a Markov chain generator myself as one of my
early Clojure projects. I posted about it at the DC Study group, here:
http://groups.google.com/group/clojure-study-dc/browse_thread/thread/26ccdc8acb102f9/d18d7627ddcaf167
It looks like yours is more succinct... I'll
First of all, this is a very interesting question. I definitely wish I
had more time to think about it and maybe put together some code -
unfortunately I don't.
Clojure does sound like it would be good for this kind of processing.
This is an ideal example of where it would be incredibly powerful
On May 6, 4:39 am, dhs827 scheur...@gmail.com wrote:
I realize now that there is no quick fix, and I'll have to learn a
lot to do this properly. But are there already enough resources so
that I can learn how to do it in Clojure? For example, would there be
enough about string processing in
; First thing to learn is XML parsing with Clojure.
This is basically done. Use the xml library in core if you just need
to load XML into a map data structure. Use the zip library if you need
to navigate it. Use the xml library in contrib if you need to do xpath-
style navigation.
For the rest
Do you mean map the function or map the data structure?
If the most natural form of your data is truly rows, you're probably
best off using a vector data structure. As for which function you use,
that depends whether you're doing something to every element or only
to specific elements, and if
Wow. I have seriously done most of these.
Leaving out return statements in javascript is the most insidious,
however, particularly since my JS coding style has become extremely
functional since learning Clojure.
-Luke
On Jun 12, 9:55 am, Luc Prefontaine lprefonta...@softaddicts.ca
wrote:
You
Lowman ( michellelow...@apress.com ) so we can talk
about it.
Thanks very much for considering this.
Sincerely,
-Luke VanderHart
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group
Why not just run an agent that does something, then calls sleep for N
seconds, then calls the next thing?
Granted, it will eat up a thread in your agent thread pool, but if
you've only got one of these in the app it shouldn't be a problem.
Or you could go the Java route, and start a daemon
Wouldn't hashCode be called every time you use an infinite sequence as
a key in a hash map?
That strikes me as a problem, since everything else in Clojure makes
perfectly good map keys.
On Oct 29, 4:01 am, Mark Engelberg mark.engelb...@gmail.com wrote:
On Wed, Oct 28, 2009 at 11:08 PM, John
Very cool.
The website doesn't say... how was/is the Clojure/core team selected?
Are they all Relevance employees, or freelance? Do you plan on ever
bringing more people on board? Although I'm not quite as qualified as
some of the others, that's something I'd potentially be very
interested in,
Clojure is not a great choice for this. It's oriented as a programming
language, not a database. It doesn't have any built-in persistence
mechanisms, and while it has many virtues, it's a little bit of a
memory hog. That isn't really what you want in an in-memory DB.
For anything more than a toy
My side project is a fairly complex GUI application written in
Clojure. Recently, I've become irritated with using Java interop for
everything. It's not that Clojure doesn't have nice java interop - it
does. It's just that when interacting with a GUI framework, which is a
large part of my app, I
Thanks, Heinz... I may.
Right now I'm still exploring what I want the API to be. I was hoping
to achieve something a bit thicker that could insulate the user from
Java classes completely. The user wouldn't even have to know Swing or
handle JObjects or worry about the event thread... In other
Why not design it so that it can be backed by Swing or SWT or HTML
(perhaps with some AJAX) or whatever? It seems kind of silly to do an
abstraction on a single backend, don't you think?
Ideally, yes. In practice, I'd rather implement one framework well
than implement only the lowest common
JavaFx. Is it because
it's new?
On May 27, 11:18 am, Luke VanderHart luke.vanderh...@gmail.com
wrote:
My side project is a fairly complex GUI application written in
Clojure. Recently, I've become irritated with using Java interop for
everything. It's not that Clojure doesn't have nice java
I would love to see an idiomatic clojure QtJambi wrapper that solves
the writing custom widgets is hairy problem.
I think QT Jambi's basic architecture precludes this. Jambi is
basically a bunch of JNI calls to a backend C++ QT app. As soon as you
start delving into Jambi's internals, you end
I can't see your code due to the IT policies here, but I can make some
generalizations - these are assuming your code is correct and you're
not accidentally using an exponential algorithm (which I wouldn't
preclude, 4 minutes does sound truly excessively slow, even for
vectors).
Vectors are
feel the project has a clear direction and a little
momentum, I'd definitely like some others on board.
Again, thanks to everyone for your input.
-Luke
On May 27, 11:18 am, Luke VanderHart luke.vanderh...@gmail.com
wrote:
My side project is a fairly complex GUI application written in
Clojure
Tiobes rankings always seems a little dubious to me.
Delphi more popular than Javascript? Really? Google Go more popular
than Lisp/Scheme/Clojure?
Ranking those three together is an atrocity, by the way. Just because
they all have paren's doesn't make them the same.
Anyway, I'm sure Tiobe
I've been reading this thread, and there's good arguments being made
both ways - I've just been reading with interest. But after seeing the
factorial function that won't compile without hints/casts, I feel I
have to speak up.
I wrote a book on Clojure. It's a short book. That's because Clojure
is
As Rich has mentioned a couple times, though, let's be careful not to
conflate bounded integers with unsafe integers. In the proposed
system, an overflowing number would throw an exception. Presumably the
documentation would make it very clear what the behavior of numbers
is. That's not unsafe or
I've been working on a simple Clojure library for bounded caching and
memoization. It's not quite ready for prime-time, but the simple case
that you need is usable.
I'll throw it up on github when I get home tonight and post the URL
here.
On Dec 30, 1:35 pm, Miki miki.teb...@gmail.com wrote:
For what it's worth, I am really glad of the position Rich is taking
on a roadmap and Clojure's future development. I would much rather
Clojure remained fresh, innovative and agile, and that it continues to
offer unexpected, delightful new features and abilities. It can't
really do that if Rich
Some of you may already be aware of of Domina, a jQuery-inspired DOM
manipulation library I've been working on. It's been out there for a while,
but I just finished up a round of changes that I think bring it to a
certain degree of completion for basic use (although there's definitely a
lot of
Using a map instead of if means that it is evaluated as a function call.
Unlike the if form, function calls eval their arguments. So the (recur)
form is getting eval'd prior to being passed to the map/function, which
isn't a tail position.
That's why if is a special form/macro, not a regular
, Luke VanderHart wrote:
Some of you may already be aware of of Domina, a jQuery-inspired DOM
manipulation library I've been working on. It's been out there for a while,
but I just finished up a round of changes that I think bring it to a
certain degree of completion for basic use (although
master?
David
On Sat, Apr 28, 2012 at 1:19 PM, Luke VanderHart
luke.vanderh...@gmail.com wrote:
David,
Yes. I've been looking at that today. Something is going on that is not
so straightforward, though - I think there might be a compiler issue (or
else I'm misunderstanding some aspect
This is a hard problem.
If you go by degrees and shades of synonymity, it can (and has been)
done manually - see Visual Thesaurus (http://
www.visualthesaurus.com/).
But for grouping based on the same semantic topics - that's pretty
difficult. You could do it based on co-location in a corpus,
For the past week or two, I've been investigating what it would take
to write something that would allow *.clj and *.java files to
seamlessly compile together, such that they could be freely intermixed
in a project. I knew it was a difficult problem, but I think the
adoption benefits would be
My apologies, the title got cut off. It should be:
Is it possible in theory to write/modify a Clojure compiler that
doesn't resolve Java references?
On Aug 28, 12:50 pm, Luke VanderHart luke.vanderh...@gmail.com
wrote:
For the past week or two, I've been investigating what it would take
I'm not just talking about class hierarchy dependencies, but also
reference dependencies.
For example:
Foo.java
class Foo {
public Bar getBar() {...}
}
Bar.java
class Bar{
public Foo getFoo() {...}
}
This is pretty common in the Java world.
What I'd like to do is have Foo be written in
possibly be a candidate for
inclusion into the main Clojure compiler?
On Aug 28, 7:02 pm, Seth seth.schroe...@gmail.com wrote:
This sounds very similar to
groovyc:http://groovyland.wordpress.com/2009/03/03/groovyscalajava/
On Aug 28, 12:50 pm, Luke VanderHart luke.vanderh...@gmail.com
wrote
Robert,
The only problem with this approach is that there ARE practically
guaranteed to be circular references. If the goal is to compile
Clojure as if it were Java, circular references must be accounted
for.
But dependencies on classes generated based on parsing bytecode...
that seems a pretty
The ability to use macros to do code generation and transformation is
extremely useful. However, you still have to explicitly call the
macro everywhere you want it to be used. In many scenarios, it might
be desirable to do code transformation/generation on code, without
explicitly modifying that
Unless I misunderstand something, (binding...) wouldn't work for this
because I'd have to wrap all of the code I wanted to be modified
within a (binding...) form. Fine if it's one source file, not so fine
if I have dozens... Or am I missing something?
On Sep 15, 2:26 pm, Nicolas Oury
expires will be affected by the new
bindings, not just the code explicitly within its lexical scope.
On Sep 15, 11:35 am, Luke VanderHart luke.vanderh...@gmail.com
wrote:
Unless I misunderstand something, (binding...) wouldn't work for this
because I'd have to wrap all of the code I wanted
fanvie, two comments:
1. It will get better over time, of course, as standard practices for
Clojure shake out.
2. You don't need 99% of the special crap that Spring/Grails gives
you. Clojure's abstractions are smaller, yes, but the're just as
powerful, and give you more control, in a more
:
On Tue, Nov 2, 2010 at 12:49 PM, Luke VanderHart
luke.vanderh...@gmail.com wrote:
fanvie, two comments:
2. You don't need 99% of the special crap that Spring/Grails gives
you. Clojure's abstractions are smaller, yes, but the're just as
powerful, and give you more control, in a more
, is it? Development platforms are
not a zero-sum game. Just because I work on/prefer a Clojure framework
to a Ruby one doesn't mean I'm trying to insult or belittle Rails.
On Nov 3, 1:43 pm, Sean Corfield seancorfi...@gmail.com wrote:
On Wed, Nov 3, 2010 at 8:51 AM, Luke VanderHart
luke.vanderh...@gmail.com
Lau,
This is really impressive, and I can't wait to experiment with it.
That said, I'm curious as to what good use cases for this would be,
and what it's motivation is. SQL is already a highly specialized DSL
for slinging around relational data that most developers are already
pretty good with.
developers do it)
in Clojure, which is guaranteed to compile to correct SQL.
Answers your question?
Lau
On Nov 24, 1:56 am, Luke VanderHart luke.vanderh...@gmail.com wrote:
Lau,
This is really impressive, and I can't wait to experiment with it.
That said, I'm curious as to what good use
In case anyone is interested in venturing beyond the bleeding edge and
trying out the current state of feature expressions, I have created forks
of the relevant repositories with the patches applied, and put together a
minimal hello-world repository.
https://github.com/levand/fx-hello-world
Just realized I forgot to post about this here, which is kind of important.
:)
It is still under development - I am raising funds via Kickstarter in order
to get the opportunity to work on it full time and make sure it gets off to
a really solid start.
It's a pretty ambitious project, but
t there is no similar delay.
>
> Thanks,
> -Eli
>
>
> On Fri, Feb 16, 2018, at 9:47 AM, Luke VanderHart wrote:
>
> The goal is to have a full featured, standardized test runner on a project
> using basic Clojure Deps, without needing to introduce Boot or Leiningen
> j
The goal is to have a full featured, standardized test runner on a project
using basic Clojure Deps, without needing to introduce Boot or Leiningen
just for that.
https://github.com/cognitect-labs/test-runner
Feedback, bugfixes and PRs welcome.
--
You received this message because you are
54 matches
Mail list logo
