Originally posted by coder
View Post
Announcement
Collapse
No announcement yet.
Wine & Mingw-w64 Might Tighten Up Their Relationship - Possible "WineSDK"
Collapse
X
-
Originally posted by tessio View PostThey are changing because It will be developed under the bigger Wine project umbrella.
Originally posted by tessio View PostAnd, let's face it, because Mingw-64 is a horrible name.
If the goal of the "rebranding" exercise is to get more people using it, then you want a name that won't make people think it doesn't apply to their use case. Calling it WineSDK or Wine-anything makes it sound like it's only used with/for Wine. It's the person who doesn't know anything about it that you should care the most about. They're the ones who need to be attracted by the name, rather than put off.
Comment
-
Originally posted by coder View PostIf the goal of the "rebranding" exercise is to get more people using it, then you want a name that won't make people think it doesn't apply to their use case. Calling it WineSDK or Wine-anything makes it sound like it's only used with/for Wine. It's the person who doesn't know anything about it that you should care the most about. They're the ones who need to be attracted by the name, rather than put off.
Windows SDK built stuff can be used on Wine with limitations at times. People should get use to accepting the reverse that Wine stuff can be used on windows.
Wine old project Wine Is Not an Emulator. People in recent years have forgot this. Wine is a compatibility layer. Even the first version of wine had options to built parts of wine for windows.
Basically there has been a long term problem in way Wine project has been presented. Sometimes you just need to bite the bullet and fix it so the long term is better.
- Likes 1
Comment
-
Originally posted by oiaohm View PostWe have a problem here that Wine is not just the big that runs under Linux. Wine does have PE builds where as much as possible is built as PE file that can be used under Windows/Reactos.
Originally posted by oiaohm View PostBasically there has been a long term problem in way Wine project has been presented.
Comment
-
Originally posted by coder View PostEven if you say this, probably 99.9% of actual WINE usage is to run Windows programs on non-Windows platforms
Basically you just said the myth not the facts of the matter. How Wine is really used is lost with the current Wine marketing. Codeweavers don't see that Windows users would be willing to pay to run old applications.
The brand and marketing of Wine absolutely does not match the market share of it users in current form.
Comment
-
Originally posted by skeevy420 View Post
My only use of Mingw is compiling Proton...to build a Linux application that other people develop that runs in Wine... My one and only use case is exactly what you say Ming isn't supposed to be for.
If it wasn't a Proton build requirement, I wouldn't have it installed.
- Likes 2
Comment
-
Wine is great but don't people realize that if it gets "too good" or better yet "too easy", all it will take is MSFT to require a certificate issued only by them for Windows apps to run and the future of Wine stops.
I think its great the work that has been accomplished and is yet to come, but that it's path to improvement simply brings it closer to its demise?
MSFT will do it in the name of security.
Comment
-
Originally posted by edwaleni View PostWine is great but don't people realize that if it gets "too good" or better yet "too easy", all it will take is MSFT to require a certificate issued only by them for Windows apps to run and the future of Wine stops.
Comment
-
Originally posted by Weasel View PostBad example. Wine can just ignore the certificate and run the app anyway.
Since they willingly leave prior Windows versions behind, I can see them do the same with legacy apps as well.
Comment
Comment