How to write Common Lisp in 2017 – an initiation manual

Re:How to write Common Lisp in 2017 – an initiation manual by kahrkunne on Tuesday March 28, 2017 @06:11PM (#13981229)

Honestly I don't think Emacs is an obstacle to people who use Vim. It's an obstacle to people who use IDEs

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by aidenn0 on Wednesday March 29, 2017 @10:27AM (#13986499)

IMO, It's an obstacle only to people who don't use IDEs.

Someone who uses e.g. visual studio for C++ isn't going to balk at the suggestion of installing IntelliJ for Java, and I doubt that they would balk at the suggestion of installing SLIME for lisp.

In my experience it's people who live in their editor (sublime, vim, &c.) that balk at the idea of installing an IDE as the first step for using a new language.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by ruleabidinguser on Tuesday March 28, 2017 @11:46PM (#13983217)

I use(d) vim and see EMacs as annoying.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by cat199 on Wednesday March 29, 2017 @12:10PM (#13987640)

I use vi and emacs and see vim as some odd vi that is trying to be emacs but ends up being neither.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by kahrkunne on Thursday March 30, 2017 @12:30PM (#13996798)

It might be annoying but it probably wouldn't be an "obstacle", especially considering things like evil-mode exist.

That's how it went for me, anyways. From vim user to trying Emacs because it has some feature that I need to becoming a full-time Emacs users with evil-mode

[ Parent | on HN ]