Comments on: #36 ObjectiveC2Swift Review http://swifting.io/blog/2017/02/14/36-objectivec2swift-review/ Sharing passion in Swift Sat, 06 Oct 2018 15:08:13 +0000 hourly 1 https://wordpress.org/?v=4.9.8 By: Alex (Swiftify) http://swifting.io/blog/2017/02/14/36-objectivec2swift-review/#comment-134 Fri, 24 Mar 2017 20:17:15 +0000 http://swifting.io/?p=866#comment-134 Just wanted to say “thanks” again to the swifting.io team for the review!
We have been working hard this month to specifically address all issues found in this review, and now we got everything in “the could be better” section covered!

We do continue to work on the most considerable improvements, such as:
– Auto-detection between let and var declarations;
– Support for public vs private accessors depending on the scope;
– Using Apple SourceKit to precisely import Obj-C to Swift method mappings.

Any feedback or suggestions on what else should we prioritize are definitely welcome!

]]>
By: Alex (Swiftify) http://swifting.io/blog/2017/02/14/36-objectivec2swift-review/#comment-122 Tue, 21 Feb 2017 11:20:28 +0000 http://swifting.io/?p=866#comment-122 The best approach I’ve seen undertaken by larger companies is making it a rule of thumb to write any *new code* for a (formely Obj-C) project in Swift.
Xcode offers great interoperability between Obj-C and Swift out of the box.
Thus if a developer needs to change e.g. a View Controller class, remove corresponding Objective-C files and replace them with Swift versions (you can still use Swiftify for that, Xcode extension comes in handy here).

]]>
By: Michał Wojtysiak http://swifting.io/blog/2017/02/14/36-objectivec2swift-review/#comment-120 Sun, 19 Feb 2017 16:39:28 +0000 http://swifting.io/?p=866#comment-120 Hi Darek,
for the most part you have answered yourself 🙂 I definitely recommend the tool to do snippets conversion, even entire files. I would risk to recommend it to small projects where you know code well too. There is nothing stopping you from removing pieces of code after conversion. It frees developers from tedious typing easy stuff. Hard stuff has to be rethought anyway.

With the big projects, might be bigger than rewrite, especially if you want to redesign architecture and patterns which is most bigger projects need after some time. Even then the tool is useful to convert simple files or snippets and you would just do final Swifty fixes.

Cheers
Michał

]]>
By: Darek http://swifting.io/blog/2017/02/14/36-objectivec2swift-review/#comment-117 Tue, 14 Feb 2017 23:55:39 +0000 http://swifting.io/?p=866#comment-117 Great article and an interesting piece of a software!

However, could you recommend this kind of tool for a full project conversion? If migration from Obj-C to Swift is done manually, the outcome is often much shorter, simpler and safer (also because moving the old Obj-C codebase to a newer version of the SDK). If there is no time for manual migration and improvements, probably there is also no time for checking the whole converted project for potential bugs which, in my opinion, can be very time consuming. Additionaly Swiftify is not a cheap solution.

On the other hand it seems to be the perfect tool for converting Obj-C snippets from the stack overflow and use them natively in our Swift project 🙂

]]>