• SokathHisEyesOpen
    link
    fedilink
    English
    10
    edit-2
    2 years ago

    Hey now! PHP may be old and a bit clunky, but it gets shit done. I’d say PHP is the Colt repeating rifle, since PHP won the internet and the Colt won the West. Much like the Colt, there are better tools available today, but if you want stuff done reliably and quickly, PHP and the Colt are good choices.

  • GamesRevolution
    link
    fedilink
    412 years ago

    It’s a pretty good representation of Rust, being 3d printed means that it’s the only gun where you can’t shoot yourself in the foot

    • @marcos@lemmy.world
      link
      fedilink
      82 years ago

      And before the time people actually talked about the multidimensional clusterfuck that C become.

    • @dan@upvote.au
      link
      fedilink
      52 years ago

      It’s not as common any more, but there’s still things using logic programming languages (Prolog and similar) even today.

      Java uses it in the type checker. From the JVM spec:

      The type checker enforces type rules that are specified by means of Prolog clauses.

      There’s some other compiler and NLP (natural language processing) use cases for it too. I’ve seen some companies use it to define restraints for their business logic, which isn’t too different from the type checker rules use case.

      It’s definitely fallen out of common use though.

      • @Treczoks@lemm.ee
        link
        fedilink
        English
        42 years ago

        We did Prolog in university - actually it was one of the two languages we had to learn in CS, the other one being Pascal.

        I always considered Prolog a pain in the ass and unsuitable for anything bigger than a piece of homework due to the “we don’t do loops, we have tail recursion” making the code unnecessary complex and hard to read. On a list of Write-Only languages I’d rate it a few steps below Perl.

      • r00ty
        link
        fedilink
        82 years ago

        And someone would pick up the phone 30seconds from the end, and there was no resume!

        • @dan@upvote.au
          link
          fedilink
          1
          edit-2
          2 years ago

          there was no resume!

          IMO the HTTP Range header (the thing that lets you resume downloads) was one of the best innovations back then. It let the client tell the server where to start the download from, and how much of the file to download. This means it also let you speed up downloads by downloading multiple pieces in parallel. I used to use a program called GetRight and loved it.

          We still split up downloads like this today. These days, internet connections are often fast enough that you can’t reach full speed with a single connection, so speed tests and things like Steam will open multiple concurrent connections for their downloads to maximize download speed.

  • Haus
    link
    fedilink
    62 years ago

    Nice seeing Mathematica and Lisp mentioned. I feel like Marvin the Martian after reading.

  • @nxdefiant@startrek.website
    link
    fedilink
    162 years ago

    Python needs an update:

    Python would be a Tavor TS12 automatic shotgun with rotating tube magazines. It’s heavy, doesn’t have a fast fire rate, but it can fire a ridiculous array of ammunition, and they’re working on the ability to fire all the barrels at once (GILess)

  • tiredofsametab
    link
    fedilink
    292 years ago

    “perl was probably useful once”?!

    I’m willing to bet a TON of medical and banking data is still making its way through perl today. (I’m not necessarily saying this is a good thing, but I have years of experience in healthcare IT).

    • For that matter, there are still folks out there coding, professionally, in FORTRAN.

      Thing is, back then, we didn’t know any better. Software was a commodity, and both the people who wrote it and the people who bought it had grown up in a time before the internet, before SaaS; people whose parents who, if they made things, made widgets.

      Back then, you could write a piece of software, and it was done. Then you sold it, and moved on. If the old software had bugs, if they weren’t catastrophic enough to cause a lawsuit, buyers learned to live with them. It was too bad; you already shipped the tapes. And few companies employed their own software developers unless they were software development companies. Man pages have a BUGS section, and that’s because there’s no intention to ever fix those bugs, because that software is done.

      Software today is never finished. Our first reaction if we see a project with no recent releases is that it’s abandoned, or dead, and certainly that it’s worse than a project with recent commits to the repo. Github is a huge culprit in reinforcing this mentality, but mobile app platforms (stores and OSes) are terrible about this, too. Google constantly changes the Play store in ways that force developers to tweak their apps lest they become incompatible, booted, or get flagged as being “old” a.k.a. “inferior.”

      Yet, still, there’s so much software out there that’s complete. An institution may hire a developer to come in and make a change, but it’s usually a contract one-off; it’s more like taking your car in to have the starter replaced. Those systems are going to continue keeping “dead” programming languages (commercially) alive for years to come.

    • palordrolap
      link
      fedilink
      22 years ago

      Perl is still as good an interpreted language as any of the others tbh.

      Most of its “problems” are cosmetic, which is probably why Python ended up being its successor in many fields.

      Given the choice between brutalist and Fisher-Price architecture, most people are going to opt for the latter even if everything’s effectively the same inside.

    • r00ty
      link
      fedilink
      72 years ago

      I use perl for that stuff (mostly automation) that’s a bit too complex for bash, but doesn’t need a proper project. Modern people would use python for this kind of thing. But, I’m too old to change!

      • assa123
        link
        fedilink
        22 years ago

        and perl is orders of magnitude faster than python for document parsing

    • @mindbleach@sh.itjust.works
      link
      fedilink
      12 years ago

      Perl is a language for programmers. This turns out to be a terrible idea. Everything actually works the first time, so you move on, and you’re left with the sloppiest inscrutable stream-of-consciousness mess that someone banged out whilst working through the problem.

      Perl is the only language where you can write more code than you read.

      • tiredofsametab
        link
        fedilink
        1
        edit-2
        2 years ago

        That’s a problem with no coding standards, peer review, etc.

        write_good_code() or die(qw(enough rope to hang yourself));

        or die unless write_good_code();

    • @frezik@midwest.social
      link
      fedilink
      62 years ago

      When it comes to surprising behavior, Perl isn’t any worse than JavaScript. Which admittedly isn’t a great comparison for either language. Most of the bellyaching around Perl has to do with regular expressions, but every other language out there picked up Perl’s regex syntax in a mostly verbatim way (PCRE).

  • @roo@lemmy.one
    link
    fedilink
    382 years ago

    It’s funny because people describe PowerShell as powerful, but really they mean it’s also a hammer to mash everything with. “Powerfull!”

    • 𝘋𝘪𝘳𝘬
      link
      fedilink
      292 years ago

      Powershell suffers from the typical Microsoft problem: Ignore for decades, and then go completely over the top with it.

      • @BestBouclettes@jlai.lu
        link
        fedilink
        182 years ago

        I see Powershell as a nuclear bomb. It is extremely powerful and complex and barely anybody uses it because of it.

          • @BestBouclettes@jlai.lu
            link
            fedilink
            21
            edit-2
            2 years ago

            Powershell is so much more than bash, not in a derogatory way.
            It’s a full fledged object oriented programming language, and it’s written in .Net I believe. You can integrate tons of plugins to manage your whole infra (exchange, Cisco, AD, VMware etc), just from the Powershell shell.
            I hate it because it’s slow, clunky and overly complex for its prime use, which is scripting.

          • @alokir@lemmy.world
            link
            fedilink
            132 years ago

            Yes and no. They serve roughly the same purpose.

            I actually hated Powershell until I was forced to work on some automation scripts with it and realized that it’s actually pretty cool.

            Bash is good for quickly doing something in the terminal but for longer script files I prefer PS now. It feels much more modern and has a less janky syntax.

            Funnily enough the reason I had to use it was to make my scripts cross platform between osx, linux and windows.

          • @dan@upvote.au
            link
            fedilink
            62 years ago

            People tend to hate on PowerShell but it’s cross-platform these days, and far easier to write than shell scripts once you understand the syntax.

            You can pipe objects between functions, rather than just string streams like in Bash. Often there’s no cut, sed, grep, etc needed as what you want is probably a property on an object.

            It’s not just a basic scripting language like Bash. It’s built on top of .NET, so most of things you can do in C#, you can also do in PowerShell (and if not, you can call into C# code).

            It’s especially popular for administration of Windows systems - if there’s anything you want to do on a Windows system, it’s likely there’s a PowerShell module for it.