melodyogonna

6 ms·

91.
by melodyogonna 5mo ago
I don't recall they promised that. They promised it'll be a superset, but Mojo introduces new keyword. Mojo could support all Python features today exactly as they're supported in Python and you wouldn't still be able to
92.
by melodyogonna 5mo ago
> Why should they? CUDA is a GPGPU paradigm, AMD/Apple/Intel all ship diverse raster-focused hardware, and TPUs are a systolic array. How much can you realistically expect to abstract with unified primitives? Ah, it seems impos
93.
by melodyogonna 6mo ago
It was always going to be a long-term thing, if it were even possible. You can't make a compiler that can compile Python into efficient machine code in just a year (which was how long Mojo had been in development when it was announced)
94.
by melodyogonna 6mo ago
Have you ever wondered how much work would have been saved by the Pytorch team if they could have used just Cuda for all the platforms they support? If they didn't have to write compatibility abstractions or layers, and instead just fo
95.
by melodyogonna 6mo ago
Something like this https://github.com/tairov/llama2.mojo ?
96.
by melodyogonna 6mo ago
Mojo isn't that far away from 1.0. Some point this year is the target
97.
by melodyogonna 6mo ago
Pytorch is built on an amalgamation of these different frameworks, not on one of them used to target different vendors.
98.
by melodyogonna 6mo ago
It is portable in that you can write code to target multiple platforms in the same codebase. Mojo has powerful compile-time metaprogramming that allows you to tell the compiler how to specialise using a compile-time conditional, e.g. https
99.
by melodyogonna 6mo ago
https://mojolang.org/docs/tools/skills/
100.
by melodyogonna 6mo ago
You'd be surprised. Anyway, the compiler will be opened with 1.0 release, that's why reaching beta is exciting.
101.
by melodyogonna 6mo ago
People keep mistaking Mojo as good syntax for writing GPU code, and so imagine Nvidia's Python frameworks already do that. But... would CuTile work on AMD GPUs and Apple Silicon? Whatever Nvidia does will still have vendor lock-in.
102.
Mojo Language(mojolang.org)
17 points by melodyogonna 6mo ago|1 comments
103.
by melodyogonna 6mo ago
Ha! Nerds.
104.
by melodyogonna 6mo ago
TL;DR: Rust can't catch logic bugs
105.
by melodyogonna 7mo ago
Aha! That would explain things. I was wondering if the Go assembly at least is stable and documented, couldn't really find anything
106.
by melodyogonna 7mo ago
https://lisette.run/
107.
by melodyogonna 7mo ago
That's two new languages compiling to Go making HN frontpage in as many days. It seems people like everything about Go except the language itself. Me? I like everything about Go including the language, these transpiled languages are in
108.
by melodyogonna 7mo ago
Python has a performance problem. Most people may not need it, but many people do. Languages like Rust and Go are heavily adopted by Python programmers either trying to understand low-level concepts or looking for something more performant.
109.
by melodyogonna 7mo ago
It does matter. It already has a pretty active community and thousands of people who follow the development closely, however, most won't commit until the entire language is fully opened... including me. Valuable technologies are not so
110.
by melodyogonna 7mo ago
The compiler will be open-sourced in a few months.
111.
by melodyogonna 7mo ago
That is interesting, but I imagine Rust has features which can not be translated into Go's assembly. This language is specifically designed for Go interop; the logistics wouldn't be the same, though I still expect it to be difficu
112.
by melodyogonna 7mo ago
I'm wondering about the logistics of making this integrate with Go at the assembly/object file level rather than at source code level. What if it compiled to Go's assembly rather than to Go source code
113.
by melodyogonna 7mo ago
I reviewed the TensorRT-LLM commit history from the past few days and couldn't find any updates regarding Gemma 4 support. By contrast, here is the reference for MAX: https://github.com/modular/modular/commit&#
114.
Understanding the Go Runtime: The Garbage Collector(internals-for-interns.com)
6 points by melodyogonna 7mo ago|4 comments
115.
by melodyogonna 7mo ago
How so?
116.
by melodyogonna 7mo ago
> If you have a system that requires predictable latency, go is not the right language for it. Having a garbage collector already make this the case, it is a known trade off.
117.
by melodyogonna 7mo ago
Rust started in 2006 and reached v1 in 2015, that's 9 years.
118.
by melodyogonna 8mo ago
I can not imagine coding without multi-level undo.
119.
by melodyogonna 8mo ago
But Zig's async is being designed to enable this low-level control.
120.
Modular Acquires BentoML(modular.com)
4 points by melodyogonna 8mo ago|1 comments

More ›