Readit NewsDeleted Comment
I’m all for paternity leave (I’m a self-employed father of two so had to create my own). But let’s start with moms, or at least a parental bucket that either parent can draw from.
How much effort would it be worth avoiding to spend a week every year ?
Sure the weeks can add up, but so does the time spent on low level abstraction, and refusing to adopt better tools when the whole environment in changing around (e.g. there is no mention of native mobile environments. Would it be churn use to Swift instead of non-ARC ObjectiveC ?)
Every answer on Stackoverflow about Swift has several answers, one for each api version. Any time you grab some Swift code from the web or an older project, it's not going to work.
Avoiding the churn isn't an option since new Xcode versions drop support for old Swift versions. And only the two latest Xcodes will run on latest macOS. They even drop the support for the conversion tools. So if I go back to an old Swift project now, it won't compile in my Xcode, nor will my Xcode help convert the code to modern. My only option is to run an order version of Xcode in a VM to convert the code.
If I'm writing a library I want other people to use or share between projects, I'll still do it in Objective-C. Apps I do in Swift but I find it annoying.
I still have 15 year old non-ARC Objective C libraries. Why spend the time updating them when the are debugged and work fine?
Every time I have to do a Swift version update I introduce bugs.
I maintain a cross platform desktop app for Windows, macOS and Linux.
Windows is the best, 32 bit versions going back 15 years still work no issues. macOS is next, 32 bit don't no longer work, but 64 bit versions still work going back 5+ years. Ubuntu is by far the worst, some library I depend on changes it's API pretty much every year, and the old version is removed, breaking my app.
The solution appears to be Flatpak which bundle up the app with all it's required libraries. However I'm not sure how to make this work for plugins. Would each plugin need to be in it's own Flatpak? It's insane.
I think the most useful thing for me is I can call it from lldb and immediately dump buffers to my terminal while debugging.