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)