• 0 Posts
  • 1.26K Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle




  • God yeah - this hits hard with me. I work in a place where the DRY principle is chanted like a mantra and I have to push back against it constantly. It’s like the one principle jr. devs learn (along with “never hardcode anything”) that just gets applied to everything whether it makes sense or not.

    "These lines of code are very similar, let’s factorize them ! "

    “We should take three simple functions that run similar (but different) things and make them call a single large complicated function that takes a parameter that tells it how to execute!”

    ::shudder::




  • Not only data science libraries, there is a library for about anything. Which is not the case for your list of languages.

    Java has an excellent ecosystem for libraries. And a much more mature one in most cases than Python. The Spring framework alone is simply amazing.

    Go’s ecosystem is pretty good as well and getting better.

    When you understand how python works, it’s quite simple to use too, and has lot less clutter than say java or c#.

    The problem is that many python devs consider things like “type hints” and “classes” to be “clutter”. It takes a lot of discipline to write managable python. Being “newb friendly” is a curse. “stringly typed” crap does NOT scale well.



  • I’m not sure how the *arr stuff works but hard links don’t let you “edit a file while preserving the original” - they let you have mulltiple paths to the same file.

    $ echo "hello" > file1
    $ ln file1 file2
    $ echo "world" > file2
    $ cat file1 file2
    world
    world
    

    Does *arr have some sort of copy-on-write behavior? Some modern file-systems have de-duping behavior and copy-on-write built in that you may be able to save some space with.

    But the point of topic 1 was to simplify. You can keep doing your hardlink stuff but standardize it and simplify setup/configuration. If you always do things in the same way it’s less complicated to keep track of and fix.

    You’ve understood the difference in terraform/ansible, and yeah terraform is probably not going to be as helpful. Ansible would be much more likely to help. It can seem burdensome to have to write configuration files for things at first, but it forces you to do things in a way that is standardized and repeatable.


    1. Simplify. You’ve made a system more complex than it needs to be. Copy files rather than working around hard link limitations. Use off-the-shelf backup solutions. Have a single file server with a known location for all your mounts. Etc.

    2. Automate. Not with bespoke bash scripts but with tools like ansible and terraform. These tools are built to help manage infrastructure and configurations.

    Everything is a file? Naah, everything is a hard link ! (Or inode? xD)

    Hard links are files…



  • atzanteol@sh.itjust.workstoLinux@lemmy.mlCosmic DE & Pop!_OS 24.04 BETA
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    1 month ago

    you’re already using a different DE than Pop comes with

    Pop comes with KDE/Plasma.

    I use PopOS because I have a System76 laptop. It runs well on my hardware. I’m allowed to complain about things without some shit telling me to just “use another distro”. If I wanted to run another distro I’d run another distro. Lordy…