Re:Visual Studio Code Will Replace Visual Studio
by userbinator on Saturday May 05, 2018 @01:03AM
(#17000414)
Also they aren't very good at the collecting part if they let you just disable, and make it known that you can, while also providing versions (the OSS version) that don't even have the data collectors.
It's opt-out, not opt-in, and how many people will bother to? Things like this don't really inspire confidence either:
https://stackoverflow.com/questions/40451596/visual-studio-c...
Re:Visual Studio Code Will Replace Visual Studio
by cup-of-tea on Saturday May 05, 2018 @01:14AM
(#17000447)
What kind of shoddy programming means it can't just be compiled for 64 bit? Why would they bake the word size so deeply into a program like that?
Re:Visual Studio Code Will Replace Visual Studio
by Karliss on Saturday May 05, 2018 @02:39AM
(#17000666)
Last time i checked c++ debugger still used 16 bit line numbers. My attempts to make a plugin for vs also left an impression that it contains large amount of modules glued together using various technologies. Things like 5 layers of c# API wrappers named api10, api20, api30 on top of some c code communicating using COM objects. I wouldn't be surprised if they still had some third party libraries for which they only have a binaries and vendor doesn't exist anymore.
Re:Visual Studio Code Will Replace Visual Studio
by pzone on Saturday May 05, 2018 @01:37AM
(#17000504)
Compilers and IDEs are resource intensive pieces of software and VS is over twenty years old. I can imagine innumerable opportunities over the years to increase performance by assuming the size of certain variables in memory. That kind of stuff would have been a big deal when compiling C++ on a 333mhz processor.
Also they aren't very good at the collecting part if they let you just disable, and make it known that you can, while also providing versions (the OSS version) that don't even have the data collectors.