Earlier 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.
SwiftUI tutorials rewritten completely
91–100 of 115 posts
Re: SwiftUI tutorials rewritten completely
#92Earlier quoted context omitted.
If you only target iOS for example it's a no brainer. There are use cases where you absolutely have to use it, those are currently Home Screen widgets and WatchOS Apps + complications. I would not be surprised if more SwiftUI-only use cases were progressively added. SwiftUI is also cross-platform, in Apple ecosystem. That is, you can develop all of your components and have them work on iOS and macOS. Then glue them t…
"cross-platform, in Apple ecosystem". Please, let's not gobble that crappy apple PR spin on what that term means. Cross-platform never meant "just an iphone and a mac os with the correct version". SwiftUI looks like a very cool tech, but it isn't "cross-platform", period.
It might be crappy marketing spin but it's hard to call anything other than the web cross-platform by that definition. It's not just iPhone and a Mac either, it's every Apple platform that has a screen. I don't think Flutter or React Native can claim that despite being called cross-platform.
Re: SwiftUI tutorials rewritten completely
#93Earlier quoted context omitted.
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.
So weird. I guess it might be because 99.9% of swift developers want as little vim as possible in their lives.
Re: SwiftUI tutorials rewritten completely
#94So far dealing with stuff like PayKit SwiftUI integration still feels really bad. There's just tons of stuff expecting UIKit and it will take a while before all of that stuff is ported. SwiftUI is really great, Combine can be hard to get into for people not initiated in Reactive and generally it's as fast to build stuff in as Flutter without dealing with the tragedy called Dart.
I sometimes wonder why do we continue to get macOS update. Were any of those "user" features really better? I wish they spend more time looking into Xcode, developer documentation etc. And it is 25M developers at $99 a year. That is $2.5B. And it is looking less than $10M a year investment into Xcode.
Re: SwiftUI tutorials rewritten completely
#95Is 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)
https://stackoverflow.com/questions/64049757/are-swiftui-com...
Re: SwiftUI tutorials rewritten completely
#96Re: SwiftUI tutorials rewritten completely
#97Re: SwiftUI tutorials rewritten completely
#98Earlier quoted context omitted.
>They should have some way of showing what docs have been updated Back when I used wrote iOS crap, I used dash as a quick reference for APIs.That was pretty good at alerting me to documentation changes, since it has to download an update. https://kapeli.com/dash I only started using it (never did buy it) because I was used to using zeal, a free-software alternative. https://zealdocs.org/
I like Dash, I bought it. But unfortunately the version upgrade from 4 to 5 introduced some mandatory UI changes that made documentation lookup much more cumbersome. Looking up a function now takes several user interaction steps, instead of just one in Dash 4. I'm still on version 4. If anyone have alternatives, I'm all ears.
Re: SwiftUI tutorials rewritten completely
#99Re: SwiftUI tutorials rewritten completely
#100It’s pretty cool that from the very first step that they are introducing how to use accessibility modifiers to improve support for voice over.