Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code is designed to fracture

ghuntley.com

Post reply on HN
Print view View original

141–149 of 149 posts

Re: Visual Studio Code is designed to fracture

#141

Post by bsder »

delta_p_delta_x wrote: post #60
bsder wrote: post #31

Earlier quoted context omitted.

> Why put your time making plugins for VS Code when rug can be pulled from under any time? Because VSCode is a huge step forward for the vast majority of people. For example, it took the might of Microsoft to force everybody onto a Language Server Protocol which is how things should have been done everywhere but nobody wanted to work together to implement it until they were forced to by VSCode eating their market sha…

> As a further example, VSCode is sweeping aside a whole bunch of absolutely garbage embedded programming environments, and I assure you nobody is crying any tears for them. Quick point about embedded: in my short summer internship where I was working on some STM32 hardware, I was quickly exposed to the plethora of semi-proprietary embedded IDEs which were themselves based on FOSS IDEs and editors (STM32CubeIDE, MBED…

> Why do these even exist?

Because there existed a time before ARM, 32-bit processors, and gcc made embedded a monoculture like x86. Because there existed a time before IDEs converged via Language Server Protocol.

This was predictable back when VSCode first came out. Microsoft was pouring more development resource into VSCode that many of those semiconductor companies entire revenue. Either you got on the VSCode train or you were going to get swept aside.

The fact that everybody is whining about proprietary Microsoft remote development plugins while emacs tramp lsp-mode remains broken for an enormous number of cases for years says it all (this is finally what pried emacs out from under my fingers as I got tired of debugging it).

Re: Visual Studio Code is designed to fracture

#142

Post by Ferret7446 »

slimsag wrote: post #79
brundolf wrote: post #61

Earlier quoted context omitted.

But ultimately these applications are still winning based on merit. If somebody created a new editor or browser that was substantially better, nothing's really stopping everyone from moving to it. Now- we can talk about how it's a problem that nobody can afford to build something good enough to compete with what these megacorps can afford to develop and give away for free. But that's a different, older, much bigger d…

You and GP's point is that these applications win on the merits of their user experience. That's not wrong, in fact I'd say that's absolutely true. But it's important to call out that the user experience most people care about has almost nothing to do with whether or not software is open/hackable. Because of that, I would suggest it is realistic that a decade or two from now we could largely lose that feature, and fi…

>But it's important to call out that the user experience most people care about has almost nothing to do with whether or not software is open/hackable.

For software developers I think that's a damn shame. Craftsmen have always made their tools suit themselves. If you aren't hacking your development tools, you're missing out, and if that opportunity is lost due to closed IDEs, that really sucks.

Re: Visual Studio Code is designed to fracture

#144

Post by al_mandi »

themoonisachees wrote: post #113
al_mandi wrote: post #78

Earlier quoted context omitted.

> and moved on to better languages anyway Such as?

Any other language other than java

Not golang or javacript or python I hope. All quite bad languages.

Furthermore, the ecosystem matters quite a bit.

Re: Visual Studio Code is designed to fracture

#145

Post by forgotmypw17 »

d_k_f wrote: post #81
input_sh wrote: post #59

Earlier quoted context omitted.

FYI you can get around HSTS errors on Chromium-based browsers by typing thisisunsafe. Source: https://chromium.googlesource.com/chromium/src/+/d8fc089b62c...

Additionally, you can remove stored HSTS states using Chrome's chrome://net-internals configuration page.

Not anymore:

>The net-internals events viewer and related functionality has been removed. Please use chrome://net-export to save netlogs and the external netlog_viewer to view them.

Re: Visual Studio Code is designed to fracture

#146

Post by crazyjustin »

barrysteve wrote: post #120
nindalf wrote: post #117

Earlier quoted context omitted.

I’m not saying de-anonymisation is impossible. Obviously it is. I’m asking you to 1. Tell us what VSCode collects that’s so sensitive 2. Show us how you’d de-anonymise a person with that information (but I’m willing to concede that this is possible) 3. Demonstrate harm from knowing that a specific person is tied to a set of VSCode logs. Don’t hand wave #3 away. Don’t assume that it’s self-evident that the harm is hig…

I rewrote this comment a couple times before posting, as getting through to your perspective rules out what I consider logical common sense. You're still asking the wrong questions because you don't get the process. VSCode could collect anything at all, but let's be hypothetical, yet specific so you understand the process. I'm going to use these two pages as reference [0]This RoboLeary blog post describes what VSCode…

Thank you for taking the time to type this out. I've been uncomfortable about telemetry data for a while but this makes it clear to me that it can be used to do a lot more than just drive ui changes. Google has been fingerprinting in this way for decades. Of course Microsoft can do the same.

I've been thinking about trying VSCode. I'm the only dev I know at my org that doesn't use it and I guess it's going to stay that way.

I really don't understand the mindset of some folks. In this dynamic Microsoft has all the power and therefore the burden of transparency and proof of good will should be on them. Why would you give away information about yourself freely to an entity with no oversight. There is no reason to trust a corporation with your personal data.

Re: Visual Studio Code is designed to fracture

#147

Post by yencabulator »

vikinghckr wrote: post #62

Meanwhile Google and Facebook internally use VS Code based IDEs as their official developer tooling. Pretty sure their legal teams have considered any legal risks with licensing.

Google also uses/used Perforce. They're fine with using commercial & proprietary tools. That's not really the same conversation as here.

Re: Visual Studio Code is designed to fracture

#148

Post by d_k_f »

forgotmypw17 wrote: post #145
d_k_f wrote: post #81

Earlier quoted context omitted.

Additionally, you can remove stored HSTS states using Chrome's chrome://net-internals configuration page.

Not anymore: >The net-internals events viewer and related functionality has been removed. Please use chrome://net-export to save netlogs and the external netlog_viewer to view them.

Interesting (and sad), thanks for the correction.

I was using "Kiwi Browser" on mobile to ensure I had the right address, which is a Chrome fork that allows extensions (I think they're forking Chrome instead of "just" Chromium since it looks and feels like regular Chrome otherwise). In here, I still have it available. Might be high time to check for something similar on the desktop.

Re: Visual Studio Code is designed to fracture

#149

Post by xwolfi »

onion2k wrote: post #40
xwolfi wrote: post #29

Earlier quoted context omitted.

You comingle HN and Ycombinator maybe? I dislike VCs and startup culture while I work in a 150yo bank ... I still like HN and shit on the model you described.

I dislike VCs and startup culture.. I suspect you are quite unusual in the demographics of HN readers then. while I work in a 150yo bank I'm British so I think 150 year old banks are quite new.

Ahahah you know how it goes, they split and they merge, and you need to draw the line somewhere.

And I think HN is now near as ubiquitous as StackOverflow among programmers as a source of IT news or as a forums on stuff that concern us all.

Why should we like venture capitalists ? The people I met who had to deal with them weren't too happy abt their deal with the devil, it's not like it always works out 's

Post reply on HN