29 ms·

Because microsoft dominated a market segment with mostly no competition for long enough to make people dependent in a way that users couldn't simply choose an a

Because microsoft dominated a market segment with mostly no competition for long enough to make people dependent in a way that users couldn't simply choose an alternative. There are idiosyncrasies in windows usage that users think are normal, but are actually legacy behavior which can't be changed because it could break other peoples tools. This makes windows users not only locked on the platform but also expect those misbehavior if they try to change. Also consider that depending on the hardware, software or services you use, there is NO alternative to windows. I don't think the same is true for Unity.

stephc_int13 4y ago
Also, yes, the user experience is not that bad, especially these days. I love using Linux and Unix in general, but the legacy idiosyncrasies there are kind of worse.
- Ekaros 4y ago
  I'm kinda sad that we have really ended up with essentially two operating systems or families of such dominating. Unix/Linux/BSD and Windows... Both with their own issues and historic loads... I feel that we could do so much better in modern age if some of the things were just let go, but trenches has been dug and nothing will likely happen.
  - philistine 4y ago
    Uhhh ... macOS is exactly what you're talking about. It's unafraid to let some things just go. They just said during the State of the Union this week that Obj-C and UIKit were legacy tools, and that the future is Swift and SwiftUI. They said it, and I promise you they will deliver on this. I predict that within a decade Apple will truly deprecate UIKit and AppKit and stop any new app from using it. Microsoft has never been able to do that.
    - Ekaros 4y ago
      Isn't it still a Unix derivative? Still have bash or something as cli?
      - sleepybrett 4y ago
        Macos still uses the darwin kernel which is a bsd. Still ships 'terminal', default shell these days is zsh.
    - stephc_int13 4y ago
      Ouch, I was not aware of that. Deprecating Obj-C will probably also deprecate support for C/C++ support. I never used Proprietary Apple tech stack, when I made games for iOS it was C/C++/OpenGL and these days Vulkan with MoltenVK If they deprecate native code, they are going to lose a lot of devs. Never going to touch Swift with a ten feet pole.
      - nmfisher 4y ago
        Swift on iOS still has support for C/C++ interop via bridging headers. I imagine that would be preserved even if Obj-C was deprecated as a broader iOS runtime. Eliminating C/C++ in one fell swoop would be disastrous.
      - galad87 4y ago
        Nothing is deprecated, they just recommend Swift and SwiftUI for new apps. And while they could deprecate UIKit in ten years or more, C and C++ won't be deprecated any time soon, they just starting working on Swift and C++ bridge too.
    - Apocryphon 4y ago
      They will try, but a decade is far too brief for that to happen. Swift was introduced eight years ago and there are still plenty of apps, especially ones belong to large corporations, that contain Objective-C legacy code. Including Apple's own apps. Maybe once SwiftUI gets its Swift 5 moment when there's a release that's stable enough going forward.

stephc_int13 4y ago

Also, yes, the user experience is not that bad, especially these days. I love using Linux and Unix in general, but the legacy idiosyncrasies there are kind of worse.

Ekaros 4y ago
I'm kinda sad that we have really ended up with essentially two operating systems or families of such dominating. Unix/Linux/BSD and Windows... Both with their own issues and historic loads... I feel that we could do so much better in modern age if some of the things were just let go, but trenches has been dug and nothing will likely happen.
- philistine 4y ago
  Uhhh ... macOS is exactly what you're talking about. It's unafraid to let some things just go. They just said during the State of the Union this week that Obj-C and UIKit were legacy tools, and that the future is Swift and SwiftUI. They said it, and I promise you they will deliver on this. I predict that within a decade Apple will truly deprecate UIKit and AppKit and stop any new app from using it. Microsoft has never been able to do that.
  - Ekaros 4y ago
    Isn't it still a Unix derivative? Still have bash or something as cli?
    - sleepybrett 4y ago
      Macos still uses the darwin kernel which is a bsd. Still ships 'terminal', default shell these days is zsh.
  - stephc_int13 4y ago
    Ouch, I was not aware of that. Deprecating Obj-C will probably also deprecate support for C/C++ support. I never used Proprietary Apple tech stack, when I made games for iOS it was C/C++/OpenGL and these days Vulkan with MoltenVK If they deprecate native code, they are going to lose a lot of devs. Never going to touch Swift with a ten feet pole.
    - nmfisher 4y ago
      Swift on iOS still has support for C/C++ interop via bridging headers. I imagine that would be preserved even if Obj-C was deprecated as a broader iOS runtime. Eliminating C/C++ in one fell swoop would be disastrous.
    - galad87 4y ago
      Nothing is deprecated, they just recommend Swift and SwiftUI for new apps. And while they could deprecate UIKit in ten years or more, C and C++ won't be deprecated any time soon, they just starting working on Swift and C++ bridge too.
  - Apocryphon 4y ago
    They will try, but a decade is far too brief for that to happen. Swift was introduced eight years ago and there are still plenty of apps, especially ones belong to large corporations, that contain Objective-C legacy code. Including Apple's own apps. Maybe once SwiftUI gets its Swift 5 moment when there's a release that's stable enough going forward.