Earlier quoted context omitted.
Sublime's updates are dismal. https://www.sublimetext.com/blog/ I had to switch to Atom just because the development is stagnant. I liked Sublime very much. But it's been 2 years already..
But what is missing in sublime?
Visual Studio Code 1.8
61–70 of 197 posts
Re: Visual Studio Code 1.8
#62Earlier quoted context omitted.
It was console.log() all the way
The Chrome based dev tools have been an option for years using node-inspector. Had all of the basics that you would expect from a debugging. Breakpoints, step into/out/over, variables available at that location in the stack, REPL console etc.
Re: Visual Studio Code 1.8
#63Earlier quoted context omitted.
The debugger changed how I code. So much better than any other node debug solutions.
I'm confused. Did javascript people not use a debugger before VS Code?
Re: Visual Studio Code 1.8
#64Why are people using this instead of WebStorm? It seems like: - It a little faster for Typescript (but no better TS features from what I can see). - A lot of people are trying it because it's new, or because they like MS tools. - It's free On the other hand WebStorm still has more functionality overall, a few less rough edges, and a more standard UI (some people don't like how MS Code doesn't have a tabbed doc UI). M…
Re: Visual Studio Code 1.8
#65There is an issue though that I find so annoying and I just hope they fix it.
I set up the external terminal to git bash on windows and sometimes when I'm deleting commands with the backspace it doesn't really delete the full word, hard to explain but as an example if I type "nani" and then press backspace "nani" stays but I know it has been deleted because it kinda flicks so I type "o" now I have in the terminal "nanio" and sure enough if I now type the name of the file it edits it.
Hope this makes sense, I put up with it because I'm really enjoying the product and the speed of development.
Big congratulations to the team.
Re: Visual Studio Code 1.8
#66Re: Visual Studio Code 1.8
#67I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editing tasks) but I found that I was increasingly having to learn outside tools in order to gain the benefit that IDEs could hand me for "free" (free like a puppy, retraining your fingers takes months).
Things I love:
- Intellisense is immediately superior to anything I've used in EMACS.
- Debugging from my editor. This was available in emacs for C, PHP & Java using GDB or similar but it never made it's way to javascript as far as I can tell.
- Goto definition.
- Good typescript and Flow integration
Things I miss:
- IDO Mode (FML I hate Finder for moving through directories)
- Creating files with just the keyboard (probably possible but I haven't figured it out yet).
- Kill ring
- Moving around the code with just a keyboard (ctrl-v and the sort).
- Non-intellisense completion. When your caret is at the end of a word, Command-\ in EMACS completes to another word from the same buffer that has the same prefix and continue to swap through words on subsequent presses. Very useful in a dynamic language.
Re: Visual Studio Code 1.8
#68Earlier quoted context omitted.
The Chrome based dev tools have been an option for years using node-inspector. Had all of the basics that you would expect from a debugging. Breakpoints, step into/out/over, variables available at that location in the stack, REPL console etc.
It was kind of a pain in my experience to use the Chrome debugger to be your main editor. I've not used VSC for this, but I imagine it's nice to not have to flip back and forth between tools.
Re: Visual Studio Code 1.8
#69Why are people using this instead of WebStorm? It seems like: - It a little faster for Typescript (but no better TS features from what I can see). - A lot of people are trying it because it's new, or because they like MS tools. - It's free On the other hand WebStorm still has more functionality overall, a few less rough edges, and a more standard UI (some people don't like how MS Code doesn't have a tabbed doc UI). M…
Downvotes? Would be interested to know which points were inaccurate.
My best guess for your downvotes is that your comment isn't only nonsense and inaccurate, but also pretty churlish.
Re: Visual Studio Code 1.8
#70It looks pretty good congratulations to the team. There is an issue though that I find so annoying and I just hope they fix it. I set up the external terminal to git bash on windows and sometimes when I'm deleting commands with the backspace it doesn't really delete the full word, hard to explain but as an example if I type "nani" and then press backspace "nani" stays but I know it has been deleted because it kinda f…