Writing Mac and iOS Apps Shouldn't Be So Difficult
inessential.com
Writing Mac and iOS Apps Shouldn't Be So Difficult
1–10 of 10 posts
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#2100% agree on this!
And I’d like to add it also should not be so difficult architecture-wise. As an experienced (10+ yrs) iOS/macOS developer, when I start a new project, I have to do a ton of architecture to have a correct project base, and I find it weird. It should be builtin. At least we should have something, which I could change if I would disagree with the chosen architecture, but currently we have just pretty much nothing.
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#3I think everything Brent says applies far beyond Mac and iOS apps. The engine + interpreted DSL architecture just makes so much sense.
Are there other examples of software built this way?
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#4As someone who did a ton of VB5-6 dev work back in the day, the same applies to all platforms.
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#5I think everything Brent says applies far beyond Mac and iOS apps. The engine + interpreted DSL architecture just makes so much sense. Are there other examples of software built this way?
Electron.
Brent seems to have something else in mind. I think many people would appreciate some other engine+DSL options.
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#6I think everything Brent says applies far beyond Mac and iOS apps. The engine + interpreted DSL architecture just makes so much sense. Are there other examples of software built this way?
Tcl/Tk is a good example of this.
I would love to see a modernized mobile compatible rethinking of Tcl/Tk.
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#7I think everything Brent says applies far beyond Mac and iOS apps. The engine + interpreted DSL architecture just makes so much sense. Are there other examples of software built this way?
Tcl/Tk is a good example of this. I would love to see a modernized mobile compatible rethinking of Tcl/Tk.
Except Tcl/Tk doesn't use native controls. I like the Tcl language, but the UI always looks and feels weird. A fork that uses native controls and adhere's to platform conventions would be nice. For example, on iOS app settings should be in the system settings app.
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#8Earlier quoted context omitted.
Tcl/Tk is a good example of this. I would love to see a modernized mobile compatible rethinking of Tcl/Tk.
Except Tcl/Tk doesn't use native controls. I like the Tcl language, but the UI always looks and feels weird. A fork that uses native controls and adhere's to platform conventions would be nice. For example, on iOS app settings should be in the system settings app.
It actually does use some native controls on Windows and macOS. On Linux and UNIX it is meant to look like Motif, which was the most popular toolkit on those platforms at the time.
There’s also the themed Ttk package which has some themes that look more modern…
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#9Just compile .NET WPF in Avalonia and be done with it.
Re: Writing Mac and iOS Apps Shouldn't Be So Difficult
#10Either way, expect no HyperCard (or work-alikes) from Apple. But how about other vendors? What about open-source projects? Nothing there, either. Oh, there is no shortage of attempts. And all of them are failures for the same reason: they insist on being more capable, more complexity-laden than HyperCard. And thus, none of them can readily substitute for it.