Thinking in terms of both server and client.

When something becomes a clear problem like Rails, it should be discarded. But it seems like the answer is always newer, hotter platforms whether or not they're actually better.

Corollary: expending capitalist time and money to experiment with new technologies, since they have too much money to understand what we're doing... is that praxis?

  • RNAi [he/him]
    ·
    3 years ago

    I have no fucking idea why are there eight bajillion different coding languages and I'm not afraid to ask it

  • Spinoza [any]
    ·
    3 years ago

    OOTL, what happened to rails? never used it

    • vertexarray [any]
      ·
      3 years ago

      At my last job people were scrambling to get our servers away from it and running something more performant

      • Spinoza [any]
        ·
        3 years ago

        i tried some googling and it seems like that's what people are saying. even though it's still around, the wiki says this at the top (lmao):

        Ruby on Rails' emergence in 2005 greatly influenced web app development, through innovative features such as seamless database table creations, migrations, and scaffolding of views to enable rapid application development. Ruby on Rails' influence on other web frameworks remains apparent today, with many frameworks in other languages borrowing its ideas, including Django in Python, Catalyst in Perl, Laravel, CakePHP and Yii in PHP, Grails in Groovy, Phoenix in Elixir, Play in Scala, and Sails.js in Node.js.

        • vertexarray [any]
          ·
          3 years ago

          Phoenix in Elixir is the one of those successors I've toyed with and I can confirm that the DNA is very present, and that it's a very necessary evolution

  • makotech222 [he/him]
    ·
    3 years ago

    I'm a .Net guy, so I try to use C# for absolutely everything if I can. This has been made much better with the recent release of .Net 5 and Blazor; I'm currently making a website with frontend code in c#, which has been surprisingly good.