Explore >> Select a destination
|
You are here 
|
iftheshoefritz.com | ||
| | | | |
honeypot.net
|
|
| | | | | LSP lets editors compete on usability, not just languages. | |
| | | | |
cullmann.io
|
|
| | | | | The Language Server Protocol (LSP) allows the integration of stuff like code completion, jump to definition, symbol search and more into an application without manual re-implementation for each language one wants to support. LSP doesn't fully allow an integration like KDevelop or Qt Creator do with the libclang based tooling aimed for C/C++ but on the other side offers the possibility to interface with plenty of languages without a large effort on the client side. | |
| | | | |
selfhostedheaven.com
|
|
| | | | | What is a Port? In networking, a port is a communication endpoint. A port is normally tied to a specific process on your computer or server. It allows you to distinguise different kinds of traffic to a specific address. You can kind of see it like letters send to a specific person in a household: in networking different ports are for a specific application or service. | |
| | | | |
briankung.dev
|
|
| | | I realized that one of my favorite Rust features doesn't have a blog post highlighting it [0], so I thought I'd talk a bit about documentation comments and doc tests in Rust. I'll give you a quick example. Let's say you have some code: There's a cargo command to generate documentation from that code: Which... | ||
