I'm interested in creating an AI-integrated IDE with some unique features, but I'm not sure where to even start. I'm contemplating whether I should fork VSCode or build something from scratch. What do you all think would be easier? If I decide to fork VSCode, what should I focus on learning about it? Any advice or guidance on the overall process and what I might expect in terms of time and complexity would be greatly appreciated!
2 Answers
Just remember that VSCode has been developed by a ton of really skilled engineers over several years. If you want to understand the complexity, try contributing to the main VSCode project on GitHub. You’ll quickly realize how challenging it can be to work on such a large codebase. It's an eye-opener and a good way to gauge your skills!
Forking VSCode is definitely the easier path since it's already built and most of the heavy work is done for you. The tricky part comes when you need to add features like IntelliSense or AI integration if you're starting from scratch. I suggest forking VSCode and diving into its codebase to see how it functions. Another option is to build extensions for VSCode; it can be a fun way to learn the system! Remember, creating a text editor isn't too complex, but features like debugging and language support add a lot of complexity. Good luck, and enjoy the learning journey!
Absolutely! Building a text editor can be straightforward, but adding advanced features can turn it into a massive project.
I think making extensions first will help you get familiar with how VSCode works. It's like modding a game—way more fun than just reading through code!
So, is forking VSCode going to be just as tough as contributing to it?