I’m not a bot.

  • 15 Posts
  • 172 Comments
Joined 8 months ago
cake
Cake day: January 21st, 2025

help-circle


  • most things work out of the box now, especially on GNOME/Plasma

    I don’t want my system to work 67% of the time. If my wifi card worked most of the time, I wouldn’t be happy. I’d like a 100% working system. This isn’t my first experience with HiDPI. I owned a Framework and returned it because it required fractional scaling and too many of the apps I use were either blurry or tiny. For me personally, that’s a dealbreaker. I understand other people would make that trade off though.

    I 100% always attribute hidpi experience to the hardware. It’s a bad choice hardware manufacturers make.

    • Should we only include a hidpi display? Something that we know before hand will definitely cause issues?
    • Should the hidpi display be some weird resolution that will require fractional scaling? Something that again has a huge and well known history of not working well?

    It’s easier for 1 hardware manufacturer to pick a Linux-compatible display, rather than expecting millions of individual devs around the world to update their apps to the latest GTK/QT/Wayland frameworks.

    Even if you’re pro-HiDPI displays, you should totally blame the laptop manufacturers for not picking a display resolution that allows integer scaling. You’re missing out. It’s a way better experience.

    what prompted you to buy this laptop in the first place

    I wanted to buy a Linux laptop because I thought it would be more compatible with Linux. I tried System76, but didn’t like the build quality. I’ve previously used Dell XPS 13 and Lenovo X1 Carbon, both of which I like (and have excellent Linux support (and offer standard dpi displays)). Coreboot was another reason, I like that it’s open source. I also thought Coreboot would boot the laptop faster since it has less bloat, but that didn’t really pan out.










  • Some very quick, superficial differences:

    • ast-grep uses tree-sitter for understanding languages

    • ast-grep is written in Rust

    • ast-grep uses YAML for config

    • ast-grep more normal --flags

    • comby doesn’t use tree-sitter and does it’s own thing… not sure what to think of this approach

    • comby is written in OCaml

    • comby uses TOML for config

    • comby uses -single-dash-flags

    • both have online playgrounds for testing

    I personally hate YAML, so it’s comby for me! (For now.)

    Also, here’s what Comby says about its approach to matching: https://comby.dev/docs/faq

    Underneath the hood, Comby uses no tree definition, but turns patterns into an executable routine (a language-aware parser) where the tree structure is implicit in this executable routine. In theory, the syntax matched by this routine could dump a serialized parse tree, but this isn’t implemented :-). With this design, Comby sacrifices this ability to recognize many predefined language constructs in order to support a more freeform pattern writing and matching process. This loses precision for deeply recognizing all of a program’s structures, and may fall short of your needs depending on your use case.




  • IDE users pretending compilers don’t exist.

    $ guix shell gcc
    
    [env]$ g++ test.cpp 
    test.cpp:4:16: warning: `0;' is not in NFC [-Wnormalized=]
        4 |         return 0<U+037E>
          |                ^~~~~~~~~
    test.cpp: In function ‘int main()’:
    test.cpp:4:16: error: unable to find numeric literal operatoroperator"";’
    test.cpp:4:18: error: expected ‘;’ before ‘}’ token
        4 |         return 0;
          |                  ^
          |                  ;
        5 | }
          | ~
    

    Look ma, no IDE! 😸











  • Many of them don’t even allow it to be a hidden file—they just require a fully unhidden “tool.yml” file sitting right there in the root of your project.

    I love this. I hate when tools only allow hidden config files. I want to know where the config is—my teammates should be aware of where the config is. I don’t want to be tricked into thinking there isn’t a config file in a directory.

    I actually have alias ls='ls -A' in my bashrc so I see everything.