• 2 Posts
  • 120 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2024

help-circle




  • I’ve distro hopped from Debian, to NixOS, to Arch Linux. The neat thing about NixOS is that 99% of the system and user configuration was spread out across a handful of manageable files. And it was only multiple files because I modularized them; it could’ve been a single file. Localizing the configuration made it easy to wrap my brain around it.

    I’ve lost track of what I’ve configured on Arch. I could’ve been more diligent and kept track but NixOS is more conducive to that from the getgo.

    Another neat thing is that nixpkgs (the NixOS package repository) has everything, close enough for me anyway. In one place. I’m already relying on the AUR (a separate repo from the core Arch ones) and all that entails. NixOS (nixos-unstable) is also more bleeding edge than Arch if you’re into that sort of thing (I am).

    The entirety of your configuration being in one (esoteric, but simple) language was also neat

    It wasn’t without its downsides but I had fun with it. I totally get the hype.








  • Ah, interesting. I haven’t kept up with the newest Java changes, so you kind of answered that backwards for me. Being able to just use IO.println() is already pretty good and for sure what I’d prefer over having to add an import. Seems to also be a new addition in Java 25, so I guess, Hello World looks a lot different all of a sudden.

    My code was merely a demonstration that just println is possible now. Like you, I’d prefer IO.println in “real” code. My bar for static imports is extremely high.

    Also interesting that this kind of static import doesn’t work with System.out.println, I’m guessing because out is already a field of System rather than a package or type. It can be used to write it as out.println, but yeah, not much of a point anymore when IO.println exists.

    Static imports are only for static fields and methods. System.out::println is an instance method.