News for hackers. Stuff that matters.
Re:GitHub code search is generally available by lelandfe on Monday May 08, 2023 @07:27PM (#35868287)
> Vs Code? wtf? there's a lot of other IDEs/editors and many would argue that they are better

VS Code is hugely dominant in terms of IDEs used by developers per the StackOverflow survey. It commands more than double the percentage of the next most used… and the second place is Visual Studio.

https://survey.stackoverflow.co/2022/#most-popular-technolog...

Re:GitHub code search is generally available by coffeebeqn on Monday May 08, 2023 @08:00PM (#35868579)
VSCode is just the lowest common denominator IDE that works decently with most languages and platforms, I use it a lot but would not think twice about switching to something else (as I have many times in my career). I don’t think it really has any “moat”
Re:GitHub code search is generally available by tipsytoad on Monday May 08, 2023 @08:31PM (#35868808)
Lol. Except the huge library of plugins, tight copilot integration and majority market share
Re:GitHub code search is generally available by fomine3 on Monday May 08, 2023 @10:41PM (#35869616)
and Remote Development extensions
Re:GitHub code search is generally available by lolinder on Monday May 08, 2023 @09:15PM (#35869101)
Those numbers are a bit misleading because they split up the JetBrains products, making JetBrains look like a smaller market than it actually is. If you add up all their tools, they hit 94% to VS Code's 74%. Obviously there are a lot of people using multiple JetBrains tools and that bloats that number, but the huge difference demonstrates how flawed SO's numbers are for gauging market share.

Also, I suspect that most people who mark a JetBrains IDE also mark a secondary editor that's lighter weight, but it's hard to tell how that all breaks down with the way they present the data. I spend about 90% of my work day in WebStorm and occasionally move over to VSCode for loading a large directory that I don't want to index. When I filled out the survey, due to they way they worded it, I marked both tools.

Re:GitHub code search is generally available by Olicer on Saturday May 20, 2023 @11:16AM (#36012607)
Add Comment lolinder 11 days ago | parent | context | on: GitHub code search is generally available

Those numbers are a bit misleading because they split up the JetBrains products, making JetBrains look like a smaller market than it actually is. If you add up all their tools, they hit 94% to VS Code's 74%. Obviously there are a lot of people using multiple JetBrains tools and that bloats that number, but the huge difference demonstrates how flawed SO's numbers are for gauging market share. Also, I suspect that most people who mark a JetBrains IDE also mark a secondary editor that's lighter weight, but it's hard to tell how that all breaks down with the way they present the data. I spend about 90% of my work day in WebStorm and occasionally move over to VSCode for loading a large directory that I don't want to index. When I filled out the survey, due to they way they worded it, I marked both tools.

If you haven't already, would you mind reading about HN's approach to comments and site guidelines?

Add Comment lolinder 11 days ago | parent | context | on: GitHub code search is generally available

Those numbers are a bit misleading because they split up the JetBrains products, making JetBrains look like a smaller market than it actually is. If you add up all their tools, they hit 94% to VS Code's 74%. Obviously there are a lot of people using multiple JetBrains tools and that bloats that number, but the huge difference demonstrates how flawed SO's numbers are for gauging market share. Also, I suspect that most people who mark a JetBrains IDE also mark a secondary editor that's lighter weight, but it's hard to tell how that all breaks down with the way they present the data. I spend about 90% of my work day in WebStorm and occasionally move over to VSCode for loading a large directory that I don't want to index. When I filled out the survey, due to they way they worded it, I marked both tools.

If you haven't already, would you mind reading about HN's approach to comments and site guidelines?