Can I suggest dropping the sign up requirement and email verification to try it out?
Re:The POSIX specification of vi
by nickandbro on Thursday July 24, 2025 @04:56PM
(#44676018)
I agree! I am just working the containerization of the vim instances. Right now using k8, but wasting $$$ on infra. Moving to cloudflare containers to save that $$$ and make it more available. In the mean time, temporary email sites are allowed and not black listed.
Re:The POSIX specification of vi
by BipolarCapybara on Thursday July 24, 2025 @03:36PM
(#44675056)
Great site! I've been wanting to learn it for the past couple of weeks, but didn't have enough motivation to sit trhough tutorials. +1
Re:The POSIX specification of vi
by nickandbro on Thursday July 24, 2025 @04:05PM
(#44675395)
Thank you! It’s an unfinished project of mine. Still looking at adding more levels and allowing users to upload their own.
I learned vi(m) using https://vim-adventures.com/. It's $25 US for a 6-month license, which is a bit short. But I felt I got my money's worth out of it and continue to use and love vi(m) to this day.
Re:The POSIX specification of vi
by nickandbro on Thursday July 24, 2025 @04:05PM
(#44675382)
Big fan of vim adventures too! It definitely gamifies the learning of vim. Mine is more for the vim enthusiast who want to measure up against other vim power users.
Once you're the slightest but comfortable navigating vi, I highly recommend Practical Vim. [0] It tooke me a few days to get through, but I'm 100% in vim these days and more effective in it than in my old primary editor PyCharm.
[0]: https://pragprog.com/titles/dnvim2/practical-vim-second-edit...
Marvellous!
:w<CR> should count the same as ZZ for the purposes of hiding better solutions, else it's fairly easy to walk up the leaderboard even though the better solutions are ostensibly hidden.
Re:The POSIX specification of vi
by nickandbro on Thursday July 24, 2025 @06:23PM
(#44677035)
Thanks, appreciate the feedback
https://vimgolf.ai
because I like vi so much. Although the app uses neovim underneath the hood because it had an easier API to work with.