LiteIDE
language-server-protocol-inspector
LiteIDE | language-server-protocol-inspector | |
---|---|---|
7 | 1 | |
7,453 | 150 | |
- | - | |
5.8 | 0.9 | |
4 months ago | about 3 years ago | |
C++ | Vue | |
GNU Lesser General Public License v3.0 only | 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.
LiteIDE
-
What's the most commonly used IDE for golang development ?
Not common, but worth a mention: I've been using LiteIDE (https://github.com/visualfc/liteide/releases/latest) since Atom + Go dev ceased development.
-
Open Source IDE for Linux
There is liteide too: https://github.com/visualfc/liteide Is not super amazing but it does the job and since is purely for Go it has a few nice features. And it's very lightweight!
-
What is wrong with VSCode IntelliSense for GO?
I mostly use VS Code, too (or rather VSCodium), but also recommend you try LiteIDE as it's exceptionally fast.
- What IDE‘s are you guys using?
- Is it worth learning Golang using VS code?
-
CodePerfect 95 – A fast IDE for Go
If this is the kind of thing you are interested in, I would strongly recommend LiteIDE:
http://liteide.org/en/
https://github.com/visualfc/liteide/releases
It's actively developed, FOSS (LGPL), native C++ (Qt), runs on Windows/macOS/Linux, supports go.mod, and uses gocode/gotools for intellisense instead of gopls. It has integrated debugging, go to definition/usages, and some refactoring support.
-
The best free IDE for Go
"technically" https://github.com/visualfc/liteide as that's an IDE
language-server-protocol-inspector
-
CodePerfect 95 – A fast IDE for Go
I wonder if these performance issues apply to all language extensions that rely on a language server (implemented in VSCode or otherwise). From what I understand, since JSON [0] is used over the wire between the editor and the language server process, there's a lot of serialisation/deserialisation overhead.
Microsoft used to maintain a log inspector [1] which you could use to see the chatter between the server and client, and there was a _lot_ of chatter with a _lot_ of JSON.
[0] https://microsoft.github.io/language-server-protocol/overvie...
[1] https://github.com/microsoft/language-server-protocol-inspec...
What are some alternatives?
vscode-go - Go extension for Visual Studio Code
lintplus - An improved linting plugin for the lite text editor.
snap - The open telemetry framework
lite - A lightweight text editor written in Lua
limetext - Open source API-compatible alternative to the text editor Sublime Text
language-server-protocol-inspec
toxiproxy - :alarm_clock: :fire: A TCP proxy to simulate network and system conditions for chaos and resiliency testing
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
restic - Fast, secure, efficient backup program
Docker - Notary is a project that allows anyone to have trust over arbitrary collections of data
Comcast - Simulating shitty network connections so you can build better systems.
Hugo - The world’s fastest framework for building websites.