Why VSCode doesn't use any front end framework
1–10 of 18 posts
Re: Why VSCode doesn't use any front end framework
#2Erich Gamma, Technical Fellow, Microsoft:
> 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 because performance is very important to us, and we want to be fully in control of our own destiny. So we don't want to chase a framework or track down performance from in the framework, we want to be directly as close to the DOM as possible.
Re: Why VSCode doesn't use any front end framework
#3That makes sense for this type of application. But people are going to start complaining about React and other FE frameworks in 3, 2, 1...
Re: Why VSCode doesn't use any front end framework
#4That makes sense for this type of application. But people are going to start complaining about React and other FE frameworks in 3, 2, 1...
So, use dynamic library hooks/tricks to provide api hooks to/for
Re: Why VSCode doesn't use any front end framework
#5A bit click bait, the answer is the obvious one: performance and independence.
Things that could have been a tweet (or tweet-sized blog post). But no, it’s a TikTok video on YouTube.
Re: Why VSCode doesn't use any front end framework
#6Building your own proprietary frontend framework still counts as a framework in my mind. Like how a custom tailored suit is still a suit, just one that is, well, tailored to spec. The whole "no framework" narrative is silly.
Re: Why VSCode doesn't use any front end framework
#7Building your own proprietary frontend framework still counts as a framework in my mind. Like how a custom tailored suit is still a suit, just one that is, well, tailored to spec. The whole "no framework" narrative is silly.
[deleted]
Re: Why VSCode doesn't use any front end framework
#8Erich Gamma, Technical Fellow, Microsoft: > 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 because performance is very important to us, and we want to be fully in control of our own destiny. So we don't want to chase a framework or track down performance from in the framework, we want to be directly as close to the DOM as possible.
Wow
Re: Why VSCode doesn't use any front end framework
#9Erich Gamma, Technical Fellow, Microsoft: > 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 because performance is very important to us, and we want to be fully in control of our own destiny. So we don't want to chase a framework or track down performance from in the framework, we want to be directly as close to the DOM as possible.
Got it...They want to control their destiny on UI ...But have no issues on everything else ...So they are ok with using Electron :-))
Re: Why VSCode doesn't use any front end framework
#10Building your own proprietary frontend framework still counts as a framework in my mind. Like how a custom tailored suit is still a suit, just one that is, well, tailored to spec. The whole "no framework" narrative is silly.
Is that the point here?
I think the key point about using someone else's framework is that it's someone else's framework, not that it's someone else's framework.