You're really splitting some very thin pedantic hairs.

You're problem isn't with me, you are quibbling with there own marketing materials. Go complain to marketing if they are using the words that you disagree with. Everything I've posted is directly from Mojo's website.

You: "Well, technically they are embedding the interpreter, so all the surrounding code that looks exactly like python, and we promote as being compatible with python, and promote as extending python. My good sir, it is not really python. That is just a misunderstanding with marketing. Please ignore everything we are clearly making out as an important feature, totally wrong".

They clearly promote that they are extending python. What is your problem with that? How is that wording causing you to seize up?

I'm aware of what is technically happening. Where did I ever say anything that was not directly from them? Do I really need to write a thesis to satisfy every ocd programmer that wants to argue every definition.

Were you let go because of an inability to think flexibly? Maybe too many arguments with co-workers over their word choice? Does you're brain tend to get single tracked on a subject, kind of blank out in a white flash when you disagree with someone?

Actually, I'm kind of convinced you're just arguing to argue. This isn't about anything.

▲

almostgotcaught a day ago | parent [-]

> so all the surrounding code that looks exactly like python, and we promote as being compatible with python

bro are you really thick? there is zero mojo code that is runnable python; take a look at

https://github.com/modular/modular/tree/main/mojo/stdlib/std...

mojo has zero to do with python. zilch, zero, nada.

what they are doing is simply embedding the python interpreter and running existing python code. literally everyone already does that, ie there are a million different projects that do this same thing in order to be able to interoperate with python (did you notice the heading at the top of the page you linked is *Python interoperability* not *Python compatibility*).

> This isn't about anything.

it's about your complete and utter ignorance in the face of a literal first hand account (plus plenty of contrary evidence).

> Were you let go because of an inability to think flexibly?

let go lololol. bro if you only knew what their turnover was like you would give up this silly worship of the company.

	▲	FrustratedMonky a day ago \| parent [-]
		Sorry. I get it now. You're bitter. To be clear, I'm not a fan boy. I don't really know much about Mojo. I've watched some videos, checked out their website, thought it was interesting idea. The parent post was about alternatives to CUDA. I posted a 6 word sentence summarizing how Mojo is trying to bypass CUDA, and using Python. -> And you flipped out, that it isn't Python. Really? I checked out your link, sure does look like Python. But that is the point, all of their promotional materials and every Chris Lattner video, all sales pitches, everywhere. Everywhere, is Python, Python, Python. Clearly they want everyone one to know how closely tied they are to Python. It is a clear goal of theirs. But. I see now the pedantic hair splitting. Mojo 'Looks Like Python', they use the same syntax. "Mojo aims to be a superset of Python, meaning it largely adopts Python's syntax while introducing new features". But you say, they aren't modifying or extending CPython so this is all false, it is no longer technically Python at all. And I guess I'm saying, Chill. They clearly are focused on Python all over the place, to say that it isn't, is really ludicrous. You're down a rabbit whole of debating what is a name, what is a language. When is Python not Python? How different does it have to be, to not be?