{"id":37928,"date":"2022-12-16T14:30:37","date_gmt":"2022-12-16T19:30:37","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=37928"},"modified":"2022-12-16T14:30:37","modified_gmt":"2022-12-16T19:30:37","slug":"sunsetting-appcode","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/12\/16\/sunsetting-appcode\/","title":{"rendered":"Sunsetting AppCode"},"content":{"rendered":"

Anastasia Kazakova<\/a> (Hacker News<\/a>):<\/p>\n

\n

Since the release of AppCode 1.0 11 years ago, we’ve been applying our expertise to make coding for iOS\/macOS more enjoyable. We’ve had many accomplishments, including first-class C++ support (from which CLion, our cross-platform C\/C++ IDE, was born), an extremely fast release of initial support for the new Swift language, and finally, Kotlin Multiplatform Mobile technology, which combines our passion for Kotlin with our knowledge of mobile technologies.<\/p>\n

While we’ve had some growth in terms of adoption, we didn’t reach the market share we had hoped for. We believe that the time has come to sunset the product and focus our efforts in other directions.<\/p>\n<\/blockquote>\n\n

Jacob Gorban<\/a>:<\/p>\n

\n

I’ve used this IDE on and off for many years. It’s got so much stuff that put it way beyond Xcode. At the same time, it was also lagging in some respect, and Apple’s speed of change with its tooling was probably hard to keep up with.<\/p>\n<\/blockquote>\n\n

Dave Verwer<\/a>:<\/p>\n

\n

Some people will dearly miss it but never quite made it big enough in the Swift development community to become mainstream. It got close, though, especially a couple of years after it first launched.<\/p>\n

Competition in this area is a good thing, but with Xcode being so good and VS Code’s support for Swift getting better every day, it’s an extremely tough market to enter with a paid product.<\/p>\n

The reasons behind subsetting AppCode make sense, but the Swift tools ecosystem will be poorer without it.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n