Re: Scala/Clojure/F# - Functional Programming Advocates - New York/Chicago/San Fran

Just this afternoon I was looking at the HN Who's Hiring thread for February. 621 comments there, mostly job postings with the occasional question comment, so perhaps 500-550 actual postings. 15 postings mention Clojure, with 9 being what looks like a

Re: Scala/Clojure/F# - Functional Programming Advocates - New York/Chicago/San Fran

Alex I was looking at Indeed.com for U.S. FP job stats and I found for "United States" by title: Java: 12,125 Scala: 336 Clojure: 28 Considering Clojure 1.0 has been around for nearly 7 years and Scala 2.0 is almost a decade old is it fair to conclude that FP and Clojure in particular are l

Re: Scala for-comprehension to Clojure

Most Scala `for` examples translate over to Clojure's `for`. The biggest difference is that Scala produces a collection matching the type of the first generator, whereas Clojure produces a lazy sequence, which you can "pour" into the collection of your choice with `into`. It looks like your speci

Re: Scala for-comprehension to Clojure

Hi, I am not sure if it will serve point the best but that is what I have received as a koan style problem with Scala solution, now I am trying to comprehend it fully and convert to Clojure. Like I said I am by no means Scala expert. Let's say we have some Val container which is capable to hold

Re: Scala for-comprehension to Clojure

It is the same thing in Clojure. It is called a 'list comprehension' even although for form for it starts with `for` I wouldn't worry too much about the flatmap / mapcat stuff, as I think the translation should be quite direct at the higher 'comprehension' level. On Nov 26, 2015 10:12 PM, "Rastko

Re: Scala for-comprehension to Clojure

It's a bit hard (at least for me) to see what you're actually trying to do here that would precent a direct translation of your snippet to Clojure's for. Could you perhaps post a complete, self-contained code example in Scala? On Thursday, 26 November 2015, Torsten Uhlmann wrote: > Hi Rastko, >

Re: Scala for-comprehension to Clojure

Hi Rastko, One way of doing that would be to use the mlet macro from the Cats library: http://funcool.github.io/cats/latest/#mlet Also, there are several if-lets or when-lets out there that allow multiple bindings, I used one from https://github.com/ptaoussanis/encore I use Scala's for most of

Re: Scala interop (or, aliasing imported Java classes)

