Project Ticino: Microsoft's Erich Gamma on Visual Studio Code past, present, and future Visual Studio Code only succeeded because a failed online editor was pivoted to become a desktop product, according to Microsoft Distinguished Engineer Erich Gamma. Gamma spoke at the virtual VS Code Day yesterday on how the world's favourite programmer's editor (or is it an IDE?) came about. Introduced at the Build event in …
"What many people don't know is that we decided to not use any UI frameworks from the beginning and that's still true today," Gamma added, "because performance is very important to us and we want to be fully in control of our own destiny."
This is very refreshing to hear a developer say this. I will likely be using this to help strengthen any arguments against the occasional framework obsessed guy I have to deal with.
Obviously because it is Microsoft I have to sound a little bit petty and include this modified quote:
"we want to be fully in control of our own destiny [and the destinies of all the other twits who buy into our ecosystem]."
But my respect for this team in general has gone up a little.
This post has been deleted by its author
Indeed, my bad for getting befuddled there.
But it's still a horrid language to code in in my opinion, and I think the decision to ignore any existing frameworks illustrates either Not Invented Here syndrome, or the fact that nothing exists yet that was considered up to scratch for that language.
Gamma spoke at the virtual VS Code Day yesterday on how the world's favourite [sic] programmer's editor (or is it an IDE?) came about.
Being old enough to remember (or forget) edlin, the Visual C++ 6.0 "editor", and the abomination known a QuickC, I find myself comforted that I have not and continue not to drink the Micros~1 Kool-Aid, and that regardless of "favo(u)rite-ism", VSCode does not grace any of my desktops.
JetBrains FTW! (Did you notice that VSCode is one keystroke away from truth in advertising, identifying itself as a Disease of the Venereal (not Venerable) kind?)
Now take yer damn editor and git offa my lawn!
They are using a UI framework - their own one. Those that decry frameworks bemuse me - every API is basically a "framework", be it a library or even something as low level as system calls. The reason the term gets so much abuse seems to be down to the JavaScript world, where every year or two a new framework eclipses the previous ones.
Visual Studio offers a "Community" edition, which is free (in the sense of nothing to pay). But if that didn't exist, then I'd just modify my question to limit it to professional developers. Presumably, if you can afford to buy hardware to work on, then you can afford to buy software to use, too.
My question was really not rhetorical. I have a sense that I must be missing out on something important but can't see what it is. VSCode hype is everywhere: it has attracted a lot of developer love, lots of effort and management attention from MS. But every time I look at it, it feels like a product for someone else (a Linux person, maybe?).
What's the idea for the future? Will VSCode evolve to be a full IDE and replace Visual Studio, or somehow will IDE users be forced to downgrade to working with an advanced code editor and some command line wrangles? Where is this all heading?
Well, IMHO VSCode/Codium is lighter/easier to install and can manage more languages/files types with its plugins. Also the interface is more simpler than the VS one. On the contrary if I have to develop in C++ for Windows, I would choose VS Community for sure (I don't use .Net). For other languages/tools like Typescript/Python/Go/Terraform/SQL/Markup/HTML/Docker/Generic editor/etc VSCode/Codium is my choice.
If your editor and computer don't crash every five minutes, why would you ever lose work because you didn't have auto-save? And when "Save All" is only ever a couple of keystrokes away, why is it such a "great feature" for the computer to do it for you?
My memory is a bit dim if you go back too many decades, but the only times that I have ever felt that I'd "lost work" were when I saved something broken over something that wasn't without having first put the working stuff to revision control. Auto-save sounds like a way to automate that mode of failure.
"Says who?"
Jetbrains and Stackoverflow polls say that.
"I don't know anyone in my team who uses it."
C'mon, personal experience is not evidence, it is anecdote. You can't generalize based on that.
"I tried it once, couldn't stand it, typical GUI editor bloatware, went back to vi"
Typical comment from a vi fanboy. Bloatware? OMG, it's just a simple editor. The "Bloatware" level depends on the number of plugins you install in it.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
