I wrote it in the wee hours one morning in a rotten mood and it shows. There are far too many absolutes that should have been qualified and the writing style is too aggressive for no good reason. I'm not taking it down because there are worthy comments, and I refuse to try to pretend it never happened. But I absolutely regret writing this article in this way. If you choose to read this, use a large sanity filter and look at some of the comments and the follow-up for qualifications to help see what I'm getting at.
I blame myself for writing this at 2: It was supposed to be humorous but it wasn't. I start with some incontrovertible facts.
The relevant facts are these: Well, actually things are subtler than that. Well, actually, I think that argument has it exactly backwards, and leads to the undoing of the points I made in the first place. It was certainly the case that with a big disk and swappable memory sections any program you could write in bit addressing could have been created in bit especially that crazy x86 segment stuff. But would you get good code if you did so?
And would you experience extraordinary engineering costs doing so? Were you basically fighting your hardware most of the time trying to get it to do meaningful stuff? It was certainly that case that people came up with really cool ways to solve some problems very economically because they had memory pressure and economic motivation to do so.
Those were great inventions. But at some point it got kind of crazy. The kind of bit code you had to write to get the job done was just plain ugly. The bit code was slow ugly crapola working around memory limits in horrible ways and the bit code was nice and clean and directly did what it needed to do with a superior algorithm.
In my thinking was that for the foreseeable future, the opportunity cost of going to bits was too high compared to the inherent benefits. Is that still the case? The case for economy is still strong.
Dec 29, · The topic of bit Visual Studio came up again in a tweet and, as usual, I held my ground on why it is the way it is. Pretty predictable. But it’s not really possible to answer questions about your position in a tweet, hence this posting. Jun 27, · What's New in this Release Tools for Apache Cordova. Visual Studio Update 3 includes Tools for Apache Cordova Update 10, including the improvements below. and Update For the latest news about our tools, visit our Developer Blog on GitHub.. We've added support for Cordova , the default version for new projects. Visual Studio System Requirements. System requirements for the Visual Studio family of products are listed in the table below. For more information on compatibility, please see Visual Studio Platform Targeting and Compatibility. For Visual Studio , see Visual Studio Product Family System Requirements.
Architecture[ edit ] Visual Studio does not support any programming language, solution or tool intrinsically; instead, it allows the plugging of functionality coded as a VSPackage. When installed, the functionality is available as a Service. The IDE provides three services: In addition, the IDE is also responsible for coordinating and enabling communication between services. A language service defines various interfaces which the VSPackage implementation can implement to add support for various functionalities. Language services are implemented on a per-language basis. The implementations can reuse code from the parser or the compiler for the language. Visual Studio.