Independently building at night
- Flotes · Markdown Note-taking Built for Learning
- Tomatillo Timer · Study timer that syncs to music
- Better Commits · CLI to make conventional commits
Learning cryptography by making a little CLI that can encrypt/decrypt stuff can feel quickly rewarding.
Compared to making a note-taking application that uses E2EE, where you might spend half your time lost in the details of the note-taking app, and not learning cryptography.
Learning cryptography by making a little CLI that can encrypt/decrypt stuff can feel quickly rewarding.
Compared to making a note-taking application that uses E2EE, where you might spend half your time lost in the details of the note-taking app, and not learning cryptography.
If it's learning through application. Go small but mighty.
- A plugin to an app/editor can do a lot with a little code.
- A CLI lets you focus on the core and not how it looks.
- A small library can solve sub problems in big apps.
If it's learning through application. Go small but mighty.
- A plugin to an app/editor can do a lot with a little code.
- A CLI lets you focus on the core and not how it looks.
- A small library can solve sub problems in big apps.
- Do things you didn't realize/expect
- Break when you update
Extras have great docs, if anything just use as a reference.
- Do things you didn't realize/expect
- Break when you update
Extras have great docs, if anything just use as a reference.
Create a folder /after/lsp/ in your run time path.
Start with a copy paste of the language server you want from here: github.com/neovim/nvim-...
call vim.lsp.enable('your_language_server_name') on startup
go to a filetype for that ls, run: checkhealth vim.lsp ✅
Create a folder /after/lsp/ in your run time path.
Start with a copy paste of the language server you want from here: github.com/neovim/nvim-...
call vim.lsp.enable('your_language_server_name') on startup
go to a filetype for that ls, run: checkhealth vim.lsp ✅
So many questions.
- Why not?
- What should I use instead?
- When is it okay to use?
Most of the time we say "Don't do X", but don't provide alternatives, exceptions, why, etc... I think it creates more confusion than clarity.
So many questions.
- Why not?
- What should I use instead?
- When is it okay to use?
Most of the time we say "Don't do X", but don't provide alternatives, exceptions, why, etc... I think it creates more confusion than clarity.
Buuut I don't think it comes off that way to many readers 😅.
Buuut I don't think it comes off that way to many readers 😅.
"Don't use effects" is a frequently repeated and upvoted statement that provides no alternative. - Exhibit A, it took 2 months for this post to get a reply lol
"Don't use effects" is a frequently repeated and upvoted statement that provides no alternative. - Exhibit A, it took 2 months for this post to get a reply lol
Definitely looking to switch back to a custom setup when I get the chance!
Definitely looking to switch back to a custom setup when I get the chance!
Svelte-Language-Server 0.17.19
I'm also using LazyVim with the Svelte LazyExtra. This is actually a whole other issue. Without it, changing TS files does not reflect changes in Svelte files. With it, big svelte projects crash the ls. 😭
My svelte lsp setup: github.com/Everduin94/d...
Svelte-Language-Server 0.17.19
I'm also using LazyVim with the Svelte LazyExtra. This is actually a whole other issue. Without it, changing TS files does not reflect changes in Svelte files. With it, big svelte projects crash the ls. 😭
My svelte lsp setup: github.com/Everduin94/d...
Too many ideas, not enough time 😅
Too many ideas, not enough time 😅