I have tried VSCode a few times for C++ on macOS and always found it more hassle than it was worth to get it up and running. I saw it had debugging options and I thought that looked pretty cool but it is a bit of a mess with tasks.json and some other file I have forgotten about now. I recall I did finally get a working setup but it wasn't portable between folders/projects as the binary filenames were hardcoded and I…
The Rise of Microsoft Visual Studio Code
211–220 of 327 posts
Re: The Rise of Microsoft Visual Studio Code
#212Earlier quoted context omitted.
amen people look at me like I'm an old crazy dude because I don't use a git UI or eclipse, or intellij, or from sublime. Git already has plenty of quirks, adding another layer of unknown on top of it is a no-go
Which is weird because with all of its inconsistencies, git must have been designed with the idea that someone would build a sensible shell over top of it. I can't imagine Linus expected people to interact directly with git when he built it.
Re: The Rise of Microsoft Visual Studio Code
#213Having gone through Triplebyte's interview process, I'll propose another interpretation: Triplebyte's interview is on aggregate biased against Java and C# developers. I'm not accusing Triplebyte of "being biased", but rather pointing out that Java and C# tend to correlate to a skill set that Triplebyte's test process values less. My experience of Triplebyte's interview process is slanted towards frontend/backend deve…
Further, it looks like the questions are biased towards Ruby devs.
Harj Taggar https://github.com/kwi
Guillaume Luccisano https://github.com/harj
Re: The Rise of Microsoft Visual Studio Code
#214Earlier quoted context omitted.
git has its problems, but it's a consistent, centralized (in the sense of origin/repo), well known set of problems. I use multiple IDEs/editors, and they all handle git differently. It doesn't make sense to learn yet another N sets of quirks.
> git has its problems, but it's a consistent, centralized (in the sense of origin/repo), well known set of problems. Consistent? Ha! Change branch: git checkout my-branch . Reset file to committed version: git checkout -- my-file . Git is many things, but consistent it is not. That said, I still use CLI precisely because I don't trust other software to make sensible abstractions on top of it, given that foundation i…
> well known set of problems
that's precisely the well know set of problems. You learn them once, apply on every console. If each UI decides to overcome them differently, you end up with N+1 different behaviors.
I'd rather have only one set if inconsistent commands, than 3.
edit:formatting
Re: The Rise of Microsoft Visual Studio Code
#215Earlier quoted context omitted.
Are sublime multi-cursors different from code multi-cursors?
It's a first class citizen in Sublime. There is no lag or weirdness when you are using them.
Re: The Rise of Microsoft Visual Studio Code
#216Earlier quoted context omitted.
Both of these are still just very roundabout ways of telling yourself you're awesome because of whatever mildly unusual thing you think you might be doing.
And this comment is just a subtextual justification for making sure you still feel valued for not doing anything unusual. This could go round and round. The point is that there SEEMS to be a correlation with people who learn things for the sake of learning them and folks who do well at exercises that test for adjacent skills.
I didn't really express any thoughts or feelings about doing unusual things, real or perceived. Doing unusual things can be great! Telling yourself you are awesome can also be great! I do think, though, that the type of thought expressed in the "The Python Paradox" and related writings (say, the bit about blub language programmers) is pretty lousy. It was lousy then and has aged even more poorly.
Re: The Rise of Microsoft Visual Studio Code
#217Earlier quoted context omitted.
Maybe it’s because the editor was taught to students at places like MIT, Berkeley, etc?
I learned emacs in the late 1980's -- it is now an ingrained part of my brain. I hate when I have to use an IDE w a different editor -- at least most editors (and GUI components like browser textfields) respond to common emacs key-sequences.
Had to use Android Studio/Eclipse for some time but it was so much harder that I kept trying to find ways to use vim even if I had to memorize or copy/paste package dependencies from Android.
I honestly wish I could use some of the most advanced refactoring tools from IDEs into vim but the way I edit is so ingrained that it's simply not worth it.
Re: The Rise of Microsoft Visual Studio Code
#218There are some warts, but it seems nice from afar. The biggest wart is/was the "FUCK FUCK FUCK" git clean vs git reset UX error: https://github.com/microsoft/vscode/issues/32405 . This is a fantastic demonstration of why i exclusively use git from a command prompt -- i know what will happen and nobody's going to reinvent terms to put on buttons that just confuse me. In my life: - I'm committed to emacs for org-mode a…
> and multiple cursors everywhere is a boon for quick and dirty data munging. VSCode has this. Hold down Command on Macs (probably Ctrl on Windows/Linux) and click. You can also select "next similar word" with command-D so you can quickly change all instances of a word to another word.
Re: The Rise of Microsoft Visual Studio Code
#219There are some warts, but it seems nice from afar. The biggest wart is/was the "FUCK FUCK FUCK" git clean vs git reset UX error: https://github.com/microsoft/vscode/issues/32405 . This is a fantastic demonstration of why i exclusively use git from a command prompt -- i know what will happen and nobody's going to reinvent terms to put on buttons that just confuse me. In my life: - I'm committed to emacs for org-mode a…
I still use the CLI to push/pull/branch/merge, etc just to have total control, but staging files, viewing diffs and making commits are a lot more annoying in the CLI.
Re: The Rise of Microsoft Visual Studio Code
#220It seems strange to me to compare VSCode against PyCharm, IntelliJ, and Android Studio separately. While PyCharm, IntelliJ, and Android Studio are distinct applications, I believe they share much of their code, UI, 3rd party plugins, and workflows for all being JetBrains language-flavored IDEs. On the other hand, VSCode supports different languages through its extensions instead of having separate language-flavored a…
Having a dedicated IDE for a given language has it's pros.
However, I use VSCode for JS/HTML development, as it has a lot less clutter, than compared to other IDE's.