4 ms·

I think he's referring to more mature languages like C#. Many features which are just now being introduced in Swift have existed for over a decade in .NET langu

I think he's referring to more mature languages like C#. Many features which are just now being introduced in Swift have existed for over a decade in .NET languages. Everything old is new again... I would love to see something like LINQ make it into Swift.

s73v3r 11y ago
"Many features which are just now being introduced in Swift have existed for over a decade in .NET languages." And nobody but insecure people give a crap. The rest of us just want to use good tools to get our jobs done.
- epoch1970 11y ago
  With Microsoft's recent push to make technologies like the .NET CLR, C#, ASP.NET, and so on available on non-Windows platforms (such as Linux and OS X), this does become a factor for a great many more developers. On one hand, we can choose a younger, less-mature language/platform like Swift. On the other, we can choose C# and .NET, even if we're not targeting Windows, and get a very mature and capable language with a superb standard library, and a very large existing user community. Whether they like it or not, Swift and its community will have to compete with what .NET offers. As it currently stands, Swift is likely on the losing end of many of these competitions in many cases. Will this change in the future? Perhaps. But it will take a lot of effort from the Swift team and its supporters.
- programmarchy 11y ago
  Don't get me wrong, Swift is a fantastic improvement over Obj-C. I am an iOS developer by trade and it makes my life much better. However, in a past life I worked with C#, and still find myself yearning for some of its features. One area Apple has a huge leg up is its API design. All of Apple's frameworks are well thought out and easy to use. Microsoft, not so much. One glaring example is Bluetooth: CoreBluetooth is a straightforward abstraction, whereas Microsoft's is a total Frankenstein shit show.
davidgrenier 11y ago
If only that was enough, but C# has been playing catch up on F# for the last three revisions (the last one still being worked on) and will likely never catch up. When a giant like Apple gives itself a clean slate to work on designing a new language, it's die-hard fans deserve better than the rag tag mess the OP has to get into and yet can't help but simply be satisfied with respect to what he had to deal with before.

s73v3r 11y ago

"Many features which are just now being introduced in Swift have existed for over a decade in .NET languages." And nobody but insecure people give a crap. The rest of us just want to use good tools to get our jobs done.

epoch1970 11y ago
With Microsoft's recent push to make technologies like the .NET CLR, C#, ASP.NET, and so on available on non-Windows platforms (such as Linux and OS X), this does become a factor for a great many more developers. On one hand, we can choose a younger, less-mature language/platform like Swift. On the other, we can choose C# and .NET, even if we're not targeting Windows, and get a very mature and capable language with a superb standard library, and a very large existing user community. Whether they like it or not, Swift and its community will have to compete with what .NET offers. As it currently stands, Swift is likely on the losing end of many of these competitions in many cases. Will this change in the future? Perhaps. But it will take a lot of effort from the Swift team and its supporters.
programmarchy 11y ago
Don't get me wrong, Swift is a fantastic improvement over Obj-C. I am an iOS developer by trade and it makes my life much better. However, in a past life I worked with C#, and still find myself yearning for some of its features. One area Apple has a huge leg up is its API design. All of Apple's frameworks are well thought out and easy to use. Microsoft, not so much. One glaring example is Bluetooth: CoreBluetooth is a straightforward abstraction, whereas Microsoft's is a total Frankenstein shit show.

davidgrenier 11y ago

If only that was enough, but C# has been playing catch up on F# for the last three revisions (the last one still being worked on) and will likely never catch up. When a giant like Apple gives itself a clean slate to work on designing a new language, it's die-hard fans deserve better than the rag tag mess the OP has to get into and yet can't help but simply be satisfied with respect to what he had to deal with before.