• 1 Post
  • 55 Comments
Joined 10 months ago
cake
Cake day: September 24th, 2023

help-circle
  • Neat, but I’d really like it to just handle memory properly without me having to tweak swap and OOM settings at all. Windows and Mac can do it. Why can’t Linux? I have 32GB of RAM and some more zswap and it still regularly runs out of RAM and hard resets. Meanwhile my 16GB Windows machine from 2012 literally never has problems.

    I wonder why there’s such a big difference. I guess Windows doesn’t have over-commit which probably helps apps like browsers know when to kick tabs out of memory (the biggest offender on Linux for me is having lots of tabs open in Firefox), and Windows doesn’t ignore the existence of GUIs like Linux does so maybe it makes better decisions about which processes to move to swap… but it feels like there must be something more?




    • Pijul: patch-based like Darcs but apparently solves its performance issues. In theory this improves conflict resolution.
    • Jujutsu: kind of an alternative front-end to a git repo (but not a front-end to git). Has some different ideas, like no staging area (draft commit), and some other stuff I can’t remember.
    • Sapling: from Facebook. Unfortunately only part of it is available. The server is not public yet (I guess it’s tired up in Facebook infrastructure too much).

    And it’s definitely not a solved problem. Aside from the obvious UX disaster, Git has some big issues:

    • Monorepo support is relatively poor, especially on Mac and Linux.
    • Submodule support is extremely buggy and has particularly bad UX even for Git.
    • Support for large files via LFS is tacked on and half-arsed.
    • Conflict resolution is very very dumb. I think there are third party efforts to improve this.

    I think the biggest issue is dealing with very large code bases, like the code for a mid-large size company. You either go with a monorepo and deal with slowness, Windows-only optimisations and bare minimum partial checkout support.

    Or you go with submodules and then you have even bigger problems. Honestly I’m not sure there’s really an answer for this with Git currently.

    It’s not hard to imagine how this might work better. For instance if Git repos were relocatable, so trees were relative to some directory, then submodules could be added to a repo natively just by adding the commits and specifying the relative location. (Git subtree almost does this but again it’s a tacked on third party solution which doesn’t integrate well, like LFS.)






  • They chose “version” because they are just that, versions. Improvements over the original design that benefit from new insights and technological improvements. We’re lucky they had the foresight to include a version number in the spec.

    No they aren’t. A higher version of UUID isn’t “newer and better”, like the word “version” implies. It’s just different. It’s like they called a car “vehicle version 1” and a motorbike “vehicle version 2”. The common use of “version” in the software world would mean that a motorbike is a newer and hopefully improved version of a car, which is not the case.

    The talking pumpkin is 100% right that they should have used “type” or “mode” or “scheme” or something instead.







  • I think you’re getting a bit confused. How do you know where x’s type is defined and therefore where x.bar is defined if you don’t know what type x is? It’s literally impossible. Best you can do is global type inference but that has very big limitations and is not really feasible in a language that wasn’t designed for it.

    Do you think that formatters for dynamic languages need to know the type in order to format them properly? Then why in the world would you need it to know where to jump to in a type definition!?!

    Not sure if that is a serious question, but it’s because formatting doesn’t depend on the type of variables but going to the definition of a field obviously depends on the type that the field is in.

    Maybe my example was not clear enough for you - I guess it’s possible you’ve never experienced working intellisense, so you don’t understand the feature I’m describing.

    class A:
      bar: int
    
    class B:
      bar: str
    
    def foo(x):
      return x.bar
    

    Ctrl-click on bar. Where does it jump to?





  • The kitty graphics protocol lets you send images to display in the terminal. I had a play around with it trying to make a similar GUI. The big gotcha is text rendering. You can either stick to normal grid aligned monospace, or I think you could maybe use a texture atlas, but it’s not going to be very efficient at all. I haven’t got as far as trying that though.

    The videos… while they work are probably uncompressed video which is only going to work well over a very fast network.