The pdf reader scenario is just one of many cases the desktop on other OS's became a vector to spread ads while the linux has only improved over time. Considering the popularity of android, it has the same problems as windows in terms of apps being just a way to spreads ads; fortunately f-droid saves me from these.
So, I hope things will continue to improve on the FLOSS desktop. Hope it brings more users too.
With regard to the electron apps... With 4 cores and 8GB of RAM, I really don't care that much about the performance loss. It feels a bit inconsistent sometimes, but I like to know that I'm using the same app as my colleagues on other OS's.
What’s shocking to me is how bad first party software is getting. Acrobat DC kills the battery on my MBP doing, among other things, constantly running some cloud updater thing. It’s worse at browsing PDFs than a decade ago. Same thing for Outlook. They’ve started integrating a bunch of web technologies into it. It actually has less features now than before (tasks and notes redirect you to the website).
And I don’t just mean that the latest version is slower on older hardware. It’s vastly slower on current hardware than the old versions were on the hardware that was contemporary at the time. My work machine is a ThinkPad i7 that boosts to 4.2 GHz. Just hitting Win-Right to snap Outlook to one half of the screen causes it to visibly spasm.
Just apt-get installed xfig. Still works pretty well.
Native Mac dev on the other hand is another matter. The situation has improved some since then, but it's not too different from when I picked up Objective-C + Cocoa/AppKit back in the early-mid 00s, where nearly all instructional material came in the form of print or random tidbits scattered across various developer blogs.
There are some individual doc pages that seem to be auto-generated and a bit sparse when it comes to useful context.
For instance, sometimes X object cannot be instantiated on its own according to its relevant doc and you need to use Y internal API that provides it instead. However, there's no explanation as to why or what can be done instead, which doesn't help someone who's very new to the architecture and frameworks.
It's not like people are developing using their mobile device. I'm sure the online docs are assumed to be read by people on a non-mobile device. I can't imagine trying to read docs on mobile while banging out code on a laptop. Seems pointless, especially if the docs have links for downloading something or what not.
It’s really some of the only documentation I’ve come across that can’t be read on mobile, and it’s all because of a sidebar which isn’t even a good reason.
https://skim-app.sourceforge.io/
(For Windows there is SumatraPDF: https://www.sumatrapdfreader.org/free-pdf-reader)
It's good.
So the endgame is probably resigning to having lousy non-native software until/unless there once more comes a time with a single dominant/monopoly platform where people just make a single native app for everyone.
I went from a shitty cli and a laggy browser extension to an excellent native feeling 1password app that is fully integrated into my desktop environment. I don't notice any lag, in fact it feels snappier than the native windows version on my handful of years older laptop.
Unlike many other apps I use (Spotify, vscode, intellij, Firefox) I don't notice any difference in system load when it's running too.
Call it 2factorpass or soemthing.
[0] And, for that matter, most of their other operating systems.
[1] WindowScene, technically
[2] Astute fans of macOS history might remember this sounding quite familiar. When Steve Jobs bought Apple with Apple's money, he wanted to basically continue NeXT as it was (even the Windows NT port) and replace System 7 entirely with lightly-rebranded OPENSTEP 5 and a VM (dubbed the "penalty box"). This failed so dramatically the whole project was cancelled/rebranded as "OSX Server", and Apple announced Carbon to provide Classic APIs with minimal changes on OSX.
Regarding point 2, that was thanks to Adobe and Microsoft pressure to keep targeting Mac platforms. Sean Parent from Adobe / C++ fame was a key person in this process.
- Microsoft: Don't break existing APIs, period. If the existing one can't be extended, write an entirely new system to replace it (e.g. XAML, UWP XAML) and leave the old system in the OS forever.
- Google[1]: Don't complicate your code with backwards compatibility. If some change would make the code better, scan the entire Google monorepo and recompile the world against your new version, and then tell our AppEngine customers they have about a week to transition.
[0] Carbon wasn't deprecated until 64-bit Intel support happened, and was only removed alongside 32-bit Intel support. A Carbon universal binary can target a disturbingly large range of macOS versions - basically Mac OS 8 up until macOS Catalina.
[1] Mercifully, the Chromium and Android teams actually don't buy into this.
Perhaps I should have said feature frozen on-the-way to deprecation instead. All new development in lang/ux is happening in Swift/SwiftUI.
https://medium.com/geekculture/swift-5-uikit-is-dying-14b475...
https://medium.com/geekculture/swift-5-uikit-is-dying-part-2...
Also at WWDC 2021 there were a few Objective-C talks.
> The Web is far more stable than native UX widgets, breaks less often nowadays
I got a good laugh on those fibs.
Objective-C isn't going anywhere, and AppKit has been mostly unchanged for longer than nearly any front-end framework you can name has existed.
I am sort of starting to maybe substitute Scrivener for it. Which is a super-amazing native app designed for writers that sets a pretty high bar for anyone who wants to "continue to improve writers’ workflows in the coming decade and innovate in that space".
Most of the apps I've installed on my Mac lately are to change the way the OS behaves, to be honest. Like, Bartender is useful and makes dealing with all the little utilities that want to live in the menu bar a lot easier. I'm an artist and Illustrator is my main medium; Time Sink's tracking tells me that I've spent about 3.3 days in Illustrator so far this year, and 9.5 days in Safari, and everything else is measured in hours and kinda looks like a rounding error compared to those two apps.