[spv]

I cannot believe that you make more from such a niche dev tool than your job at Google. I always thought people who use clojure/scheme would be using their custom setup in emacs or vim.

I'm interested to learn more details, how things were when you first started out selling the app and the trend.

[Crinus]

You say that but one thing that i always dislike when i consider taking a look at Lisps is how everything seems to be either on Emacs or looks like it'd really like to be Emacs.

Personally I want a full blown IDE that takes advantage of advanced modern technologies such as displays that can draw individual pixels, have a model of the codebase that allows advanced features such as word completion and preferably fits nicely with the underlying OS. A debugger would also be nice, but i understand that sometimes i ask too much.

I wouldn't mind paying for such a tool (though i do mind DRM schemes and subscriptions - i want to be able to pay once and then be on my way). Cursive looks something i'd pay for if i was really interested into Clojure and was using macOS.

[brokenkebab]

Actually, there's completion, and excellent debugging tools for Clojure in Emacs, both step-by-step kind, and investigative. "I don't want to use Emacs" is a completely valid stance (de gustibus...), but it should not be misinformed.

[Crinus]

I know that Emacs has good support for Lisps in general, my comment was a joke towards what i consider basic features of an IDE (the whole 'modern' and 'advanced' thing when referring to stuff that were available in the late 80s should have made it obvious :-P). It comes mainly from my observation of the trend where a lot of developers like to jury rig "IDEs" out of text editors and a bunch of other unrelated tools that look as if they are made to be run in 70s terminals that look and feel considerably worse that MS-DOS applications which had 1/100000th of the available resources.

[jcadam]

> Cursive looks something i'd pay for if i was really interested into Clojure and was using macOS.

um... it runs on Linux and Windows as well.

[Crinus]

Ah, somehow i missed that it is build on IntelliJ. I thought it was a native macOS application.

[wry_discontent]

FWIW I've found Clojure has pretty decent support in a few editors. I know Cursive is quite popular, but I've also used both VS Code and Atom to some extent, and they have nice features.

Somebody else could probably speak more to it than me, since I do primarily use Emacs, but I definitely don't introduce my friends to Clojure with it.

[krn]

> I cannot believe that you make more from such a niche dev tool than your job at Google.

It's important to note, that there are markets where Google pays 70-90k / year[1].

[1] https://www.glassdoor.com/Salary/Google-Berlin-Salaries-EI_I...

[lemming]

I'm not talking about those markets - this was after an acquisition and I was supposed to move to either SV or NYC. In the end I didn't want to work at Google or move to the US so it was pretty brief.

Thinking about it, I'm not sure Cursive pays more than my total comp at Google, but certainly more than salary + bonus.

[eafkuor]

There are markets where it pays less - see Warsaw.

[lemming]

I wrote a little bit about this below (https://news.ycombinator.com/item?id=21337892), but I think that a lot of that perception is because lisps (with the exception of CL) have traditionally been things that people tinker with as a hobby. Once you get a significant number of people making a living working with a language, suddenly a lot of people want barriers to getting their work done removed. And Emacs, for all its benefits, can be a significant barrier to getting work done for a lot of people. Plus there are those of us who just think that life is too short :-)

[jcadam]

As a Clojure (and Java) dev, I started with Cursive and eventually moved to emacs w/CIDER as I became more comfortable with it. Cursive is great for people new to the language who may not know emacs - learning a new language is challenging enough without also having to constantly refer to an emacs cheat sheet :).

[lemming]

FWIW Cursive is also great for people who have a lot of experience with Emacs and just can't be bothered with it. Popular examples include David Nolen and Timothy Baldridge (and me), but there are plenty more too.

One representative comment that someone made to me at a conference was along the lines of "Since my boss encouraged us to move to Emacs, I've never spent so long fiddling with and arguing about my editor config. After a while most of us moved to Cursive and all that just went away".

I think Emacs is generally easier to get along with these days, but it'll never be as easy to use as a "normal" app where things just work out of the box. Some people like that, and others don't, but it's not as simple as a division between newbies and experienced users. They're roughly equivalent in power these days, some things Emacs does better and others Cursive does better - fortunately there's plenty of room for both, even in a userbase as small as Clojure's.

[jimmyvalmer]

I think if stackoverflow conducted their survey on HN readers alone, the editor-used distribution would be very different.

[cmancini]

A lot of people use Emacs, but I remember as Cursive took off in the Clojure community. It's so wonderful being able to work on a large JVM app that includes Scala and Java in IntelliJ and have first class Clojure features. Cursive is phenomenal, and because it's (or was at the time) the only choice, I would gladly fork over 2x the cost out of my own pocket (though my company would let me expense). It was great too to go to Conj and major Clojure conferences and hear Colin announce new features and talk about the roadmap.

[jetti]

My team is mixed. We have two devs using Cursive, one using Atom, one using vim and then two using emacs. The two devs using Cursive love IntelliJ and being able to work in IntelliJ and do Clojure development is a big win for them

[kimi]

They (we) used to, but with Cursive.... welcome to the XXI century :)