221–230 of 427 posts
If it's in Java it's not exactly lightweight.
VSCode is Electron. You can't be more heavyweight.
Not using any of the above mentioned anymore, so I'm not teaming for one site.
Earlier quoted context omitted.
Same. > For years folks have been asking us, “JetBrains, when will you create a lightweight editor?” I sure never did. If anything, I want their IDEs to be more involved and sophisticated. Otherwise I'm likely going to cancel our company subscriptions next year, VSCode is starting to overtake e.g. PyCharm in terms of developer comfort. So I really hope this is just a tech demonstrator to renew the architecture of the…
I've worked in 4 different software shops over the last 15 years. My general observation is the developers who rely on heavily automated/magic tooling are significantly outclassed by those who use the terminal + a basic text editor. Terminal + Vim or Emacs/VSCode (depending on configuration) is not only all you need, it also produces developers who understand the systems they work with. I know a lot of people will di…
Also, autocompletion, in-built documentation can be a great tool to learn as well (I read much more documentation due to a quick hotkey showing me it, than I would manually hunting it down). And I know that these tools can be customized to do all these, my experience is that with so many tools they tend to be buggy and slow, and still only support a handful of features that a full-blown IDE does.
Earlier quoted context omitted.
I've never used IDEA and friends for JavaScript. Are they not using the LSP?
They've historically done a lot of things on their own for JS. So perhaps VS Code + TS language server isn't quite on par with their JS tooling (which works a lot better with TypeScript type definitions, though, so perhaps it's just mostly the same as well). However, what I personally hated was that there's so many squiggly underlined things ... in red, yellow, green and what other colors, each of which (regardless o…
> especially because issue categorization and accuracy was so random
Stockholm syndrome is strong with this one. =)
the reason you didn't find the IDE suggestions helpful is exactly because of how difficult it is to reason about dynamic language code. the tooling is basically just guessing and expecting you to deal with the noise on the off chance it found something.
Earlier quoted context omitted.
I've worked in 4 different software shops over the last 15 years. My general observation is the developers who rely on heavily automated/magic tooling are significantly outclassed by those who use the terminal + a basic text editor. Terminal + Vim or Emacs/VSCode (depending on configuration) is not only all you need, it also produces developers who understand the systems they work with. I know a lot of people will di…
I learned programming with paper, pen, match boxes to represent unary turing machines, and printed out language manuals, I'm afraid you can't out-hipster me with just emacs. And you completely miss the point: I'm fully aware that they exist, and that's the problem. Lightweight yet modular editors are such a crowded market that I don't see a realistic way for JetBrains to successfully compete in it. They don't have th…
If anything, they just want to build up a new frontend and the first look on that will be an “easy” one with a vanilla code editor.
Earlier quoted context omitted.
at that point why don't they just use native + skia ? Seems weird to build a web based editor to then just use canvas.
At a guess, they're probably sticking with it because it enables Javascript/Typescript as an interfacing language for plugins which, given the language's popularity and cross-platform nature, is probably part of the reason the plugin catalogue is so large.
Earlier quoted context omitted.
> People moved from IntelliJ to VSC because it was faster, simpler and language-agnostic, instead JetBrains blamed users for not using advanced features like CPU profiling which most people don't use daily. They are jumping on simple-editor train now. Better late than never From my experience, most people who nowadays start programming, flock to vscode because it's free, used in most tutorials and then they simply do…
I tend to agree. It's a bit like the dynamic vs. static typing situation. New comers often prefer languages like Python at first for their simplicity, only to "rediscover" that static typing is so much more manageable later in their career.
However, I don't see how you can do either of those features well without a lot of indexing of the codebase. And indexing is a major reason why IntelliJ so so clunky.
Earlier quoted context omitted.
VSCode is Electron. You can't be more heavyweight.
You never started any Java-based IDE, did you? You can smack tons of plugins into VSCode, enable them all and it still loads faster. Not using any of the above mentioned anymore, so I'm not teaming for one site.
Java itself doesn’t have that slow of a startup.
Earlier quoted context omitted.
They've historically done a lot of things on their own for JS. So perhaps VS Code + TS language server isn't quite on par with their JS tooling (which works a lot better with TypeScript type definitions, though, so perhaps it's just mostly the same as well). However, what I personally hated was that there's so many squiggly underlined things ... in red, yellow, green and what other colors, each of which (regardless o…
> Granted, that's how easy it is to properly check JS code for whether it does something sensible > especially because issue categorization and accuracy was so random Stockholm syndrome is strong with this one. =) the reason you didn't find the IDE suggestions helpful is exactly because of how difficult it is to reason about dynamic language code. the tooling is basically just guessing and expecting you to deal with…