It's unclear to me from the article or docs: does this release of Mojo support GPU?
Well assuming that a usable thing exists seems to be where you went wrong according to the reports on Twitter and such haha.
RTFM.
Mojo is available for local download
71–80 of 193 posts
Re: Mojo is available for local download
#72Why are people so enthused about Python syntax? Some problems off the top of my head: - The lack of new variable declaration keyword makes scopes less explicit. nonlocal is not simpler in the large than `let x = ...` - The lack of multi-line lambdas is very limiting for anyone coming from JS, C#, Rust, Kotlin... heck even Java - The ternary operator (... if ... else ...) is needlessly different for other mainstream l…
Yeah, I highly dislike working with python, everything is special syntax or different for no reason. In addition to what you mentioned:
* try catch is different keywords from virtually all other languages.
* walrus tusks, the general order in list comprehensions generally where bindings come after expression
* typing is awful, unsound in a lot of cases, there’s a ton of special non straightforward plugins in mypy. This is partially better in pyright but not considerably.
* package management is silly. Poetry is like a poor imitation of npm. Venvs are a pain in the butt.
… all of this for a pretty slow language.
Re: Mojo is available for local download
#73Still not available for Mac with Intel chips unfortunately
Re: Mojo is available for local download
#74Still not available for Mac with Intel chips unfortunately
Not available for anything but Linux x64
Re: Mojo is available for local download
#75Earlier quoted context omitted.
Same, and even worse, the playground requires you to be logged in. That's like the initial step of a demo and requiring an account is simply nuts.
The same is true of GPT. Just sayin. Actually GPT is worse because they demand both a phone number and an email. Still haven't signed up because of that nonsense.
That's why I don't use GPT.
Re: Mojo is available for local download
#76Who would risk using a closed-source language? I know some academic groups using Matlab, and I know some engineering companies use tools like Simulink, but these are very established products. I don't think I could even get sign-off for using a new closed language for a work project...
Given Lattner's record, I think it would be a bad assumption to think it will stay closed.
Re: Mojo is available for local download
#77Earlier quoted context omitted.
I'd like to add that forced whitespace is infuriating. It's annoying to navigate (in vim I can't easily go to the beginning/end of a code block like I can in languages where scopes are defined by braces), and it's annoying to read because it's not always intuitive how deep I am within nested scopes
> ... it's not intuitive how deep I am within nested scopes The ONLY piece of information that is available to you regardless of how deep you are into a function is INDENTATION. Your curly braces won't help you. Besides that, you should seriously reconsider your coding style if this is an actual problem for you.
>The ONLY piece of information that is available to you regardless of how deep you are into a function is INDENTATION.
...No? It sounds like you write very long, messy code blocks. Consider the following example, I will write a nested loop in 2 languages:
In Python:
for _ in range(10):
for _ in range(10):
print("Inner")
print("Outer")
for (const _ of foo) {
for (const _ of foo) {
console.log("Inner");
}
console.log("Outer");
}
Curly braces allow me to have 3 visual indicators that a block is finished: a visual text object (the brace itself), an extra line separator (the closing brace lives on its own line), and indentation. In Python, I only have one of those things (just indentation). I can have 2 (indentation + line sparation) if I always insert a newline before `print("Outer")`, but empty lines can get deleted and I may forget to include them as I write code. You'd need to configure a linter to guarantee the line separation indicator in a language that delimits scopes by whitespace.
Re: Mojo is available for local download
#78A rant. I apologize. I try to avoid on HN and in general. Faster, yes, but at what cost? I'm so impressed by the Python community, but I'll never quite understand why they gravitated to... Python itself. It's unbelievable to me that in Mojo's case some of the brightest, most famous engineers have gathered to do incredible computer science work to improve the compute performance of a language that is fundamentally fla…
> But my god, what if the community had gravitated to a better language [for these purposes] in the first place? How much further along would we be in our tooling and capabilities to deliver value?
Better in what regard? Performance? Maybe there are more important things than performance, like ease of use and barriers to entry.
People in this space already tackle essentially complex problems, don't throw more accidental complexity in the form of "better" or more performant languages/APIs.
Re: Mojo is available for local download
#79Earlier quoted context omitted.
Python is slow, but it's not "invest time building software with a closed source language from a new company" slow.
Yeah, and I assume in the future Python will get its own JIT or AOT compiler, if people really demand it. Most Python for scientific programming is just a higher level glue code for the C++ underneath.
Python already has JIT compilers (PyPy and Numba).
Re: Mojo is available for local download
#80A rant. I apologize. I try to avoid on HN and in general. Faster, yes, but at what cost? I'm so impressed by the Python community, but I'll never quite understand why they gravitated to... Python itself. It's unbelievable to me that in Mojo's case some of the brightest, most famous engineers have gathered to do incredible computer science work to improve the compute performance of a language that is fundamentally fla…
if the better languages were actually good, they wouldn't have allowed python to whip their asses. Python won because it was nice and easy. meet your users where they are, not where you want them to be.