step function

Because they don't want you to improve.

codex cli. I switched, no regrets. Also, $20 for top model vs being limited to sonnet.

Plus (the $20 plan) is still stuck on 5.2 right now..

5.3 codex xhigh works for me

Honestly even medium is quite good.

> the compiler can now allocate the backing store for slices on the stack in more situations

Any details on when this happens?

see: https://go-review.googlesource.com/c/go/+/707755 and https://go-review.googlesource.com/c/go/+/664299

Looks for slices with lengths <= 32.

For the same reason we don't commute on horses anymore.

And safety.

ZGC? It should be on par or better than Go.

Java’s collectors vastly outperform Go’s. Look at the Debian binary tree benchmarks [0]. Go just uses less memory because it’s AOT compiled from the start and Java’s strategy up until recently is to never return memory to the OS. Java programs are typically on servers where it’s the only application running.

[0] https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Also -- Java versus Java native-image

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

IIRC the native image GC is still the serial GC by default. Which would probably perform the worst out of all the available GCs.

I know on HotSpot they’re planning to make G1 the default for every situation. Even where it would previously choose the serial GC.

I have the same feeling, and my best guess is that it's the intentional (and imo arbitrary) friction that has been sprinkled into the language. And camelCase.

Lol. Funny enough I actually like camel case because I've spent so much time in Java.

Yeah, I can see that. It's also difficult to put my finger on, but for a language that claims to be simple it seems to make a lot of things needlessly complicated. I'm also not loving how everything is deeply nested structs so I have to do struct.doThefirstThing.doTheSecondThing.doTheThirdThing().etc() all the time.

parent said free, not open source. I want Mojo to succeed, but I'm also doubtful of the business model.

Do you get a functional version of CUDA free with AMD's much more reasonably priced hardware?

Mojo is planned to be both free and open source by the end of next year and it's not vendor locked to extremely expensive hardware.

To take full advantage of Mojo you will need Modular's ecosystem, and they need to pay the VCs back somehow.

Also as of today anything CUDA works out of the box in Windows, Mojo might eventually work outside WSL, some day.

Commercial use of Mojo on Nvidia hardware is already free today.

There is no disadvantage vs CUDA.

A language without ecosystem isn't that interesting.

more like old school lib vs "new left"

> I mean, in 2025, not having crypto in stdlib when every man and his dog is using crypto ? Or http when every man and his dog are calling REST APIs ?

I'm not and I'm glad the core team doesn't have to maintain an http server and can spend time on the low level features I chose Rust for.