• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle


  • There are far more factors determining wrist position than the size of the keyboard

    Ergonomic keyboards are not a result of “the size of the keyboard”, but the shape. The size could be identical, it is the shape that matters.

    Without any real studies on it mentioned so far you’re relying on gut feeling and logic here. Well, you mention sitting with proper posture actually helps, which is putting your body into proper alignment. That makes sense, if your neck is arched and your back is crunched all day it will eventually cause damage to your discs and cause nerve pain.

    Why doesn’t the same apply to your wrists? It seems logical that keeping your wrists cockeyed all day would put strain on them, and that keeping them in alignment would reduce strain.

    At the very least it seems easy to see why some people would genuinely prefer keyboards like that just for comfort. I find it hard to label as “snake oil”






  • Vscode is beginning it’s enshittification cycle. They got everyone using it, now they start locking it down. Much of the fear is what Microsoft could do, not so much what they have done so far

    The C# extension going proprietary is the smoke to the coming fire though, and highlights what could happen to other languages. The new extension cannot be installed on open source redistributions like vscodium. What happens now if the typescript extension gets a similar update? Or Python? Etc.

    They’ve made it so technically anyone can spin off their own extensions marketplace, and attempt to make their own C#/typescript/Python extensions, but can they truly compete with Microsoft? That is the fracture the author is talking about. They’ve effectively made a walled garden out of an open source platform, they’ve just been playing nice to hook devs and companies in before the slow enshittification





  • They provide a link to the section where they elaborate on “commit first vs test first”, here is the relevant text

    Instead of jumping straight to the commit step, Fossil applies the proposed merge to the local working directory only, requiring a separate check-in step before the change is committed to the repository. This gives you a chance to test the change first, either manually or by running your software’s automatic tests. (Ideally, both!) Thus, Fossil doesn’t need rebase, squashing, reset --hard, or other Git commit mutating mechanisms