Man I wish Xcode was a decent IDE
Me too. I don’t understand how they release an IDE without Vim emulation or some support for plugins that enable Vim emulation. It’s quite miserable. Last time I checked you had to root the app to install a Vim extension.
SwiftUI tutorials rewritten completely
41–50 of 115 posts
Re: SwiftUI tutorials rewritten completely
#42Earlier quoted context omitted.
Because it’s native to the platform. Seriously, that’s huge. The React Native toolchain is cumbersome to say the least. There’s something to say about a first-class library, meaning one that is being used exactly as designed. I mean, why do people use Javascript? Because it’s the native language of the browser.
Yea I don’t disagree, but what development team has the luxury of choosing SwiftUI? Most places hiring are looking for cross platform “2 developers for the price of one” ... and the burden of dealing with cumbersome react native falls on the developer.
Re: SwiftUI tutorials rewritten completely
#43Why learn SwiftUI? If you want a declarative UI framework wouldn’t you be better served for your time to learn something like React Native or Flutter? I’m not trying to knock SwiftUI, I am genuinely curious what the value proposition is for anyone considering it...
Even with all the rough edges currently SwiftUI+Combine is how I want all my programming to be done from the day they were announced.
Re: SwiftUI tutorials rewritten completely
#44Earlier quoted context omitted.
AppCode. I used to use it a lot, and in many respects it's just plain better than Xcode. You can one-click install a plugin to use vim bindings, for example, whereas in Xcode you have to strip out the code signature so that you can install a third party plugin for vim bindings because, I don't know, fuck you I guess. The problem was that AppCode was always a few months behind Xcode in terms of Swift support, and Inte…
I wish Jetbrains could do what they did with .NET which is Resharper. A plugin for Visual Studio that brought IntelliJ like features and smartness to it. It was a breeze. Unfortunately I don't think XCode is built to handle third party vendors plugins and it never will (which is why Appcode exists in the first place).
Re: SwiftUI tutorials rewritten completely
#45Is SwiftUI just an abstraction over AppKit and UIKit ? Does it bring any widgets of its own - ie something native to SwiftUI as opposed to being wrapped ? (apart from the declarative stuff)
Re: SwiftUI tutorials rewritten completely
#46Man I wish Xcode was a decent IDE
If there's anything you can credit the Google team for, it's using IntelliJ as the basis of the Android IDE.
Android Studio requires a gaming rig to run properly, Android developer forums are filled with discussions on how to not use it in pain.
Re: SwiftUI tutorials rewritten completely
#47Why learn SwiftUI? If you want a declarative UI framework wouldn’t you be better served for your time to learn something like React Native or Flutter? I’m not trying to knock SwiftUI, I am genuinely curious what the value proposition is for anyone considering it...
After you’ve used SwiftUI you wouldn’t want to work with any other framework. Even with all the rough edges currently SwiftUI+Combine is how I want all my programming to be done from the day they were announced.
Re: SwiftUI tutorials rewritten completely
#48Earlier quoted context omitted.
I used Xcode recently and it's gotten a lot better. It's still not as good as IntelliJ or AppCode but it's usable. I remember around when Swift came out, Xcode was so bad that I couldn't even use it because typing was ~1 character/second and it would crash every few minutes. It's definitely recovered from that and I can actually type without lag now.
Xcode had no such problems with Objective-C though... Maybe Swift's design deserves some blame here for years of subpar developer experience.
Like many of Apple’s developer tools, if you stick to the happy path, performance is great. Practically that means compiling your source into a single Swift module and keeping the number of modules low. If you are a “basic” iOS or macOS app with just a couple of 3p libraries things work great. Real world projects are drastically more messy...
Re: SwiftUI tutorials rewritten completely
#49Earlier quoted context omitted.
I think JetBrains has a XCode replacement but I dont do Apple development so I'm not sure if its possible to use it as a complete replacement for developing macOS, iOS and IPadOS apps. Anyone have first hand experience?
AppCode. I used to use it a lot, and in many respects it's just plain better than Xcode. You can one-click install a plugin to use vim bindings, for example, whereas in Xcode you have to strip out the code signature so that you can install a third party plugin for vim bindings because, I don't know, fuck you I guess. The problem was that AppCode was always a few months behind Xcode in terms of Swift support, and Inte…
Then XcodeGhost happened. They try to replace it with Xcode Source Editor Extension but that one is just not as good as Alcatraz
Re: SwiftUI tutorials rewritten completely
#50Earlier quoted context omitted.
I wish Jetbrains could do what they did with .NET which is Resharper. A plugin for Visual Studio that brought IntelliJ like features and smartness to it. It was a breeze. Unfortunately I don't think XCode is built to handle third party vendors plugins and it never will (which is why Appcode exists in the first place).
My Visual Studio is an happy boy without Resharper bloat, never got the point of it.