Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)VA
Posts
2
Comments
39
Joined
2 yr. ago

  • Same. I've had a few big config purges and migrations every few years, but I'm always neovim.

    I started using Neovide as a frontend so people could follow what I'm doing (it adds animated cursor movement, etc.) I actually found that I really like it and rarely use a terminal to run neovim now.

  • My experience may be dated, but I've always had issues with controllers on Windows and Linux. Less so with Linux these days because my controllers are dated and the drivers are in the mainline kernel.

    The biggest issue was solved with steam and it's controller interface / community layouts.

  • One of the goals of neovim was to introduce tools to build a GUI around vim. Imo the terminal is by far the best option, but there are some fun options. Neovide is an interesting one. Mostly because it doesn't do too much -- just eye candy.

  • It's going to be a lot smaller since it doesn't bundle a version of chromium in every build. Instead it uses the systems native web view. This does pose the problem of vendor specific rendering issues.. How snappy it feels is down to how the front-end programmed. It can still be a mess of bloated JavaScript 🙂

  • I always just use zsh with oh my zsh. Best of both worlds.

    One thing that I still don't know how to do is go to the next result in the search with Ctrl+r. Makes it less useful lol

  • Prioritizing developer experience is not the reason we use front-end frameworks. People expect the web to work like a desktop app (no page reloads). The initial request might take a little bit longer, but in the end a well written front-end app will feel faster.

    The problem is that people don't worry about bundle size and cram every library off of npm into their website.