• abhibeckert@lemmy.world
    link
    fedilink
    arrow-up
    27
    ·
    edit-2
    10 months ago

    Currently the obvious tell is if they pitch Rust

    I would amend that to “if they pitch any language”.

    The best language is almost universally “whatever we already use” or for new projects “whatever the team is most familiar with”. It should occasionally be reconsidered, and definitely try out new languages, but actually switching to the new language after trying it out? That should be very very rare.

    • stevecrox@kbin.run
      link
      fedilink
      arrow-up
      10
      arrow-down
      4
      ·
      edit-2
      10 months ago

      The team/organisations knowledge is a huge factor but its easy to fall into a trap where no matter what the problem is the solution is X language.

      If I have an organisation that knows C# and we need to build a Web Application. I would suggest we need to learn Node.js and Typescript and not invest in a solution that turns C# into web pages.

      • fuzzzerd
        link
        fedilink
        arrow-up
        3
        ·
        10 months ago

        Wait, are you seriously overlooking ASP.NET and suggesting c# tes learn typescript and node to build web apps?

        I get that it’s a hypothetical, but typescript and node shouldn’t be the first stop on the we need to build a web page train for folks already in the c# wagon.

      • anti-idpol action
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        10 months ago

        not invest in a solution that turns C# into web pages

        do you also mean we should yeet any server-side rendered html while that was how the web mostly worked before react and how it is starting to work again after we’ve reached a point of discord having an input lag worse than ssh on a mobile network to a server on another continent?