31–40 of 573 posts
And it runs on Linux.
So can we finally say that Hell has Frozen Over?
Microsoft Open Sources Parts of Visual Studio and releases Linux Software.
Apple open sourced their language and it will work on Linux.
No, Apple announces they intend to open source Swift at a future date. That's not the same as doing it.
This places Swift right along Golang and Rust as the new interesting language.
No, Apple announces they intend to open source Swift at a future date. That's not the same as doing it.
As far as HN comments go, this one sets a pretty low bar. Is there even one doubt that this will happen? If not, the pedantic distinction between "announce they intend to" and "doing it" is extremely worthless...
No, Apple announces they intend to open source Swift at a future date. That's not the same as doing it.
As far as HN comments go, this one sets a pretty low bar. Is there even one doubt that this will happen? If not, the pedantic distinction between "announce they intend to" and "doing it" is extremely worthless...
I will surely be downvoted for speaking so off the cuff, but I haven't really enjoyed swift so far. How has the general developer reception been to the language, not just with respect to obj-c, but also to java or any other turing complete language?
The switch when dealing with a combination of C/C++ and Objective-C source was not really a problem. But trying to interface a C++ library into a Swift application is less than a fun experience.
Personally, while the language is fresh and seems pretty good (it has some great additions), I still prefer Objective-C. I guess I'm waiting for better integration with existing libraries.
I will surely be downvoted for speaking so off the cuff, but I haven't really enjoyed swift so far. How has the general developer reception been to the language, not just with respect to obj-c, but also to java or any other turing complete language?
It's hard to realize most of the performance benefits when everything you're interacting with requires objc_msgsend or uses NSArray / NSDictionary.
As well, it's far less 'scripty' than Obj-c. The type system in swift really leaves something to be desired in terms of typing types. The point of Obj-C was kind of to avoid writing the kinds of apps where a great type system would really shine, swift lets you build those kind of apps, but in my opinion most of the time we shouldn't be building them.
Your project probably doesn't need 1,000 developers on it who need solid interfaces and type checking to make sure that everything is going according to the UML diagram. It probably needs 2 or 3 developers who talk to each other, add asserts to their code, and a type system thats a little forgiving.
ObjC is a language that has everything you really really need, and left out the 1 thing you kinda wanted in exchange for leaving out the thousand 1 little things that everyone else wanted too. Like for example exceptions, sure they're there, but it's not idiomatic and when you program without them you realize what a crappy idea they were in practice. In day to day coding NSError is 1000x better than exceptions.
Swift interfaces with C and Objective-C natively right? I can't wait to see web servers written with it.
This places Swift right along Golang and Rust as the new interesting language.