I'm OK with Lisp output, but maybe that just shows how old I am. :-)
I wonder if it's possible (or wise) to have two different compilers for a language -- one that's optimized for such tight loops, and another that does thorough checking, etc. You know, kind of like -O, but at a much deeper level.
Anyway, I've played around with the idea a bit so far, and it seems that current agents/harnesses use way more tokens with that architecture.
I think "batteries included" is not a good thing to have in the future.
We'll want to be very explicit about what AI generated code can and can not do.
And so some form of effects based scripting language seems like a plausible choice: A language where by default "all batteries are removed".
Pinyin is a system for writing Mandarin Chinese sounds using the Latin alphabet. Pinyin is commonly used for learning Chinese pronunciation and for typing Chinese characters.
The article did explain, albeit near the end.
Now if .NET was still not so embedded in the Windows ecosystem that would be very interesting to me to jump from TS. As it is I am learning Go instead.
This was why I was excited by Bun until recent events. A typescript runtime with a rich standard library, and fast. It looked like it would be a great sweet spot for many use cases.
Python is easier to interface with C/C++ libs.
For example you don’t get to see TCP headers with Node out of the box and you can’t craft packets, whereas you can in Python.
Go might have the advantage because it's easier to read outside the IDE
But then you have the major downside of 'writing' poor code.
Rust has a huge advantage here, in fact many popular Python libraries use Rust underneath.
* Most applications run on the web nowadays. With TypeScript, you can write both the front end and the back end. * TypeScript shares many syntactic-sugar ideas with Python, but it is also statically typed. Whether that is good or bad is a hot topic, but it gives you a lot of confidence through compile-time checks. * Running Node for system tasks is as easy as running the Python interpreter. However, Python is still slightly ahead there.
Python is a general development language that can be used to build servers and web pages, but does a lot more besides.
They're not really comparable.
Having said that - I wouldn't be surprised if Python drifts towards stronger typing, although it will probably remain optional.
I do not think subpar means what you think. Or maybe you rewrote the sentence and forgot to change that word? Anyway, this does not make sense.
So that it's easy for humans to review it. Same reason as ever. Obviously Python isn't always the correct choice, but the overlap with cases where vibe coding is the correct choice is pretty high.
Also wtf is Pinyin?
From the article:
> Many people don’t realize this, but children in China first learn Latin characters, which they use to spell out Chinese phonetically, using a system called “pinyin.” They then use their knowledge of Latin characters to learn Chinese characters, whose pronunciation isn’t obvious from the characters themselves.
More than one reply to my original comment is along the lines of "but humans cannot read/understand machine code effectively". Perhaps instead of starting my comment with "If we're not writing code by hand anymore anyway", I should have said "writing or reading", but it was implied.