Lapce (IPA: /læps/) is written in pure Rust, with a UI in Floem. It is designed with Rope Science from the Xi-Editor, enabling lightning-fast computation, and leverages wgpu for rendering. More information about the features of Lapce can be found on the main website and user documentation can be found on GitBook.

• Built-in LSP (Language Server Protocol) support to give you intelligent code features such as: completion, diagnostics and code actions
• Modal editing support as first class citizen (Vim-like, and toggleable)
• Built-in remote development support inspired by VSCode Remote Development. Enjoy the benefits of a "local" experience, and seamlessly gain the full power of a remote system. We also have Lapdev which can help manage your remote dev environments.
• Plugins can be written in programming languages that can compile to the WASI format (C, Rust, AssemblyScript)
• Built-in terminal, so you can execute commands in your workspace, without leaving Lapce.

You can find pre-built releases for Windows, Linux and macOS here, or installing with a package manager. If you'd like to compile from source, you can find the guide.

The most popular place for Lapce developers and users is on the Discord server.

Or, join the discussion on Reddit where we are just getting started.

There is also a Matrix Space, which is linked to the content from the Discord server.

Lapce is released under the Apache License Version 2, which is an open source license. You may contribute to this project, or use the code as you please as long as you adhere to its conditions. You can find a copy of the license text here: LICENSE.

A lightweight comments widget built on GitHub issues. Use GitHub issues for blog comments, wiki pages and more!

• Open source. 🙌
• No tracking, no ads, always free. 📡🚫
• No lock-in. All data stored in GitHub issues. 🔓
• Styled with Primer, the css toolkit that powers GitHub. 💅
• Dark theme. 🌘
• Lightweight. Vanilla TypeScript. No font downloads, JavaScript frameworks or polyfills for evergreen browsers. 🐦🌲

how it works

When Utterances loads, the GitHub issue search API is used to find the issue associated with the page based on url, pathname or title. If we cannot find an issue that matches the page, no problem, utterances-bot will automatically create an issue the first time someone comments.

To comment, users must authorize the utterances app to post on their behalf using the GitHub OAuth flow. Alternatively, users can comment on the GitHub issue directly.

A comments system powered by GitHub Discussions. Let visitors leave comments and reactions on your website via GitHub! Heavily inspired by utterances.

• Open source. 🌏
• No tracking, no ads, always free. 📡 🚫
• No database needed. All data is stored in GitHub Discussions. 
• Supports custom themes! 🌗
• Supports multiple languages. 🌐
• Extensively configurable. 🔧
• Automatically fetches new comments and edits from GitHub. 🔃
• Can be self-hosted! 🤳

Note
giscus is still under active development. GitHub is also still actively developing Discussions and its API. Thus, some features of giscus may break or change over time.

How it works

When giscus loads, the GitHub Discussions search API is used to find the Discussion associated with the page based on a chosen mapping (URL, pathname, <title>, etc.). If a matching discussion cannot be found, the giscus bot will automatically create a discussion the first time someone leaves a comment or reaction.

To comment, visitors must authorize the giscus app to post on their behalf using the GitHub OAuth flow. Alternatively, visitors can comment on the GitHub Discussion directly. You can moderate the comments on GitHub.

Features:

• Lightweight comment widget, with i18n, dark mode.
• Email notification
• Webhook
• Easy to self-host
• Many integrations

Documentation

https://cusdis.com/doc

Community

Discord

FAQ

Compared to Disqus

Cusdis is not designed to be a complete alternative to Disqus. It's aim is to implement a minimalist and embeddable comment system for small websites (such as your static blog).

Given below are the pros and cons of Cusdis:

Pros

• Cusdis is open-source and self-hostable. Hence, you own your data.
• The SDK is lightweight(~5kb gzipped).
• Cusdis doesn't require your user to sign in to make a comment.
• Cusdis doesn't use cookies at all.

Cons

• Cusdis is on the early stages of its development.
• There is no spam filter, hence, you will have to manually moderate your comment section and comments won't be displayed until you approve them.
• Disqus is a company, we aren't.

Contributing

Contributing Guide

If you are going to make a PR, remember to choose dev as the base branch.

License

GNU GPLv3