10 ms·

As far as I know activestate has a TCL IDE. But I think like lisp, an IDE is a foreign concept in coding TCL. TCL is a different beast, it cannot be represent

As far as I know activestate has a TCL IDE. But I think like lisp, an IDE is a foreign concept in coding TCL. TCL is a different beast, it cannot be represented with an EBNF, you can redefine anything including language keywords etc. TCL is thus closer to a human language (much more expressive) so making an IDE to accomodate features of TCL could be harder than conventional languages.

aidenn0 6y ago
"like lisp"? The high quality free IDE (SLIME) is a big part of why I still use common lisp.
- terminalcommand 6y ago
  I wouldn’t call slime an IDE, lisp compiler isn’t even included in it. Slime is a wonderful editor mode. You still need to configure things to get it working. With an IDE, I think of something like Xcode or VS.
  - aidenn0 6y ago
    I think anything that Integrates the tools used for your Development Environment is an IDE. SLIME integrates a compiler, debugger, code browser, documentation, and editor. If it's not an IDE than nothing is (and there are no Java IDEs either then because they almost always use an external compiler and runtime).
    - terminalcommand 6y ago
      The line between IDEs and editors get blurry every day :). You’re right java IDEs sometimes don’t include java sdk in the base package. I’ve recently been fiddling with ios development, when thinking of an IDE, I think of xcode, visual studio etc. Lots of defaults and magic. Slime might very well be considered an IDE, an IDE for power users :) who likely have learned at least some emacs lisp to get it working.
      - aidenn0 6y ago
        FWIW, when I first started using SLIME, I used it just as a debugger and REPL. I wrote all of my lisp code in vim and used slime for debugging it. I knew zero elisp and zero emacs shortcuts; I used the menu interface for all but a few commands. The first (and only for about 3 years) elisp I wrote was a command to open up the current file in vim, and reload it when vim exited. This let me browse & debug source with emacs while editing with vim. SLIME offered so many features that this was an actually useful workflow, and I didn't switch to using emacs for editing as well until much later, when evil-mode came out. side-note: I had tried other vi-like modes prior to evil-mode coming out (e.g. viper), but they fell in an uncanny valley for me; just familiar enough that I would regularly muscle-memory some sequence that didn't work in viper.

aidenn0 6y ago

"like lisp"? The high quality free IDE (SLIME) is a big part of why I still use common lisp.

terminalcommand 6y ago
I wouldn’t call slime an IDE, lisp compiler isn’t even included in it. Slime is a wonderful editor mode. You still need to configure things to get it working. With an IDE, I think of something like Xcode or VS.
- aidenn0 6y ago
  I think anything that Integrates the tools used for your Development Environment is an IDE. SLIME integrates a compiler, debugger, code browser, documentation, and editor. If it's not an IDE than nothing is (and there are no Java IDEs either then because they almost always use an external compiler and runtime).
  - terminalcommand 6y ago
    The line between IDEs and editors get blurry every day :). You’re right java IDEs sometimes don’t include java sdk in the base package. I’ve recently been fiddling with ios development, when thinking of an IDE, I think of xcode, visual studio etc. Lots of defaults and magic. Slime might very well be considered an IDE, an IDE for power users :) who likely have learned at least some emacs lisp to get it working.
    - aidenn0 6y ago
      FWIW, when I first started using SLIME, I used it just as a debugger and REPL. I wrote all of my lisp code in vim and used slime for debugging it. I knew zero elisp and zero emacs shortcuts; I used the menu interface for all but a few commands. The first (and only for about 3 years) elisp I wrote was a command to open up the current file in vim, and reload it when vim exited. This let me browse & debug source with emacs while editing with vim. SLIME offered so many features that this was an actually useful workflow, and I didn't switch to using emacs for editing as well until much later, when evil-mode came out. side-note: I had tried other vi-like modes prior to evil-mode coming out (e.g. viper), but they fell in an uncanny valley for me; just familiar enough that I would regularly muscle-memory some sequence that didn't work in viper.