That would need quoting wouldn't it? (import '(the.java.package {Clazz1 Alias1 Clazz2 Alias2} Clazz3)) or: (import '(the.java.package Clazz1 Clazz2 Clazz3 :rename {Clazz1 Alias1 Clazz2 Alias2})) On Sun, Nov 3, 2013 at 11:22 AM, Sean Corfield wrote: > Perhaps a small extension to (impor

Re: Scala interop (or, aliasing imported Java classes)

Perhaps a small extension to (import ..) is warranted then, since the underlying machinery seems to support aliases? (import [the.java.package {Clazz1 Alias1 Clazz2 Alias2} Clazz3]) or, maybe more in keeping with require: (import [the.java.package Clazz1 Clazz2 Clazz3 :rename {Clazz1 Ali

Re: Scala interop (or, aliasing imported Java classes)

Mark writes: > I think my preferred solution would be to allow imported Java classes > to be aliased, so I could do this: > >> (import '(org.fooinstitute.team.library.foo package :as foop)) > => org.fooinstitute.team.library.foo.package >> (foop/isFoo "foop") > => false > > But to the best of my

Re: Scala interop (or, aliasing imported Java classes)

I ran into this problem using inner-class enums and wound up writing a macro to generate aliases for me. You could do something similar: (defmacro def-class-alias "Make name reference class (def-class-alias class-name foo.bar.baz.SomeClass) (class-name foo) -> foo.bar.baz.SomeClass/foo

Re: Scala interop (or, aliasing imported Java classes)

+1 On Fri, Nov 1, 2013 at 6:49 PM, Cedric Greevey wrote: > I vote for adding :as to import. I've personally thought of other > situations where this could be useful. > > Being able to alias a (Java) package might be useful too: > > (import '((java.util.concurrent :as juc) LinkedBlockingQueue >

Re: Scala interop (or, aliasing imported Java classes)

I vote for adding :as to import. I've personally thought of other situations where this could be useful. Being able to alias a (Java) package might be useful too: (import '((java.util.concurrent :as juc) LinkedBlockingQueue ReadWriteLock)) (def my-queue (juc/LinkedBlockingQueue.)) Most useful w

Re: scala

On Jun 18, 11:56 pm, cageface wrote: > > Unfortunately there seems to be a lot more commercial momentum for > Scala though. It's still a blip compared to the mainstream languages > but I'm seeing more and more job posts mentioning it, and hardly any > for Clojure. I don't think Scala is a bad lang

Re: scala

For such a young language it has a big momentum. Did Scala have that after 2 years? On 18 Jun., 23:56, cageface wrote: > Quick disclaimer - there are a lot of things I like in Scala and I > think Odersky & crew have done some very impressive work bringing > functional language concepts to the VM

Re: scala

Bear in mind that Scala is about 5 years older than Clojure, so it's had more time to build up momentum. On Jun 18, 5:56 pm, cageface wrote: > Unfortunately there seems to be a lot more commercial momentum for > Scala though. It's still a blip compared to the mainstream languages > but I'm seein

Re: scala

I've spent a number of years looking for a functional programming language suitable for the kind of work I do. evaluating Clojure, Haskell, Erlang, Scala, F#, Mozart, ML, Clean, Racket, and probably some others I'm not thinking about right now. For me, once Clojure hit 1.0 status, it was clearly

Re: Scala vs Clojure

On 01/04/2009, at 1:26 PM, Rayne wrote: > > Unless they slowed down, the pace in which Enclojure was improving > would put me dead on. Neither the site nor the mailing list shows a lot of activity - it's not dead, but it is taking a long time compared to the IntelliJ support, which was my p

Re: Scala vs Clojure

Unless they slowed down, the pace in which Enclojure was improving would put me dead on. I personally use IntelliJ IDEA. But who says I paid for it? On Mar 31, 5:45 pm, Antony Blakey wrote: > On 28/03/2009, at 5:21 PM, Rayne wrote: > > > I'd say Enclojure is close to > > production-ready. > >  F

Re: Scala vs Clojure

just wanted to know because it didn't sound like it from the comparison being made. On Tue, Mar 31, 2009 at 8:34 PM, Antony Blakey wrote: > > > On 01/04/2009, at 10:01 AM, e wrote: > > > but the InteliJ IDE isn't free, is it? > > So what? I'm a professional developer. I make money using these too

Re: Scala vs Clojure

On 01/04/2009, at 10:01 AM, e wrote: > but the InteliJ IDE isn't free, is it? So what? I'm a professional developer. I make money using these tools. The money people pay for IntelliJ is one reason that the Scala support in IntelliJ is more ambitious and why the IntelliJ Clojure plugin is

Re: Scala vs Clojure

but the InteliJ IDE isn't free, is it? On Tue, Mar 31, 2009 at 6:45 PM, Antony Blakey wrote: > > > On 28/03/2009, at 5:21 PM, Rayne wrote: > > > I'd say Enclojure is close to > > production-ready. > > From my playing with it, plus the list of things not yet done, I > don't think this is true. Th

Re: Scala vs Clojure

On 28/03/2009, at 5:21 PM, Rayne wrote: > I'd say Enclojure is close to > production-ready. From my playing with it, plus the list of things not yet done, I don't think this is true. The IntelliJ clojure support seems more advanced right now, and I'm starting to use that in production. IMO

Re: Scala vs Clojure

On Mar 31, 4:52 pm, Luc Prefontaine wrote: > I was searching for a Java alternative for our medical bus product and > looked at Scala during summer 2008. > I found it was too tied to an object model. The lack of a complete macro > system was in my view also a short coming. > > I concluded that

Re: Scala vs Clojure

I was searching for a Java alternative for our medical bus product and looked at Scala during summer 2008. I found it was too tied to an object model. The lack of a complete macro system was in my view also a short coming. I concluded that it was not a significant departure from Java. I really wan

Re: Scala vs Clojure

On Tue, Mar 31, 2009 at 5:20 PM, Chas Emerick wrote: > > We shipped production software built in Scala last year, but likely > will never do so again given clojure.  Our primary motivating factor > is the degree of complexity in the Scala, but since you're looking for > "auxiliary" factors: > > -

Re: Scala vs Clojure

We shipped production software built in Scala last year, but likely will never do so again given clojure. Our primary motivating factor is the degree of complexity in the Scala, but since you're looking for "auxiliary" factors: - clojure has a far richer "ecosystem" -- there's a metric ton

Re: Scala vs Clojure

I sure hope this topic doesn't start a flamewar. I've used both languages, with Clojure being used more. Scala is more mature than Clojure, so you really have to put that in perspective when comparing the languages. Scala's IDE support is superior to Clojure's but not for long as all three major