Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ui-best-practices-working-group] [ide-dev] VS Code

On 14 September 2016 at 21:54, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:
On 2016-09-14, 2:25 PM, "ide-dev-bounces@xxxxxxxxxxx on behalf of Gorkem
Ercan" <ide-dev-bounces@xxxxxxxxxxx on behalf of gorkem.ercan@xxxxxxxxx>
wrote:

>On 13 Sep 2016, at 16:06, Doug Schaefer wrote:
>
>
>VS Code is a coding editor not an IDE. It caters a different workflow
>than IDEs. Yes there are ideas here and there that can be applied to
>Eclipse workflows such as the language server but I think Eclipse should
>continue to improve on its workflow and not borrow a new one.

I¹ve heard this argument before. What¹s an IDE?

As soon as you have integration with a debugger, I consider you an IDE. VS
Code has that.


I agree with this. I think once you integrate with a debugger, or a *semantic* tool (like code completion deamon), you have an IDE, not an editor. Under this sense Vim/Emacs when used for programming would be an IDE. But this just arguing abstract semantics, most users would still call their tool "editors". Vim/Emacs in particular would probably be offended if their tool is called an IDE. :p

I think what is really important is whether the user expect their IDE/editor to be "lightweight" and "simple". Because the VS Code people call their tool an "editor", they are making a statement that they expect to deliver something "lightweight" and "simple". Whilst those terms are not precisely defined either, I'd expect most users would agree VS Code is simple and lightweight, and Eclipse is not, far from it. (BTW, neither is IntelliJ)

So I think trying to draw UX lessons from VS-Code to Eclipse is not going to work well, IMO, unless you want to redesign a whole new Eclipse workbench.

--

Back to the top