81–90 of 520 posts
Earlier quoted context omitted.
Honestly, the only domains that I think rust isn't suitable for are: * rapid-prototyping, where javascript and python are still top-tier * adding scriptability to existing programs, where lua and scheme (and python) are popular * Server-side API implementation (rust is usable here, but I think Go fits the slot better)
GPU programming?
M$ choosing Rust might be the strongest argument for picking Go instead
Rust is absolute performance, similar to C++. Go is deliver fast and get a very good performance to effort ratio.
This is very big news, all major OS vendors that also have a role in C and C++ language tooling, now have diversified their options in systems programming languages for greenfield development. Additionally we finally get some public news about the MSVC integration rumors regarding Rust.
Earlier quoted context omitted.
Honestly, the only domains that I think rust isn't suitable for are: * rapid-prototyping, where javascript and python are still top-tier * adding scriptability to existing programs, where lua and scheme (and python) are popular * Server-side API implementation (rust is usable here, but I think Go fits the slot better)
My employer company go through JavaScript, Java, Golang and at the end landed on Rust for srver side and don't want to change anything. Everything is Rust now, regardless of traffic. I don't know why you think it's only usable but this is your right.
This is very big news, all major OS vendors that also have a role in C and C++ language tooling, now have diversified their options in systems programming languages for greenfield development. Additionally we finally get some public news about the MSVC integration rumors regarding Rust.
Are you thinking this augurs more interoperability features in C?
COM and WinRT (basically COM Next) are the way to do cross language Interoperability in Windows since VB 5 replaced VBX with OCX, it was a key feature in .NET Framework design, and revamped on Windows 8, when WinRT was introduced as the original design for .NET (Ext-VOS).
https://arstechnica.com/features/2012/10/windows-8-and-winrt...
See windows-rs crate.
So when will we get tier 1 debugging support in Visual Studio?
With certain rough edges like complex traits and Async aside, rust is an S-tier lang in several domains. Of interest: - Embedded - PC desktop applications - Computationally-intense scientific programming. (Chem, structural bio etc) - OSes, drivers etc - High-performance tasks in general. CPU, GPU, etc. It's not a memory-safety one-trick pony; it's a well-rounded lang which has learned from its predecessors.
Yeah I'd written some rust ~ 10 years ago when the language was very different and that led me to believe that it was a 'great within it's niche' sort of thing for a long time, but after spending the last couple of years with it as a daily driver I think it's a pretty great general-purpose language. The one really common gotcha with rust is that when trying to write concurrent code, newbies tend to throw Arc > goo ar…
I think C++ is an excellent choice due to its volubility actually. Bc when I want safety, I mostly have it (but I have done a lot of C++, admittedly).
Earlier quoted context omitted.
Because it takes time. Even with coding agents, to add the capability. Then, there is the question on whether Rust developers who like to engage with Microsoft tools, would really consider Visual Studio as their IDE, instead of something like VS Code, VS Code Agent Mode, GitHub Copilot App, or GitHub Copilot CLI with simpler editors. I'd be curious to know whether Rust developers believe Visual Studio is the right pl…
There's two ways to approach this — build tooling for existing Rust developers to get them to adopt the Microsoft stack, or build tooling for existing Microsoft stack developers to get them to adopt Rust. I'd argue that the former is less important than the latter, and my understanding is that Visual Studio is still the IDE for Windows-centric development, so for those MS-first developers, Rust missing from VS means…
If it is a tier-1 language why isn't it supported in Visual Studio?
Because it is already supported in VS Code. I don't think this is a hot take, but I'm predicting Microsoft will gradually phase out Visual Studio in favor of VS Code.