Rust and its ecosystem needs to become more original. There are so many new problems that needs software solutions. Existing solutions that already work don't have to be rewritten in Rust.
Past attempts at what exactly, I'm not sure I follow. Are you talking about two-language problem, heterogenous compute, or cross-platform accerelated compute stack?
> The development feels less organic and more driven by venture capital
The development has been driven by the needs of Modular.
> This is most acutely felt in the current closed source development of mojo itself
Mojo compiler is closed, the language development is quite open. Some of the proposed changes have been shelved or tweaked based on community feedback. However, you should understand that the compiler is closed to avoid design by committee and bike-shedding, Modular will and does veto decisions on core language semantics, see: https://forum.modular.com/t/canonicalize-apis-around-int/253...
> which seems like it will continue into the near future.
The compiler is getting opened this August. I must admit, a lot of people who would be normally interested in the language are hesitant to poke at it with a stick with the current license (myself included).
The language has really great set of features and functionalities wrapped in a familiar syntax, I have zero doubt it'll reach mainstream adoption.
Ha! I think whether Mojo will make mainstream or not is already a forgone conclusion. It solves too much of a technical problem to be niche. To me, it is a matter of when... not if.
How did Mojo already lose when Qualcomm just made a $4B bet on it? You're forgetting that the language is still pre-1.0.
The way I think of this... if Modular is able to remain an open platform, being part of an established corporation with existing customers is a better way to drive penetration compared to acquiring new customers.
Qualcomm has acquired excellent engineering talent here, the infrastructure I've seen Modular build in the 3 years I've followed the company is insane.
From what I can see, your comment does not disapprove the main points of the article... Which are that OpenCL development moved very slowly (design by committee always do) and that vendors did not contribute with all their cards at the table.
While you may have adopted OpenCL for a long time, Chris Lattner created it (with his team, of course), I wouldn't dismiss his account of the early history offhand.
All very interesting, but I'd wait and see what people with real-world experience running Spacecraft can come up with before dismissing the entire endeavor.
Interesting. From looking into it Wayland had issues with Nvidia, I thought that was already fixed?
I admit, it is a bit of a hack getting screen-sharing to work; I've not really had time for it yet as it isn't a daily driver for me.
I installed Arch on my old Mac few months ago, alongside Xorg and i3, they were what I was used to before I switched to Mac about 6 years ago. Back then Wayland was a mess, so I never even bothered to check it out this time.
However, few days ago my non-technical girlfriend wanted to use my laptop, I couldn't see her using i3 so I decided to install Plasma, a proper desktop environment. Lo and behold I couldn't launch it. After searching I found out I needed plasma-x11-session as the default plasma install now included just a Wayland session. I found this a bit surprising, so I did further digging and discovered a huge chunk of Linux desktop community have basically migrated to Wayland since the last time I was here. Very surprising I must say.
So I decided to try Wayland again; I installed Sway and was pleasantly surprised. My screen resolution was automatically calibrated, operations seemed to run more smoothly, my laptop's fan kicked in less frequently (don't know why), and I didn't need a compositor package to fix screen tear (bye Picom). But all these weren't the reasons I decided to stick with Wayland. You see, in x11 I've been having a persistent problem: playing videos from certain websites, notably Twitter, introduces noticeable flickers. I tried everything to get rid of this: media drivers, verifying GPU acceleration, calibrating refresh rates, nothing worked. When I installed Sway I decided to see if this issue got magically fixed, and lo! It was. Wayland has come a long way since I last tried it. Now that I mentioned it, I have just remembered I need to figure out a way to share screens on Google meets, at the moment I seem to be limited to sharing just the Chrome window.
I mean that in both cases, the core language platform provides the tools and libraries you need to develop complete applications; you don't have to introduce external dependencies or resort to writing low-level data structures and data types.