3 ms·
Even if it had an intelliJ IDE it wont be used. The barrier to entry is not the IDE, its that Lisp is not fashionable at the moment. Those who know how to use
by worthless-trash 3y ago
Even if it had an intelliJ IDE it wont be used.
The barrier to entry is not the IDE, its that Lisp is not fashionable at the moment. Those who know how to use it, put their head down and do the work, those who dont will follow the next fashionable trend for their work that they see their employment needing.
- deleted 3y ago[deleted]
- admax88qqq 3y agoThere are developers out there who don't just jump on the next fashionable trend but who still want a better out of box experience than "you want to learn Lisp? Cool also learn emacs and about all these different lisp distros" Common Lisp will probably never be the next Python, but it might be the next Ruby.
- bitwize 3y ago3/4 of devs use Visual Studio Code. A significant portion of the remainder use full-fat Visual Studio or an IntelliJ product. The number of new Lisp users in 2023 is pretty small, sure. But it's frickin' 2023, those users need a better onboarding experience than having to futz with Emacs, even given something like Portacle. They will be familiar with VSCode or one of the above IDEs, not Emacs, and they shouldn't have to entirely relearn how to write code.
- gumby 3y agoYou can use lisp with vi or any other editor you like.
- dustfinger 3y ago>But it's frickin' 2023, those users need a better onboarding experience than having to futz with Emacs Funny, the years spent onboarding Emacs, and GNU/Linux for that matter, was the experience I was looking for.I never wanted to be just another cog in a well lubed task grinding machine. >they shouldn't have to entirely relearn how to write code If you are referring to elisp, it really isn't a mountain to climb or anything like that. Besides, only very basic lisp knowledge is required to customize Emacs, after that you can code your day away in a lisp of your choosing. If you are looking for a more modern experience with emacs try elgot + tree-sitter [1] [1]: https://www.adventuresinwhy.com/post/eglot/ https://www.adventuresinwhy.com/post/eglot/