wow, somehow you jumped to some next level conspiracy garbage more extravagant than the rest of the comments. 20 million people participating in protests was not a “state sponsored attack”
I was excited for Accelerator. All of the projects from last year[1] actually looked useful or I was already using them (htmx, dioxus, nuxt, datasette, trpc, strawberryql). Now it is a bunch of garbage LLM tools I will never use. Even their front page[2] looks infinitely worse than I remember and only says "Powering AI Advancements in the open." RIP GitHub Accelerator.
EDIT: they really did make the front page much worse[3]. The words on the original page actually sound like they were written by a human. No mention of uplifting the open source ecosystem anymore, not even pictures of OSS maintainers.
This post is rather unrelated. The linalg dialect can be lowered to LLVM IR, SPIR-V, or you could write your own pass to lower it to e.g. your custom chip.
This comment finally pushed me to try out Kagi and WOW. I did not realize how much I was missing out from a search engine - pinning & blocking websites on my search???? It seems so obvious now, but damn is that incredible.
Have any examples of syntax you find tasteless? Things in Zig that feel ergonomic to me: comptime params > separate generic args; ptr.* > *ptr; optional pointers > possibly null normal pointers; separate syntax for slices, arrays, & pointers > 1 syntax for ptr & arrays.
... wat? imperative; compiled to machine code, either static exe or dynamic libs; builtin RAII & polymorphism (parametric, subtyping); maps, vectors, trees, and other data structures in the stdlib; raw access to pointers; C ABI compat. there are some big differences, but "nothing like c++" is absolutely not true.
It looks like the Mojo compiler/runtime hooks into the CPython interpreter.
> We utilize CPython to run all existing Python3 code “out of the box” without modification and use its runtime, unmodified, for full compatibility with the entire ecosystem. Running code this way will get no benefit from Mojo, but the sheer existence and availability of this ecosystem will rapidly accelerate the bring-up of Mojo, and leverage the fact that Python is really great for high level programming already.
The goal is for the language to be a superset of Python
> Further, we decided that the right long-term goal for Mojo is to provide a superset of Python (i.e. be compatible with existing programs) and to embrace the CPython immediately for long-tail ecosystem enablement.
> This was not a "knee-jerk" reaction, nor was it an attempt to spread fear or cause panic. While the document the foundation drafted did lead to the fork, we believe it is an overdue solution to a problem that already existed, and addresses some issues that many community members have had for some time.
This is obviously very knee-jerk and will either die or end up creating the same bureaucracy that Rust has. People love to complain about bureaucracy without understanding it exists for many reasons. The Rust teams are far more equipped to handle the development of Rust than anyone entertaining this fork (unless, of course, a significant number of members of the Rust teams decide to move over).