Our great sponsors
-
NvChad
Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
google-search-results-nodejs
SerpApi client library for Node.js. Previously: Google Search Results Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Immature dev leading the project - merging broken code into master without code review, massive changes that requires every user to update their config with no discussion very frequently. No direction at all, it feels like every couple weeks there is a "configuration" change which just keeps going back and forth - a few examples: - 10 days ago, see comments: https://github.com/NvChad/NvChad/commit/d61946d3bfa304e8924120888611d64ee9f98f51 - 27 days ago, see comments, people trying to get code review comments in AFTER its already merged: https://github.com/NvChad/NvChad/commit/a6f2f0e0b92de561053681747c2d537cda1adf42 - 24th July, contradictory lspconfig 'improvement' to the config: https://github.com/NvChad/NvChad/commit/26fc9b5a6ce811a020c096922152e6e845fd0a3a - and so, so many more but I'd be writing this comment all day. Just browse the github, click on a few commits and issues - they are nearly all handled extremely immaturely, issues are closed with one-line responses etc.
I would throw out kickstart.nvim and suggest this as your base and override where required. LSP, LSP server installs, treesitter, completion, snippets, comments and a statusline, all in under 400 LOC
If you are interested in Ruby and web scraping, we are hiring at https://serpapi.com