• Melkath@kbin.social
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    edit-2
    1 year ago

    I feel like we are “mirror images”, but not in a predictable way.

    Like, you get off on flying through languages having done things in said languages but never fully understanding any language and I get off on not needing a new language until I fully understand the one Im on, but LOVE informing you on the same tripwire you hit in each new language whilst I trip over that same thing in my language. Every. Time.

    I dont fancy you wrong, just not correct.

    I’d hope you’d fancy me not correct, but also not wrong.

    • Neshura@bookwormstory.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      flying through languages

      I wouldn’t excatly say I’l flying through languages. My migrations so far were these:

      C++ -> Rust: I learned C++ in Uni, I switched to Rust pretty quickly because I heard a lot of good things about it before I needed a compiled language in my free time

      Python -> Bash: sort of a regression but most of my projects using Python by now have been moved over to Rust because I value the stability it provides. Bash replaced the use cases for small things like turning off RGB before suspend and things like that. I looked at Python, tested out Bash and concluded that my experience would be better with Bash despite it being older and less user friendly

      Typescript + React -> Typescript + Svelte: I initially started out using NextJS and was growing frustrated with it, heard a lot of good about Svelte and decided to try it out on a smaller project. I quickly discovered that using Svelte increases my development speed and significantly reduces my headaches.

      That’s 3 switches in 4/5 years of developing things, most of these happened pretty early on as well. What I’m doing however is keeping an eye open in case something pops up that would suit my needs substantially better than what I already have.