6 ms·
I feel like MS naming convention are flipped on the head. Rust for Windows -> a version of Rust for Windows? Windows Library for Rust -> a library for Rust tha
by turbinerneiter 5y ago
I feel like MS naming convention are flipped on the head.
Rust for Windows -> a version of Rust for Windows?
Windows Library for Rust -> a library for Rust that allows to interface with Windows APIs
Same with Windows Subsystem for Linux. It's a Linux system for Windows.
But hey, that's just names. Nice for win-devs to get more languages supported.
- skohan 5y agoMaybe it's cynical, but I wonder if it's a PR/imaging move. When you read these kind of names, it seems like the Linux/Rust community is embracing and supporting Windows, while really it's the reverse.
- loa_in_ 5y agoI don't think it's cynical at all, and is probably both. I guess in all big companies PR/marketing teams chime in to all public facing projects
- mcny 5y agoI think you are right. If I remember correctly, someone on the typescript team said they have no control over version numbers. PR/marketing decides what is version 4.0 vs 3.11.
- Vinnl 5y agoI don't think that's strictly true: https://twitter.com/drosenwasser/status/1098748330765619200 https://twitter.com/drosenwasser/status/1098748330765619200 As far as major versions go, AFAIK they just bump the mayor version every ten minor versions, of which they release a new one every 3 (?) months.
- pjc50 5y agoMicrosoft naming is incomprehensible sometimes. Doing a .net framework -> dotnet core transition at the moment has really exposed me to a lot of this.
- xbar 5y agoI find Microsoft naming is always suspicious. "Let's deliberately choose a name for a thing that could be confused for a different thing. [some amount of time and nefarious activity later, and with false innocence] Oh, we've always called it that, so you can't have that namespace even though you think it should belong to that technology that predates our suspicious name with which we encroached on non-Microsoft technology."
- arwhatever 5y agoNew Microsoft project name idea: Microsoft Namespace
- Boulth6 5y agoThis is mostly for legal reasons and the "for X" where X is a trademark is a common theme. (just look at Google Play store "for Twitter" or "for Reddit"). Looks and sounds weird though!
- rasz 5y agoand windows 0.9? Cmon, not even full 1.0? https://en.wikipedia.org/wiki/Windows_1.0 https://en.wikipedia.org/wiki/Windows_1.0
- 29athrowaway 5y agoThat's exactly what I thought. It should be Windows support for Rust and not the other way around.
- worble 5y agoWhen it was Windows Subsystem for Linux, I assumed marketing dictated "No no, the word Windows MUST be the first word." This one just seems deliberately confusing for no reason.
- oaiey 5y agoMentioned somewhere else: Windows NT has subsystems. E.g. posix, os2, win32, ... What they do is adding a subsystem to windows. The module they code is the subsystem not the distribution. Nowadays it is a bit blurry die to the full kernel and this windowing subsystem.
- bitwize 5y agoAFAIK it was their legal department, who advised them that calling it a "Linux Subsystem" may run afoul of the Linux trademark, especially considering that in WSL1, Linux itself was not involved at all.
- kaetemi 5y agoCorrect. It's a trademark law issue. In the same way that you can develop a "Chess for Windows" but not a "Windows Chess". Using "for X" is fair use.
- MereInterest 5y agoBut even in your example, it shows how bad of a name WSL is. "Chess for Windows" implies that there is a chess program that runs on windows. By analogy, "Windows Subsystem for Linux" implies that there is a Windows Subsystem that can run on Linux.
- mastax 5y agoSimilarly, the unofficial Reddit apps had to rename from e.g. "Reddit Sync" to "Sync for Reddit".
- losvedir 5y agoYou say "correct" but you're directly contradicting the parent's point, since with your argument the easily and correctly parsed 'Linux Subsystem "for Windows"' would not run afoul of any trademarks.
- shp0ngle 5y agoAt least they didn’t name it Azure Rust, Rust Live, Rust.net or Rust 365 :)
- mrlonglong 5y agoRusty Windows ftw
- barbarbar 5y agoOr Windows with Rust?
- deleted 5y ago[deleted]
- dvfjsdhgfv 5y agoI'm pretty certain some of these names will appear sooner or later.
- dmytrish 5y agoYes, this is more of a "Rust rof Windows" thing.
- signal11 5y agoThe way to parse WSL is that it's a <Windows (NT) Subsystem> for Linux. Windows NT had environment subsystems as a key part of its architecture, with subsystems for POSIX and OS/2, originally[1], and even Win32 was conceptually a subsystem for NT, albeit a very important one. [1] https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#/media/File:Windows_2000_architecture.svg https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#/me...
- skohan 5y agoAnd how are you supposed to parse the rust library?
- deleted 5y ago[deleted]
- gpm 5y ago<A Rust Library> for Windows
- remram 5y agoThat still sounds like it's a Rust library you get to use on Windows, not a library of Windows functions to use from Rust.
- moron4hire 5y agoA Rust Binding for WinAPI
- guerrilla 5y agoThank you. I was wondering why someone resurrected Windows 0.9 (was that even a thing?) and why in the hell someone would port Rust to it.
- ZuLuuuuuu 5y agoA good usage example for a similar naming is "Qt for Python" which is the name of Python bindings of Qt framework. I literally didn't understand what "Rust for Windows" meant, I needed to read the blog post to understand what it is, which is a Rust library to use Windows API from Rust.
- lostmsu 5y agoI think Microsoft played all of us with this name. The confusion is there intentionally for developers to argue about, therefore generating marketing material for free.
- Iv 5y agoMicrosoft sucks at many things. Naming things in a descriptive way is one of them.
- contextfree 5y agoIt was Rust/WinRT, then they added support for other kinds of Windows APIs alongside the WinRT support. Someone probably thought Rust/Windows looked weird, so, Rust for Windows. Rust/WinRT was called that because it was patterned after C++/WinRT, which was called that because it was a replacement for or alternative to C++/CX, which was called that because it was an analog to C++/CLI. C++/CX and C++/CLI are language extensions/forks, while C++/WinRT and Rust/WinRT are just libraries (and tools). (I always thought C++/WinRT was a bad choice of name for this reason)