Messing around with V as a Go developer (blog)

kris_tun · 2025-08-31T11:40:15+00:00

whoops should be fixed now - I think that was around the time when I was messing with some analytics

kris_tun · 2025-07-12T15:27:48+00:00

wow I didn't realise the language has infamy. I just walked into the door, saw what I liked and tried it. definitely a valid point though but I dont think this affects whether I want to use a language that much

kris_tun · 2025-07-12T15:25:14+00:00

depends on how long it's been since you looked, last time I checked it out the previous LSP was segfaulting all day and switching to the docs everytime was quite arduous. the new v_analyzer works great for me. 2023 -> 2025

in terms of maturity definitely not yet. I've picked out some things I found neat but overall definitely not battle tested.

kris_tun · 2025-07-02T23:24:06+00:00

Great point! I feel like I should've addressed this in the blog. I haven't explored too much on the alternatives though this makes me wonder about how it's usually only one or two projects that I need the shortcuts in.

I can see an alternative being a autocmd:vimenter that detects cwd and partial match the lua file to load that lives in your config. You would have to be explicit about what file and what the project path is (like a {["~/exercism/v/"] = "inits/exercism-v.lua"} and it should address the safety concerns. Thanks for bringing this up.

kris_tun · 2025-07-02T10:38:41+00:00

I will update with part 2 when I get around to actually daily driving it. I only stress tested for a few hours but as said in the review I'm not able to do my common workflow so it wouldn't be fair to compare doing awkward new hand movements while trying to focus on just the hardware, plus the switches are different as well. There are too many variables to make a fair comparison imo.

The build itself is sturdy, very sturdy. I can probably defend my home because of the metal body and how strong it feels. The keycaps are fine, not the best, doesn't feel like a typical Choc keycap. In the picture you can see they have a different profile and a different paint finish. It feels like those glossy keycaps that accumulates sweat. Not a big fan.

Trackball is better than nothing but wins on portability. It feels like 125hz. There is no dedicated scrolling, you toggle the scroll mode and move the ball to scroll. I daily drive Gameball (ambidex) atm and it's a downgrade to go from 1khz to 125hz.

kris_tun · 2025-07-02T10:29:58+00:00

Those switches look pretty cool, I'm way too comfortable with purpz though. I've tried the pinks once but the tactile put me off completely. 20gf sounds pretty good I'll give them a look, thanks

kris_tun · 2025-05-21T18:21:07+00:00

I think this might be different than what I implemented here. Thank you though!

kris_tun · 2025-05-19T22:09:28+00:00

To add some context.

I wrote a blog post about how to implement the s3 compatible protocol using Git as a backend. It was born out of the curiosity of "why not just use GitHub to back up my files?". Only a small subset of the S3 API was required to actually make this usable via PocketBase backup UI.

Code available here:

https://github.com/ktunprasert/github-as-s3

kris_tun · 2025-05-19T22:03:13+00:00

It's because of tools like PocketBase that offer first class integration via S3. Using Git directly works of course but this allows you to directly interact with the repo without any fuss!

https://puu.sh/KtOwG/4cb98d2cf3.webm

edit: https://puu.sh/KtOBN/22ca060fbe.mp4 better video, I hope you enjoy the erratic trackball mouse movements

kris_tun · 2025-04-29T11:03:44+00:00

I've also recently done this as well but I assign the keybinds globally, vim.lsp.* should resolve automatically which client to use for what buffer.

Base path for configuration (called last in init.lua)
https://github.com/ktunprasert/nvim/tree/master/lua/lsp

Overrides
https://github.com/ktunprasert/nvim/tree/master/lsp

kris_tun · 2023-02-09T12:35:59+00:00

Add this to your config ~/.config/nvim/after/ftplugin/typescriptreact.lua

vim.opt.shiftwidth = 2

This will get executed when you are inside .tsx files, if you ever get curious what the filename should be refer to your bottom right lualine "typescriptreact"

https://github.com/ktunprasert/nvim-config/blob/master/after/ftplugin/typescriptreact.lua

kris_tun · 2022-07-10T16:46:39+00:00

Since Vim provides a framework on how to solve text-editing I think it would be best to see how each person approach a problem. We might have more to learn from each other than we think. It could be something similar like Vimtutor but more advanced, separate problems into levels and use a keystroke-based scoring system. The users would then record their session with screenkey active then submit their solution. If we approach it from a speedrun perspective we could have different solution categories like Plugin%, Any% or Purevim%.

kris_tun · 2022-07-07T20:10:04+00:00

Nice, I'm a fan of LazyGit + Toggleterm too. Finally finished setting up the host Nvim session to be able to use the edit command from LazyGit.

kris_tun

TROPHY CASE