There are several distinct developer ecosystems. Some people write C# and VB on .NET in Visual Studio on Windows machines for delivery to Windows Server enterprise networks. Some people write Java on Spring/J2EE in Eclipse for delivery to Java enterprise application servers. Some people write C++ in proprietary IDEs for delivery to proprietary embedded systems platforms. But the one I’m talking about is the one centered around Github, Kubernetes, Macs, and trendy open source tools like Go, Rust, React, etc. The “hipster” characterization is tongue in cheek. It would be insufficient to say “the developer ecosystem” because MS already has one of those, including its own VCS, Team Foundation Services.
Rust is an interesting one, because I think it bridges those last two - normally very separated - groups. Some of those who deliver software into embedded systems are excited about the possibility of a replacement to C++.
(disclaimer: am an embedded systems engineer and a Rust fanboy)
To me, if it requires an explanation then an explanation would be best. I certainly don't care for explanations of things that don't require explanations.
There are several distinct developer ecosystems. Some people write C# and VB on .NET in Visual Studio on Windows machines for delivery to Windows Server enterprise networks. Some people write Java on Spring/J2EE in Eclipse for delivery to Java enterprise application servers. Some people write C++ in proprietary IDEs for delivery to proprietary embedded systems platforms. But the one I’m talking about is the one centered around Github, Kubernetes, Macs, and trendy open source tools like Go, Rust, React, etc. The “hipster” characterization is tongue in cheek. It would be insufficient to say “the developer ecosystem” because MS already has one of those, including its own VCS, Team Foundation Services.
Rust is an interesting one, because I think it bridges those last two - normally very separated - groups. Some of those who deliver software into embedded systems are excited about the possibility of a replacement to C++.
(disclaimer: am an embedded systems engineer and a Rust fanboy)
If it requires an explanation, don't explain.
To me, if it requires an explanation then an explanation would be best. I certainly don't care for explanations of things that don't require explanations.
Guess I'm not gonna ask why you created an account just to say that