When I four-finger swipe left for Dashboard, stocks and weather take several seconds to load, and to use the calculator I actually have to click inside of it. And visually they all look like toys that bear no relation to current OS look and feel.
Two-finger swipe-left from right edge brings up Notification Center with weather and stocks always instant (so much faster), and I use cmd-Space for Spotlight for all calculations and conversions without having to click/tap ever, just using my keyboard. And since Spotlight allows me to type complex math expressions with parentheses, I've never had a need for multiple calculators. And then Stickies has a dedicated app.
So except for multiple unit conversions (which I've never needed)... I'm personally very glad we've moved on from Dashboard.
Hot damn! That's the most useful thing I learned today!
I can't even recall how to invoke Dashboard. The fact that was always hidden meant I never used it.
This was a space that was useful, and then became saturated and commercialized to the detriment of usefulness. It was just before we had good off-screen rendering, right as the html-and-js-as-desktop-apps was starting to take off, and when transparency in window rendering was still difficult. I could share a lot more thoughts
Is there an opportunity to fill the void? I'm really not sure. Bear in mind that this was well before the iPhone hit and smartphone apps got huge. Most of the things we did with widgets back then are far easier done on our phones now. Kapsules had some good parity with what Konfabulator and Apple Widgets had offered, and I can't name a single widget for Kapsules, aside from the silly barking hamster, that doesn't ship by default with our phones now.
The widget craze was a fun phase of app development, and no doubt influenced UX and mobile apps, but I consider it merely an interesting footnote now. If anyone is interested in the source code for Kapsules, I can probably dig it up from one of my old HDDs. It was written in C# on .NET 4.0.
I missed multiple calculators by default as in Windows. I found a simple Apple Script accessed with 'mcalc' that made this a bit easier for me.
do shell script "/Applications/Calculator.app/Contents/MacOS/Calculator -background >&/dev/null&"
http://www.markc.me.uk/blog/files/MultiCalc.htmlI use multiple calculators for quick reference and when testing various implementations of my work, and was baffled that Apple explicitly stopped my from doing that with their stock calculator.app
open -n /System/Applications/Calculator.app
works for meEdit: and fun fact, if you hate Electron, don't go looking under the covers of Dashboard... it's tons of old-school web tech cruft. Fun, if you're into it.
Also siri can be configured to have text-only input. a long hold of cmd-space will pop up an additional window where I can type "weather in london" or "time in london" etc.
Similarly, someday MS will remove live tiles from the start menu. It’s inevitable, but clearly internal politics are keeping the feature around. Guaranteed that 99% of humanity will rejoice when it happens, but equally guaranteed that someone on HN will express how appalled they are that a company as big as MS didn’t choose to keep the feature alive for the sake of the handful of people who liked it.
(And I'm sure a 3rd party replacement will pop up, if there are enough frustrated users).
A good example was usage of LLVM on the PPC->Intel transition which then helped when they ported OSX to ARM (ie, iOS, nee iPhoneOS).
Another is Safari (which was useful/needed on Mac at the time) but more importantly was critical in making the iPhone successful - mobile browsing sucked before the iPhone.
I’m not an Apple insider, but I don’t believe LLVM played a substantial role in either the PPC-to-x86 or x86-to-ARM-for-iOS ports — the former was accomplished with Rosetta and a lot of bugs.
The current rumor, OTOH, is that Apple’s collection of LLVM bitcode for apps is intended to allow painless migration for applications when macOS is switched over to ARM.
Has anyone been able to execute built-for-x86_64 bitcode on aarch64 ever?
I will say, however, that executing LLVM bitcode on different targets than the compilation machine is a subject of active research. It's one of the things that I work on in my day job.
Bitcode is not [12:30] a magic solution, though. You can't take a 32-bit app, for example, and run it on a 64-bit device. That kind of portability isn’t something that Bitcode can give you, notably because that is something that's visible in C. As you're writing C code, you can write #ifdef pointer size equals 32, and that’s something that Bitcode can't abstract over. It's useful for very specific, low-level kinds of enhancements, but it isn't a panacea that makes everything [13:00] magically portable.
What’s funny, is later on after Apple shipped a 64 bit chip for the Apple Watch. He admitted that forcing developers to ship watch apps as bitcode allowed Apple to recompile all of the third party Watch apps on the fly to support it, he knew that was coming, but couldn’t say anything at the time.
https://twitter.com/clattner_llvm/status/1046960724646465541
It was still the fastest way to access:
- Multiple calculators
- Multiple sticky notes
- Multiple unit conversions
- Stocks
- Weather widgets
Notification center as currently implemented is just not cutting it. The amount of widgets I can quickly access is dependent on screen size, and worse, they're moving targets! — The weather widget causes all the ones below it to shift up and down while it loads. Not to mention I can't see my notifications when in Widget mode.
What a sad state of affairs for what was once a very powerful feature.
EDIT: For fun here's Steve Jobs' intro to Dashboard widgets https://youtu.be/XQQPTtdzBig?t=4872