• bahmanm@lemmy.ml
    link
    fedilink
    English
    arrow-up
    43
    arrow-down
    1
    ·
    1 year ago

    When i read the title, my immediate thought was “Mojolicious project renamed? To a name w/ an emoji!?” 😂


    We plan to open-source Mojo progressively over time

    Yea, right! I can’t believe that there are people who prefer to work on/with a closed source programming language in 2023 (as if it’s the 80’s.)

    … can move faster than a community effort, so we will continue to incubate it within Modular until it’s more complete.

    Apparently it was “complete” enough to ask the same “community” for feedback.

    I genuinely wonder how they managed to convince enthusiasts to give them free feedback/testing (on github/discord) for something they didn’t have access to the source code.


    PS: I didn’t downvote. I simply got upset to see this happening in 2023.

    • The Hobbyist@lemmy.zip
      link
      fedilink
      arrow-up
      4
      arrow-down
      9
      ·
      edit-2
      1 year ago

      Im not sure what the issue is. I have listened to Chris talk about the development of Mojo and while I have not come across any confirmation for open sourcing all aspects of Mojo yet (which would be desirable), the fact that it is being developed with involvement from the community, in a closed beta is understandable and also a good idea.

      He explained it as this: during the closed beta, he didn’t want people to start sharing temporary quirks and bugs or features while they could still drastically change. Someone complained at some point that the python function “open” was not recognized. That’s probably exactly what they are set up to solve and we would probably here many more “issues” from people if it were all happen in the open. People would just see it’s not working perfectly as if it were released and would dismiss it and it could mean the end of Mojo.

      Instead, they selected individuals who cared, who wanted to be involved and improve it and give feedback. This is a normal development process. It is logical to me to launch it once the language is mature and most issues are ironed out and that the API, language and features are more stable.

      Edit: what are people who downvote disagreeing about?

      • ericjmorey
        link
        fedilink
        arrow-up
        12
        arrow-down
        1
        ·
        1 year ago

        People would just see it’s not working perfectly as if it were released and would dismiss it and it could mean the end of Mojo.

        This explains why Python, Rust, Typescript, and Go aren’t popular and died.

        • The Hobbyist@lemmy.zip
          link
          fedilink
          arrow-up
          3
          arrow-down
          2
          ·
          edit-2
          1 year ago

          Python is the de facto language for all machine learning work. I don’t know about the other languages (though go seems to have a strong community for all networking related projects) but Python has certainly not died.

          Edit: if this was sarcastic it really flew over my head :) my bad!

          • Boff@beehaw.org
            link
            fedilink
            arrow-up
            5
            ·
            1 year ago

            He was being sarcastic, he listed the most popular languages in modern development

  • Pennomi@lemmy.world
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    1 year ago

    Ew, their claimed benchmarking is ridiculously biased. “We completely restructured the algorithm to be more efficient, so our language is faster than yours.” and “We ran our benchmarks on a faster computer than we ran the Python benchmarks.” Not a good look to lie through your teeth like that.

    • AlmightySnoo 🐢🇮🇱🇺🇦@lemmy.world
      link
      fedilink
      arrow-up
      27
      arrow-down
      1
      ·
      edit-2
      1 year ago

      They also claimed to be faster than C++ in the beginning, but they failed to mention that the C++ code was unoptimized single-thread code while the Mojo version was SIMD-vectorized and multithreaded. It’s only after people criticized them for that that they started calling the C++ code “scalar C++”. Scientific rigor is lacking in their benchmarks.

  • AlmightySnoo 🐢🇮🇱🇺🇦@lemmy.world
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I mean I know they promised to do it, but it’s sad that they still haven’t open-sourced the toolchain. The naming is awkward though, I’d have loved if they called it Python++ instead as it’s supposed to be a superset of Python and would have made it easier to present to your boss.