6,027 karma · joined January 10, 2019
It was made worse since desktop keyboards lacked the feature so you couldn't practice/learn the UI on anything but MacBooks. Keyboard shortcuts were far more useful since they worked on any Mac and whether or not you were using an external keyboard.
That lack of external keyboard support also meant developers couldn't write decent interfaces for the TouchBar unless they had the right MacBook. The simulator was not sufficient to actually test real world usage for positioning/ergonomics.
I found it to be a top to bottom failure of a feature. Small OLED screens on physical buttons would have been far superior ergonomically. Using the space for better cooling on the i7 and i9s would have been a much much better use of that space.
No. Neither can be trusted as far as you can throw them. They're both incredibly invasive data brokers. Their customer facing products are just vehicles to show ads and Hoover up more PII and behavioral data on everyone.
Thats with all my appliances being electric and superfluous crap running like a 24/7 file server running. Because my power is so cheap I don't have any problems running that kind of stuff.
Well rational thinking people wouldn't. A great many using CSAM as a wedge to de-anonymize the Internet or institute regressive "profanity" laws are often neither.
Tiger and Leopard were sprawling releases. Tiger covered 32-bit and 64-bit PowerPC, then 32-bit x86, then 64-bit x86 Macs. Tiger was also what I guess I'd say is the first "modern" OSX release, with subsystems like launchd and a more mature OpenDirectory replacing older NeXT subsystems.
Leopard in my experience was a train wreck. It shipped a lot of new features, both user facing and back end frameworks, but the development was seriously impacted from teams losing engineers to iOS. Leopard had features planned assuming 100% availability of SWE's resources but ended up with 40-50% of SWE's resources (made up numbers based on my feels at the time). Many new frameworks in Leopard did not land or get stable until very late in the development cycle which meant everything downstream had to scramble right before GM. It was 100% the case that Leopard was not really stable until 10.5.8 and still sucked IMHO.
There was a lot of clean-up needed in MacOS and that was Snow Leopard. It was not a perfect release but 10.6.3 (the second disc pressing IIRC) and onward were very stable. Dropping PowerPC support really helped focus QA since they didn't need the massive array of test hardware Tiger and Leopard required. You also didn't need to wrangle builds for four architectures, including multiple compilers as a few libraries (if not whole frameworks) were compiled with ICC on x86 for performance reasons.
The "Snow Leopard wasn't that great" meme is weird. I'm sure it had its problems like every OSX release did. Unfortunately most OSX releases broke someone's workflow[0]. Snow Leopard ware no different. But it was always billed internally as a "no new features" release and those features that it did ship faced a very high bar to get in the release. I definitely look back on Snow Leopard as a high water mark for macOS quality in terms of a release.
The thought frankly horrifies me. I hate an accessible and efficient web!
None of this is helped by how slow the Magic Link is. Supposedly the DataRover 840 was much faster but I've never owned one to tell for sure.
The UI of the Newton MessagePad (I own several) is far from perfect but makes much more sense than MagicCap. It also requires fewer taps to reach different functions.
Every once in a while I'll pull out my Magic Link but the insanity of the UI just inspires me to put it back in a box.
For CPU inference on old hardware I don't think q4 offers any benefit over q8 since the AVX unit doesn't support such small floats. I don't even think AVX supports 4-bit int math. IIRC AVX2 does.
With space manufacturing the first widget out of a factory costs trillions of dollars. There's also few if any raw materials that are far more abundant in space than here on Earth (at orders of magnitude smaller cost).
I learned Photoshop well enough back in the day to do cool stuff and make a few bucks on the side doing graphic design. I'm not a professional graphic designer at all so it never made sense for me to get on the version treadmill. Even today it does everything I need and more.
Adobe got paid for the work they did. I've gotten incredible value out of my purchase since I've used it so long and the cost has amortized over decades.
Subscriptions imply change. I don't necessarily want change. If I buy something that suits my needs...it already suits my needs. Adding more shit isn't necessarily a boon. Changing the behavior or look with a new update is infuriating. This is especially true of complex software that takes time to learn.
For a developer selling a subscription the strategy of locking up data is entirely rational. They'll keep getting money no matter what they do because they're holding my data hostage. It's a model I have no interest in.
Even better is when they decide to shut down or get bought out. If the subscription shuts down there's no amount of money I can pay to get it back.
¹ Terms and conditions apply.
I find 2006 an interesting horizon. It was then that the average home computer massively jumped in processing power compared to the software running on it. For the vast majority of users the computer spent more idle time waiting for input than users waited for output. Of course for some users there's never enough power but for most all of their tasks were effectively instant. Even heavyweight (for the time) stacks like Java ran incredibly well. He'll even Emacs could run well!
Then the curve seemed to invert. Hardware kept getting more capable with even faster CPUs, more cores (on common consumer machines, and more RAM. As the article points out a "lightweight" Linux DE with native apps really flies on such hardware.
But more development seemed to move to the web. More JavaScript required more powerful JS engines and those are up more and more memory. More shit loaded into the DOM means more and more objects on the heap with more pointer chasing.
Modern stacks are really only fast because modern computers brute force their way through them. A simple CRUD type task that fly as a VB or Delphi (neither stack performance kings) app on Windows 2000 now requires a 2GHz dual core CPU with 4GB of RAM as a baseline thanks to it now being a web app.
Using a twenty old machine with native applications and the CLI feels to me like a super computer compared to the computers I first used (Apple IIs). A Core 2 Duo is a stupidly powerful CPU for most tasks. If you can get by with a command line workflow even a Core 2 Duo is crazy fast.
/soapbox
I've run into a lot of "UI designers" that were just graphic designers that lucked out getting a job in a software company. They design and compose the UI for static screenshots like they would do a 2D graphic composition. Far too often they'd hand off Photoshop PSDs they would expect a developer to turn into an actual UI. They don't follow a HIG document or respond to any pushback with "you have to know when to break the rules" (they do not know when to break the rules). A good UI designer is worth their weight in gold. In my experience most are worth their weight in very low grade playground sand.
Also the genocides.