Personal views on several IDEs

(Note: This article only expresses personal opinions. In fact, several IDEs in this article have different functions and cannot replace each other. The programs on the screenshots have been released)

I personally think that an IDE should be easy to operate under the premise of complete functions. In addition, the compatibility with zoom will also affect the look and feel. The following is an analysis of several IDEs I have used.

1.Visual Studio (currently not used, no screenshots)

I have learned C language in computer class before, but because I can't remember the process of building a new project, I found another video tutorial. The IDE used in the video is Visual Studio. I personally feel that Visual Studio prefers the management of projects with multiple files. For projects with a single file, the process of creating a new project is more complicated. Visual Studio's compatibility with scaling is fine. Another problem is that functions such as scanf() are deprecated, causing inconvenience to development. Later, it was found that the trial version was installed, and it was replaced by Code Blocks when it expired. Later I learned that the community version of Visual Studio is free, but since I have changed the IDE, I did not switch back to Visual Studio.

2.Code Blocks

The main advantage of Code Blocks is that it can directly open and run .c files, which is convenient for developing programs of a single file; it also provides the function of managing programs composed of multiple files. However, it is said that Visual Studio is more widely used in large-scale projects. Since I have not developed large-scale projects on PCs, I will not comment on this aspect for the time being. Code Blocks is generally not compatible with zooming, and the interface will be blurry.

3. VS Code (because it is installed in another system, no screenshots for now)

I use VS Code mainly to develop ROS programs. VS Code uses CMake for project management. Although it is highly versatile, the configuration process is relatively complicated. In actual use, there may be situations where the operation is OK but the compilation cannot be performed. VS Code has good zoom compatibility and a clear interface.

4. Cone5

 

 I use Keil5 to develop stm32 programs. Keil5 has a built-in function of managing multi-file projects, but it is still troublesome to add files when there are many files. Keil5 is generally compatible with zooming, and the interface is blurred when zooming.

5.Thonny

 

I use Thonny to develop Python and MicroPython programs. Thonny is easy to operate, you can directly open the .py file, you only need to add the corresponding code when importing the file, no additional import steps are required. Thonny has good compatibility with scaling and a clear interface.

Conclusion:

The IDE has a significant impact on the development experience. In my opinion, an ideal IDE should open files directly, import files directly using include/import statements (C/C++ should also use this method to determine the inclusion relationship of files), run programs with one click, and be compatible with zooming.

Guess you like

Origin blog.csdn.net/weixin_74155302/article/details/131186117