vscode-cpptools
vscodium
vscode-cpptools | vscodium | |
---|---|---|
66 | 547 | |
5,518 | 25,329 | |
0.3% | 1.3% | |
9.2 | 9.2 | |
7 days ago | about 22 hours ago | |
TypeScript | Shell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-cpptools
-
Visual Studio Code is designed to fracture
Its close in spirit to DRM. They want to ensure that if you are using their projects, it must be under their terms.
Many of their VS Code extensions[0] have license terms which /prohibit/ them from being used in editors that are not Microsoft's VS Code editor, and Microsoft can issue cease-and-desist for violation of this or use of their extension marketplace in alternative editors.
Microsoft has a pattern they follow where they publish repositories on GitHub to proclaim they are open source, while actually distributing proprietary binary blobs in them that are fundamental core parts of functionality to the codebase[2][3][4]
[0] https://github.com/microsoft/vscode-cpptools/issues/6388#iss...
[1] https://github.com/microsoft/vscode-cpptools/issues/5784
[2] https://github.com/microsoft/win32metadata/issues/766
[3] https://devlog.hexops.com/2024/building-the-directx-shader-c...
[4] https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/...
-
Linux Mint Disabling Unverified Flatpaks by Default
The C/C++ extension is open source with MIT license but the shipped extension binary contains MS proprietary binaries that is not as open [1]. I am not sure what will be the difference between using MS official build and compiling the source (there will be some for sure).
[1] https://github.com/microsoft/vscode-cpptools/blob/main/LICEN...
-
Xmake: A modern C/C++ build tool
Now if only MS would fix VSCode[0] :'(. Come on, the feature if more than half a decade old and this point.
0: https://github.com/microsoft/vscode-cpptools/issues/6302
-
🚀 Exciting New Feature Proposal for C++ Developers: "Add Similar Function" in IntelliSense! 🚀
🔗 Link to GitHub Issue: Add Similar Function - https://github.com/microsoft/vscode-cpptools/issues/11477
-
How to enable pretty printers?
According to this: https://github.com/microsoft/vscode-cpptools/issues/3423 it seems to be at least somewhat possible to reuse natvis files from Visual Studio, but I have not tested that. Never really had the need to look at any non-vector container in the debugger.
-
How to Debug C/C++ with Visual Studio Code (From a Microsoft Software Engineer)
Thank you for the feedback! Perf is always an ongoing issue for us but I can say that we’ve recently allocated one of our senior engineers to take on more perf related issues. Something that really helps us out is if you could file reproducible steps that lead to your performance issue. This allows us to address the issues more readily. Please file your issues here: https://github.com/microsoft/vscode-cpptools/issues
-
How to Setup VSCode for C/C++ Programming (From a Microsoft Software Engineer)
Yes, see this github issue for an example: Add Ada to supported languages for debugging · Issue #10475 · microsoft/vscode-cpptools (github.com)
-
Me after trying to use Git with Eclipse
Nope https://github.com/microsoft/vscode-cpptools/issues/16
- [Vscodium] L'extension C / C ++?
- εχει τρεξει κανεις cuda σε visual studio code ;
vscodium
-
Visual Studio Code vs. Sublime Text: Which code editor should you use?
Vscodium for me
binary releases of VS Code without MS branding/telemetry/licensing
https://github.com/VSCodium/vscodium
-
Microsoft is introducing hidden APIs to VS Code only enabled for Copilot
> Visual studio is open source
Sort of. The core is, and the installable binaries with telemetry and properietary extensions are not.
The open source, telemetry-free version of VSCode is called VSCodium: https://vscodium.com/
> Didn't cusor fork it and is building it features directly into the fork?
Yes, in their recent interview with Lex Fridman they argued that life as an extension is too limiting.
The main reason we criticise Microsoft for doing this and not them is just their size and market dominance.
Why jump through hoops to make competitors better able to hotwire their own AI into VSCode, or hotwire Copilot into their own IDE, when it's easier to iterate fast and remain unpredictable?
-
Visual Studio Code is designed to fracture
> If you enjoy a rabbithole, look at how much DRM there is in Pylance (another extension that MS has locked down): https://github.com/VSCodium/vscodium/discussions/1641
The funny thing is that I’ll never understand why it’s not open source and why its license prohibits its use in VSCodium. Pylance is good, but not that good. Certainly not on a level of PyCharm. What incentive do they have to keep it secret except being evil?
-
Forget ChatGPT: why researchers now run small AIs on their laptops
If you're gonna go with a VS code extension and you're aiming for privacy, then I would at least recommend using the open source fork VS Codium.
https://vscodium.com/
-
How to install VSCode/VSCodium?
Go to the VSCodium website.
- Migrating from DokuWiki to Obsidian
- Open Source 'Eclipse Theia IDE' Exits Beta to Challenge Visual Studio Code
-
Maker of RStudio launches new R and Python IDE
This looks great, combining the best of VSCode and RStudio.
I prefer coding in VSCode but prefer data exploration in RStudio.
The only issue with this is the lack of copilot. Copilot can be installed on VSCodium [1] but it breaks often.
[1] https://github.com/VSCodium/vscodium/discussions/1487
- Windows 11 is now enabling OneDrive folder backup without asking permission
-
Validate your Jenkinsfile with the vscode plugin vscode-jenkins-pipeline-linter-connector and the LLMs large model
The plugin is now available in the Visual Studio Code Store and Open VSX Registry, and you can theoretically use it in Microsoft Visual Studio Code, code-server, VSCodium, and other vscode series IDEs, linked below:
What are some alternatives?
CodeLLDB - A native debugger extension for VSCode based on LLDB
Code-Server - VS Code in the browser
vscode-clangd - Visual Studio Code extension for clangd
Visual Studio Code - Visual Studio Code
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
Visual Studio Code - Public documentation for Visual Studio Code
nvim-dap - Debug Adapter Protocol client implementation for Neovim
pylance-release - Documentation and issues for Pylance
Bear - Bear is a tool that generates a compilation database for clang tooling.
theia - Eclipse Theia is a cloud & desktop IDE framework implemented in TypeScript.
vscode-clang-format - A Visual Studio Code extension that provides C++, C, Obj-C, Java formatting with the use of clang-format
lapce - Lightning-fast and Powerful Code Editor written in Rust