171–180 of 197 posts
Earlier quoted context omitted.
> In general, ignorance is not a pejorative but if a candidate walk into an interview claiming to be an expert and I find out that you debug in anger using console log, I'm calling bullshit. Some of the best programmers advocate for printf over debuggers... And some of the crappiest programmers run around the debugger for hours with no idea what could be wrong in the program, stepping blindly here and there...
To explain this further, I think printf is more focused and direct than running around in the debugger. You need to have a clearer idea of what you're looking for in advance and know how to exclude parts of the program as possible culprits, which I think helps with debugging in general. And, come to think of it, with hot code reloading, printf can be just as immediate, but more direct and focused, than using the debu…
Earlier quoted context omitted.
How is it better than the one in IntelliJ/webstorm?
I don't know, I don't use intelliJ and I don't want to pay for webstorm. Somebody else probably knows. Anyway I like how low-memory-on-the-disk and low RAM usage VScode is, so I probably wouldn't enjoy intelliJ and webstorm for those reasons. I felt like even sublime was too bulky for me. Maybe they're good for other people and that's fine, but vscode just ticks all the right boxes.
Once you figure that if anything makes your days better by spending $10 or so a month, not choosing the best tool for the job sounds simply dumb.
I have a friend who sticks with plain vim uncustomized because he doesn't want to deviate from the default in fear of not being able to seamlessly use other environment sounds utterly stupid wasting productivity for 99% of the time being on his own machine.
Earlier quoted context omitted.
> In general, ignorance is not a pejorative but if a candidate walk into an interview claiming to be an expert and I find out that you debug in anger using console log, I'm calling bullshit. Some of the best programmers advocate for printf over debuggers... And some of the crappiest programmers run around the debugger for hours with no idea what could be wrong in the program, stepping blindly here and there...
To explain this further, I think printf is more focused and direct than running around in the debugger. You need to have a clearer idea of what you're looking for in advance and know how to exclude parts of the program as possible culprits, which I think helps with debugging in general. And, come to think of it, with hot code reloading, printf can be just as immediate, but more direct and focused, than using the debu…
Debuggers are a valuable tool that nowadays should be standard.
Why 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…
I upvoted your comment because your points are accurate (I have both WebStorm and Visual Studio Code open all day every day for my current project) and informative, but mostly because what the fuck are adiranlmm and plexicle going on about. From my experience, I would just add that while WebStorm is indeed far more powerful in terms of features that it has, it: - is actually slower even than VS Code for many operatio…
That "full of shit", which is useful to some, I just go to plugins and uncheck them, once.
Earlier quoted context omitted.
WebStorm has both Intellisense-like autocomplete and word completion. Its "Jump to definition" helped me become a better programmer because jumping into library code became a habit - be it Ruby or Javascript (I use RubyMine). They were one of the first editors to fully support JSX, and before that they came first in supporting Angular v1 and its directives. They let you refactor code in dynamic languages, does it sil…
Couldn't agree more, intellij is my favourite piece of software ever.
I want to love you, VS. Your name would look so good on my resume.I'm going to try one more time.
I don't work on vscode directly, have contributed bug fixes and features but if you'd like to be considered for a team inside visual studio working on web diagnostics, please ping me.
Why 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…
vs.code - FREE - faster - source is on github - easy to write, fix plugins in javascript - javascript intellisense is better WebStorm is a good product but it doesn't really do anything that much better than vs.code that I would go back to it. Was a long time WebStorm user.
Stuff like Atom, I dig a dozen plugins only to keep 3 or so in the end, because they're written by random people with random quality, which is not much of use.
mini-map is the only thing stopping me from jumping to VSCode.
Never used it on sublime text. Genuinely curious.
I'd use method listing which is visually more distinguishable.