4 ms·
I guess all modern IDEs can be considered unified at this point, but the idea is that all the tools and integrations are part of it - including the build proces
by overload119 12y ago
I guess all modern IDEs can be considered unified at this point, but the idea is that all the tools and integrations are part of it - including the build process, typechecker, etc.
Before you would have to run all these in the background + have your IDE open (ie. Sublime Text).
Of course Sublime Text has plugins itself now too, but you get the idea.
- codemac 12y agoIt's similar to developing emacs-lisp packages with emacs. It's a dream.
- stephenr 12y agoSublime is not an IDE. It's a text editor. There is a difference.
- ssalazar 12y agoI don't get the idea. And Im not sure when Sublime Text became considered an IDE, if anything it is anti-IDE. An IDE classically has tools and integrations, well, integrated. E.g. Visual Studio or Eclipse.
- blister 12y agoSublime Text has a really robust plugin architecture, similar to Visual Studio's extension capabilities. Whenever I'm working on a project, I basically install whatever plugins I need into Sublime Text to give me full "IDE-like" capability specific to that stack. Be it debuggers, integrated compilers, REPLs, version control systems, etc. I like Sublime Text because at it's default, it's just a text editor, and then _I_ turn it into the IDE that fits my flow and current technology requirements. It becomes an IDE completely customized for my project.