4 ms·
I’ve been writing shipping software for my entire adult life. In my experience, shipping requires compromise. For example, I have found it to be a very bad ide
by ChrisMarshallNY 5y ago
I’ve been writing shipping software for my entire adult life.
In my experience, shipping requires compromise. For example, I have found it to be a very bad idea to schedule a ship project, based on shiny. It’s always a good idea to step back from the precipice, a bit.
The last two years at my last job, we were assigned to work with a startup, staffed by awesomely brilliant folks, to develop a particular kind of software, in one of the new, customized, LLVM-spawned, languages. I won’t get specific.
It did not end well. The devil is in the details. It was a great R&D project, but a lousy ship project.
The app I’m currently developing is being written in Swift (shiny), but using UIKit (b o r i n g), and traditional MVC (b o r i n g), instead of SwiftUI (shiny), and MVVM (shiny). SwiftUI was a thing, when I started the project, but it was still pretty raw, and I had barely started to work with it. The servers are written (for the most part), in PHP. They work great. If anyone has any doubts about the viability of PHP as a server, they should check out the “fishtank graph.” That was the graph that was released, recently, that showed PHP is several orders of magnitude more prevalent in Web server code, than any other language.
I call it the “fishtank” graph, because PHP is this line along the top, and every other language is represented by lines that look like gravel, on the bottom of the tank.
I may have been able to do this enormous app in SwiftUI, but there was no guarantee. There was no doubt, whatsoever, that it could be done in UIKit. If I write in UIKit, I write MVC. UIKit was designed for MVC. I’ve found that it’s always a good idea to use a tool the way it designed to be used. SwiftUI is good for PoP, KVO, etc., and different event-handling models.
It’s coming along great. The quality is amazing, as is the UX, and the performance.
I plan to ease into SwiftUI, by writing SwiftUI versions of my various UIKit widgets. That will be a much better way to learn up on it.
- alexjplant 5y ago> MVVM (shiny) Microsoft tried to make this a thing 15-ish years ago with WPF/Silverlight ... is it experiencing a renaissance? Unfortunately I don't recall too much about its merits (or possible lack thereof) since the last time I read about it I wasn't sufficiently experienced with software architecture to understand what it brought to the table.
- ChrisMarshallNY 5y agoIt’s fairly prevalent in Apple programming. I’m ambivalent about it, but I have yet to do a full-size project with it (like I said, I feel that it is best to use classic MVC for UIKit development). I have used Presentation Manager (MS-defined) for serverside (PHP) code, but that’s different from MVVM for Swift-based stuff for Apple device programming. We’ll see. SwiftUI is fairly radically different from UIKit. I basically like what I see, but I haven’t gone down that rabbithole, yet. I’m very practical. I don’t get particularly distracted by shiny, and have no problems doing stuff like mixing cutting-edge techniques with 35-year-old patterns.