Python has overtaken JavaScript as the most-used language on GitHub, according to the code-hosting platform's latest Octoverse report. The company
  • FizzyOrange@programming.dev
    2·
    7 months ago

    Ok after reading the article this is bullshit. It’s only because they are counting JavaScript and Typescript separately.

      • daniskarma@lemmy.dbzer0.com
        0·
        7 months ago

        We have different concept about what great news is.

        Compiling to an interpreted high level language is crazy. I just refuse to believe we haven’t got a better solution to yet.

        • Cratermaker@discuss.tchncs.de
          1·
          7 months ago

          As someone who works with typescript daily, you’re not wrong. It’s an extremely overcomplicated glorified linter that tries and mostly succeeds in catching basic type errors. But it also provides false confidence when you concoct something that shows no errors but doesn’t behave how you expect.

  • aubeynarf@lemmynsfw.com
    0·
    7 months ago

    Thank god, Javascript is a mess.

    I’ll still plug Scala for having the beauty of Python, the ecosystem of Java, the correctness of Rust, the concurrency of Go, and the power of Lisp.

    • bjornsno@lemm.ee
      0·
      7 months ago

      I code both typescript and python professionally, and python is almost as much of a mess, just a different kind of mess. The package manager ecosystem is all over the place, nobody is agreeing on a build system, and the type system is still unable to represent fairly simple concepts when it comes to function typing. Also tons of libraries just ignore types altogether. I love it, but as a competitor to JavaScript in the messiness department it’s not a good horse.

      • hector@sh.itjust.works
        0·
        7 months ago

        I’m going to code in Python for my job soon, do you have links on how TF I should manage dependencies? I can’t stand the bloat of virtual environments or Anaconda sorry.

        I need to make myself a stack python but I don’t want to look at this madness. At least Typescript benefits from a high quality ecosystem of frontend tooling with Vite/React/ESLint/ESBuild and it’s getting even better with the new runtimes features :)

        I need to learn about:

        • built-in tools provided by the language (practice on the job and the power of Google & LLMs will help)
        • ecosystem
        • good practices

        Why is their a build system for an interpreted language ? Do you have bundling concerns like in JS or you somehow compile Python code now?

        • bjornsno@lemm.ee
          1·
          7 months ago

          You need to get over the bloat of virtual environments. It’s the same as node_modules and it’s completely necessary if you want more than a single python project to live on your machine.

          I personally use poetry as my dependency manager and build tool. It’s not perfect but it’s a lot better than pipenv or just rawdogging pip like a maniac. uv is the new hotness, but I haven’t tried it so can’t vouch. People seem to like it though.

          JavaScript is also an interpreted language with tons of build tools. The reason to have one for python is mainly about packaging and code distribution, so same as JavaScript. If you want to distribute a program you probably don’t want to just point people to a GitHub repo, and if you want to publish a package on pypi it needs to be bundled correctly.

          For ecosystem there isn’t much I can do for you, it completely depends on what you’ll be working on. Baseline you want pydantic for parsing objects, assuming some APIs will be involved. You want black for code formatting, flake8 for linting, pytest for testing. If you’re gonna write your own APIs you can’t go wrong with fastapi, which works great with pydantic. For nice console stuff there’s click for building cli apps and rich and textual for console output and live console apps respectively.

          People are actively trying to replace flake8 and black with feature compatible stuff written in rust but again I haven’t tried those so can’t vouch.

          Coming from react you’re gonna need to pretty quickly switch gears to thinking more object oriented. You’re gonna be annoyed at how you can’t just quickly declare a deeply nested interface, that’s just how it is. The biggest change other than object oriented thinking will probably be decorators. Typescript had them experimentally and only for classes, python has them for classes and functions natively. They’re a bit tricky to wrap your mind around when you want to write your own, but not too bad. A lot of Google hits will be outdated on this front. Google specifically “decorators ParamSpec” to see how to make them properly.

          Good luck in your new job, you’ll be grand!