• 0 Posts
  • 8 Comments
Joined 1 year ago
Cake day: June 28th, 2023
  • sarjalimtoProgramming@programming.dev•NodeJS vs Go
    13•10 months ago

    As someone else already said, don’t overthink the language choice aspect in general. If you learn almost any imperative language with C-like syntax (Go, JS/TS, C#, Java etc), picking up another one in the same “family” to a usable degree will be a very minor hiccup done within a very short time (hours). Sure, there are quirks and special syntax and different collections of built-in features for each one, but as a developer you will likely switch between several anyway and need to look up syntax from time to time - you know that something can be done, but the details how are a bit fuzzy.

    For instance, I code mostly in C# and JS/TS, but we have legacy applications written in VB.NET so I often google VB syntax for things that I know how to write in C#. I also occasionally code in C, have dabbled in Fortran, Python and PHP and I’m sure I’m forgetting one or two. SQL and LINQ syntax too of course. What you learn on your developer journey is that something can be done, but remembering the specific implementation in a specific language might be a job better suited for your search engine. That said, of course it’s good to start with one language that you know pretty well, but it seems like you’re already there with Python.

    The real challenge is learning the methodology of building applications, philosophy of OOP, patterns and program/application architecture and frameworks. Language choice is very much secondary to those areas of expertise imo.

    Personally though, I am partial to JS/TS as I’ve used those the longest, they are extremely versatile and frontend development is my favorite area.

  • sarjalimtoProgramming@programming.dev•BEM methodology is not about CSS
    3•11 months ago

    I’m honestly not necessarily a BEM fan as class names become literally huge if you don’t rely a bit on nested elements (targeting nested classes is not very BEMmy - but SASS makes it so convenient). But haven’t found a naming convention or “framework” that does the job better. BEM also doesn’t address how you should organize the style library for maintainability. I just use my own simplified structure based on ITCSS now.

    I just wish that someone could make a methodology or an architecture of building style libraries that felt obvious and was more plug-and-play, I hate that I feel like have to revisit the style library organization and naming convention for each new project to reevaluate if it makes sense for the scope of the project.

    Then again, I work as a fullstack dev in a small team of more backend-focused fullstack devs, so I don’t do frontend as often as I’d like and don’t really have anyone to discuss these issues with.

  • sarjalimtoSelfhosted@lemmy.world•Help needed configuring prowlarr with qBittorrentEnglish
    6•11 months ago

    If I understand correctly (and I’m not 100% sure I do), localhost in a Docker container lives in it’s own little network which is not the host’s network.

    The container is its own localhost, which has its own ports (which is why you have to map an internal localhost port to a host PC localhost port for every container you wish to access). This means that Prowlarr in your case, has no idea what localhost:4666 should be since in Prowlarr’s localhost universe there exists nothing on that port. To access what the host knows of ports (instead of the container), you have to write the host’s address from inside the Prowlarr container.

    I hope that wasn’t impossible to follow 😅

    Now that I think about it (haven’t tried myself though) you could possibly add the mapping of port 4666:4666 to the Prowlarr Docker compose setup and then use localhost:4666 to access qBittorrent from inside Prowlarr.