bellsDoSing

@bellsDoSing@lemm.ee

• ⁨Comment⁩ on ⁨Logitech has ‘no plans’ for a subscription mouse⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  Have you ever learned about the following in VIM:

  • H, M, L, 22H, …,: vertical cursor placement
  • zt, z0, zb: vertical scroll positioning
  • 0, $, gm, gM: horizontal cursor placement
  • w, e, b: word based cursor movement

  Simply holding j or k at times also works, even more so with a decently high key repeat rate.

  Of course there’s a lot more: vimhelp.org/motion.txt.html

  The trick is to only learn a couple new movement mappings at a time and use them during one’s workflow for a while, up until they feel ingrained. Then repeat, iteratively building up one’s movement skills in VIM.

  One can say many things about VIM, but not that learning it’s movement mappings will make your required APM (let alone mouse clicks) go up to “get stuff done”. Honestly, once a basic set of these movements has been learned, any other editor without them will feel like a drag.

• ⁨Comment⁩ on ⁨What Would You Like To See Improved in GNU/Linux?⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Depends on the specific plugin. I’ve been doing music production on Linux for several years now. Back then things looked a lot worse than now. Most popular bridge solution for Windows plugins on Linux is yabridge atm. The README is well worth a closer read, cause it will answer many questions on how to get even more modern plugins to display correctly (i.e. JUCE based ones).

• ⁨Comment⁩ on ⁨GitHub Desktop or Git CLI?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  And it will find you the most answers online in case you have a git related question.

• ⁨Comment⁩ on ⁨How to access all files in docker volumes for backups?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  You didn’t mention how big those volumes are and how frequently the data changes.

  Assuming it’s not that much data:

  • use tar to archive each volume first, while using proper options to preserve permissions and whatever else is important for your usecase
  • use restic to backup those archives
  • use a proper pruning strategy to not let your backups get too big:
    • I’m not that familiar with restic, but maybe you can backup those archives separately and apply a more aggressive pruning strategy just for them
    • simply might be needed, cause deduplication (AFAIK) might not be that great with backing up archives
    • but maybe if the volume data and the resulting archive doesn’t change that often, deduplication would be sufficient even with a not so aggressive pruning strategy
• ⁨Comment⁩ on ⁨A lot of YAML⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Yeah, such a simple, but still killer feature. Really sad that JSON doesn’t support them.

• ⁨Comment⁩ on ⁨Unity May Never Win Back the Developers It Lost in Its Fee Debacle⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Nobody can tell you in advance how far your interest in game dev will take you. Only one way to find out: start small (some tutorials, build some crappy first) and see if your interest sticks around as you up the challange.

  Maybe game dev in Godot will end up being a significant chapter in your life, maybe it will just be a small sidequest. But once you’ve given it an honest try, no matter the outcome, you at least will know if it’s something for you or not. That in itself is already worth something.

  And who knows: maybe Godot is just your entry gateway to something else you discover along the way, which you wouldn’t have discovered if you hadn’t taken on the challange in the first place.

• ⁨Comment⁩ on ⁨OC: Me since Bun 1.0.0⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  To add, edge functions (powered by deno) are one of the bigger pain points of supabase. At least that’s my own practical experience and the experience of quite a few others on their github (discussions and issues).

  In my current project, I started of optimistically (“Should be doable, they say you feel right at home coming from nodejs!”), tried rewriting some existing nodejs code and use edge functions just like your average nodejs powered serverless functions.

  But in the end, things just didn’t work out:

  • deno’s crypto module just wasn’t up to scratch yet re nodejs compatibility (for my rather humble needs)
  • supabase uses –no-npm flag re its use of “deno deploy runtime”, which means node: specifiers for imports aren’t supported
  • the fact that unlike for serverless functions, which update their runtime only once you yourself trigger a new deployment (e.g. nodejs on vercel), “deno deploy runtime” is continously being updated to latest version, which to me still feels pretty strange for production use, considering how serverless functions handle runtime updates.

  In the end I changed my architecture yet again, moved most of the code to an expressjs backend and only use edge functions as a kind of “tender” proxy layer with minimal dependencies (mostly just deno and some esm.sh imports; e.g. supabase-js).

  Don’t get me wrong, supabase overall is a great thing and they do many things well! I’m still using them going forward. But edge functions just have the potential for being such a pain point in a project and many have already wished for also having the option for “classic” serverless functions.

• ⁨Comment⁩ on ⁨Every Single Freaking Time⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I additionally mapped that latter one to F2, because being able to repeatedly copy from VIM and paste into another application without having to move your hand between mouse and keyboard is nice.

  Of course, that’s VIM. If you meant “vim mode” in shell, then that’s a different story.

• ⁨Comment⁩ on ⁨Bram Moolenaar Has Died⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Yeah, truely! There’s plenty of “data written” that will outlast beyond his “departure”.