Hi,
I love ClojureScript and routinely recommend it to people in the
supermarket. With that said, in the context of a backend service these are
some of the things that I would miss from Clojure:
1. Rock solid dependencies for doing all the operations you describe. I've
found the JVM ecosystem
Hi everybody!
I'm working on showing dependency graphs from github urls. If you have a
Clojure project with a project.clj file in it or a ClojureScript project
with :cljsbuild in it, it *should* work. You can the demo at:
http://asterion-dev.elasticbeanstalk.com/index.html
some cool projects t
be
> implemented is spot-on. I have done this exercise and thought about
> possible implementations. For me a r*easonable implementation* is one
> that has good interoperability capabilities and doesn't add too much
> overhead because of Clojure language constructs, which is quite a
Hi Frank,
I've been thinking about this for some months now. The actor model is a
great fit for a number of applications and the BEAM is made for it.Though
it seems feasible, I'm afraid the result might not feel so close to
Clojure, at least with any reasonable performance. I hope I'm wrong. I
> Data as Data makes Clojure *simple*.
> Immutability makes Clojure programs *easy to reason about*."
>
> Oooh, looking at that list, I wonder if one about laziness is missing...
>
> -- John
>
>
>
> On Thursday, August 13, 2015 at 3:45:23 AM UTC-4, Sebastian
ity can be memory efficient.
>
> The current immutability/concurrency paragraph reads to me like
> concurrency is the main point of immutability, where in my experience it's
> just one useful consequence.
>
> On 13 August 2015 at 08:44, Sebastian Bensusan wrote:
>
>>
cies?" Wouldn't many
> dependencies be a bad thing? If the question (and expected answer) are
> correct, can you go into a bit more detail on why having many dependencies
> is a positive quality?
>
>
> On Wednesday, August 12, 2015 at 11:52:39 AM UTC-7, Sebastian Bensusan
>
> On 12. aug. 2015, at 20.52, Sebastian Bensusan wrote:
> >
> > Hi everybody!
> >
> > I've written a short post on my interpretation of Clojure. It is meant
> for people that are curious about the language and want to understand what
> the language is about.
> >
Hi everybody!
I've written a short post on my interpretation of Clojure. It is meant for
people that are curious about the language and want to understand what the
language is about.
http://bensu.github.io/decomplecting_clojure/
Any feedback is welcome.
Thanks to the folks at Slack that read
Hi Simon,
Not exactly what you are asking, but a guide to Using cljc might be helpful:
https://github.com/clojure/clojurescript/wiki/Using-cljc
Hope this helps,
Sebastian
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send
Hi Nathan,
I've been developing a small library to do exactly
that: https://github.com/bensu/doo
It's still alpha and doesn't support all Js targets but it will get there
:) I haven't tried test.check for clojurescript yet, but if you run into
trouble please post an issue since it should work
I stand corrected. I guess I believed Hal Abelson when he used
"Scheme"/"Lisp" interchangeably.
On Tuesday, April 14, 2015 at 2:39:32 AM UTC+2, Alexis wrote:
>
>
> Sebastian Bensusan > writes:
>
> > As a side notes, in Lisp it is convention to append &
ps://github.com/AndreaCrotti/hackthetower_clojurescript/blob/master/hangman/test/hangman/secret_test.clj
>
>
> 2015-04-11 10:02 GMT+01:00 Sebastian Bensusan >:
> > Hi,
> >
> > I browsed over it, a couple of things:
> >
> > `defonce` is meant for code relo
Hi,
I browsed over it, a couple of things:
`defonce` is meant for code reloading:
(defonce live-games (ref {})))
Don't use `for` when you can use `map`:
(mapv (fn [i] {:char i :visible (not (valid-char i))}))
Strings can be treated as sequences:
(first (.toLowerCase (str char)))
Hope this h
Hi Daniel,
I believe the point of the analogy is that "tests can't do the thinking for
you". In that sense, a strict TDD workflow where you think only about the
very next test might be undesirable. In case you didn't read it, this
article explains it much
better: http://patrick.lioi.net/2011/1
Can you post your project.clj and your folder structure? You might have
your `:http-server-root` pointing to the wrong place. To see a working
configuration try `lein new fighweel your-project-name` and you'll get a
template with figwheel ready to go.
On Saturday, March 7, 2015 at 11:47:19 PM U
ary 2015 at 12:55, Khalid Jebbari > wrote:
>
>> Indeed, "data" is better than "app".
>>
>> Khalid aka DjebbZ
>> @Dj3bbZ
>>
>> On Mon, Feb 2, 2015 at 10:49 AM, Sebastian Bensusan > > wrote:
>>
>>> Thanks Khalid,
>&
Hi Elric,
The JVM can't use file directories that include hyphen -
All paths are converted to _
http://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html
http://clojure.org/libs
Sebastian
On Monday, February 2, 2015 at 7:04:06 PM UTC+1, Elric Erkose wrote:
>
> What is the reason th
Thanks Khalid,
The way I see it, Om has three concepts regarding state:
1. The global state defined with atom. Named `app-state`
2. The cursor passed to each component with the relevant parts of the
global state. Named `app`
3. Local state of each component, initialized in `IInitState` and
mani
Saturday, January 31, 2015, Sebastian Bensusan > wrote:
>
>> Sure, I'll explore Figwheel's new REPL and add that instead.
>>
>> What about adding/configuring Figwheel? Should it be step by step inside
>> the tutorial, from mies-om to mies-om + Figwheel? Or
Sure, I'll explore Figwheel's new REPL and add that instead.
What about adding/configuring Figwheel? Should it be step by step inside the
tutorial, from mies-om to mies-om + Figwheel? Or it should just start with a
ready to go template "mies-om-wheel"?
Thanks
Sebastian B
torial to the Om Wiki. Otherwise, if you feel the extra
dependency on Chestnut is also too much, I'll fork mies-om and add Figwheel
there for the tutorial.
After revising this work, I'll move on to the next tutorial.
Best
Sebastian Bensusan
On Tuesday, January 27, 2015 at 5:25:09
t;
> El martes, 16 de diciembre de 2014 10:11:11 UTC, Sebastian Bensusan
> escribió:
>>
>> Hola Juan,
>>
>> I am using sutartsierra/component and from the README I see cylon offers
>> what I want: both client and provider. Thanks a lot for the suggestion. I
&
domingo, 14 de diciembre de 2014 18:08:58 UTC, Sebastian Bensusan
> escribió:
>>
>> Hi,
>>
>> I am writing a Single Page Application using Om that communicates via XHR
>> with a REST API using compojure + liberator. I should be able to
>> authenticate users by usin
Thanks Sam.
The gist is very helpful (as well as the Friend + Liberator post). I see
you are generating and maintaining your own tokens (" exchange for
long-lived token").
Did you write custom code for this or is there some library I should look
at?
Sebastian
--
You received this message
e?), what purpose does a Friend workflow have in
> this context? Seems like you could skip Friend altogether.
>
> DD
>
> (2014/12/15 17:40), Sebastian Bensusan wrote:
> > Hi Dave,
> >
> > I am planning to use friend-oauth2 to handle "third party work
k for you for some reason I'd like
> to know why, as I'd like it to be able to handle this use-case.
>
> https://github.com/ddellacosta/friend-oauth2
>
> Thanks!
>
> DD
>
> (2014/12/15 3:08), Sebastian Bensusan wrote:
> > Hi,
> >
> > I am
Hi,
I am writing a Single Page Application using Om that communicates via XHR
with a REST API using compojure + liberator. I should be able to
authenticate users by using email & password credentials or third party
Oauth2 like Linkedin's. I
My plan is: use clauth [1] to roll my own oauth2, pac
28 matches
Mail list logo
