waffle

Waffle is a weblog.
The author of Waffle, some guy in Sweden, also occasionally writes stmts.net.

Lately on Waffle

Windows 10

  • I liked the Windows 8 Start screen for what it was. I thought Windows 8 was far too much about the experience of tablet/touch users subsuming everything several hundred million Windows desktop users had committed to muscle memory (or at least the apparently only 6% who know about alt+tab (the guy in that video is also unleashing the fury of Raymond Chen for referring to the “tray”)), but for the select few who had a Windows tablet and enjoyed Metro apps, I’m sure it worked.

    The initial Windows 10 Start menu looked like a great compromise between Windows 7 and Windows 8 as first announced — but the subsequent unexplained redesign dropped almost all of that. The subset of Windows 7 holdouts who want a vertical list of icons and text label items — very likely most of them — will find themselves yelling at live tiles. Or dead tiles, since the “live” aspect is not present for anything except Metro apps of Windows 8 or newer Universal pedigree.

  • With very few exceptions (like the taskbar and the excellent desktop picture) Windows 10 looks like a half-finished thought design-wise. Padding is awkwardly and uncomfortably narrow almost all over the place, and while this may be an effort to appease all the people who went to bits over “wasted space”, it does seem comically obtuse in the hodgepodge of buttonssorry, tiles at the bottom of the Action Center, with the small text edged up in a corner of a huge tap/click target.

  • The control box/icon buttoned window menu dropdown is dead again in Metro apps, meaning I can’t double click the top left to close those windows. (I did retrain. For several glorious months, just before getting my first PowerBook G4, I did go to the top right to find the close button; then I started using OS X where they are in the top left, and then I was back to seeking that corner instead.) Instead I’m activating the back button not once, but twice, winding up god knows where.

  • Oh yes, the back button in the top left (and indeed on the task bar in Tablet mode). Consider the following scenario: going to the Settings app (now finally, apparently, having absorbed a useful subset of the Control Panel’s functionality), finding my way to a setting, clicking a link to go to a related section where a related setting is, and then clicking back.

    The expected result, conditioned not only by common sense but by however many thousands of hours of web browsing is that I’m back at the screen with the link, and can fiddle with the rest of the settings. No, I am instead “back” at the screen from which I would have clicked into the screen that the related setting was found. Note also that the screen I’m referring to is not the section in itself, but the screen containing a sidebar to the left from which I can select sections that then show up to the right.

    To wit: I have a useful button using which I can go up in the hierarchy of settings screens for the current setting (skipping one level in the case of sidebar-equipped screens like the first level). Fair, but don’t call it “back”. Call it, possibly, “up” — anything but “back”. Also, provide an actual history trail. Don’t provide something that looks browser-like, with back arrow buttons and links and mostly plainly and dumbly flow-layouted contents, and then flake out on completing the metaphor.

  • With remarkable and uncharacteristic determination and consistency, Microsoft has taken “Universal apps” and really made them the undeniable “apps that run on Windows” platform. There’s no guessing which platform Microsoft will consider their Windows platform for the future. Where there is guessing is what everyone who’s written Windows desktop apps in C++ with MFC or other toolkits, or .NET with WPF are supposed to be doing. (.NET with Windows Forms is to go cry into a pint and then port to WPF.) It is not impossible that the free Windows 10 upgrade was offered solely to make “transitioning to a platform where people are supposed to write Metro apps under the expectation that more than, absolute tops, a fifth of the Windows user base will be able to run them” a brave and unproven strategy instead of just simply a staggeringly laughable strategy.

    Of the “bridges” to the Universal platform, the run-a-web site-as-an-app solution is brilliant in its simplicity and a keeper, while the bring-your-iOS-and-Android-code-bases solutions are as courageous as they will be Sisyphean efforts (and even if there’s not a lot of established native widgetry consistency to break with, people will not want to use phone apps as desktop apps).

Windows 10 is pretty good in many ways. It is not a mere whitewashing of the Windows 8 platform and endeavor. With it, Microsoft, Windows logo blue in the face, finally exhales after three years, admitting that as much as they need viable tablet/phone building blocks, the Desktop is where their bread is buttered.

In the same way as Windows 7 was the rescue boat that was needed to provide a viable Windows version after Vista, so is Windows 10 when Windows 7 is starting to age faster than XP, due to a world where it is likely to be the only six year old piece of software still in use.

But the new stuff is not new enough. Metro was introduced with a bold vision, applied ruthlessly; while Microsoft has managed to convincingly put the Desktop back in focus, it is being used to run “Metro 2.0″ apps without personality, without ken, without oomph, without stretching for something in the distance. It is possible and maybe even probable that the potluck of mobile and desktop UI elements (hamburger menu, anyone?) cobbled together with some sort of ultimate familiarity in mind was a wiser choice than is plainly visible.

Vista tried to rethink the desktop and fail, Windows 7 saved it and Windows 8 and 8.1 went on a “let’s pretend we don’t have nearly a billion users who’d just like shit to keep working” misadventure. 20 years on from Windows 95, the time has come to redefine what a Desktop can be by embracing what it currently is, but by providing new ideas and new tools, by providing something that is as clearly as can be a follow-on to what has come before, which is familiar but better in every way. Windows 10 brings us a version of Metro, gutted of its originality, mixed out to a bland, featureless grey goo. It has extricated Microsoft from the Windows 8 debacle at last, but at the cost of the clean start that the Windows Desktop so desperately needed – especially since the future of the OS X Desktop increasingly seems to be “iPad” (except for when they steal Snap Assist and no one so much as bats an eyelash), and especially since Windows 10 now seems to be going into an “as a service” cadence with small iterations.

I will be installing Windows 10 everywhere I had Windows 7 and everywhere I had Windows 8. And as I do, I will endure parts of it, I will even straight-out no-joke like a lot of it, but I will weep for the reboot that never was, and I will seriously find myself wondering if the fabled Linux Desktop isn’t the last great hope of reinvention after all. (Until I remember that changing the window widgets is considered wildly extravagant, and that most of them consider reinventing K&R-era infrastructure and replacing stupid fucking X11 fool’s errands. We’re doomed. Dooooomed.)

Officious

How Microsoft Office’s codebase is being reworked to adapt to the new multi-platform requirements is the most interesting thing you’ll watch today, if you’re a programmer. Contains some nice breadcrumbs about how Mac Office development may be tilted on its head, and some brash admissions that the way forward will not be features that only work on one platform, because it’s hell going forward.

Via: Herb Sutter’s usual C++-will-solve-all-your-problems ditty from this week’s Microsoft developer hullabaloo, which contains a slideware admission that you can’t reach 95% of customers by doing Windows versions, but that you need Windows, OS X, iOS and Android to reach 95% of customers. It’s becoming a cliché to chalk all of this up to Nadella at this point, and it really doesn’t matter either way. The point is that the part of Microsoft that previously made damn sure you wrote to something somehow dependent on the Win32 API is now bending over backwards – relatively speaking – to support other things as well.

I Feel Fantastic and I’m Still Alive

Just checking in. Yes, I am still alive.

Furthermore, yes, I am aware that the mode buttons in ThisService on OS X Yosemite has had some sort of pidgin Cthulhu-Klingon accent thrust upon them by an unfortunate accident with bezier path glyph rendering code, lack of foresight specifying an explicit font and a pair of rubber bands. The precise details of the accident are not important because no one has ever managed to duplicate the exact circumstances under which it happened… you get the point, I can still paraphrase the Hitchhiker’s Guide to the Galaxy at the expense of actually getting the intended message across. [Personality authentication complete.] Thank you.

Anyway – a fix for that issue will be forthcoming because just using modern Xcode versions to rebuild the same project with the minor fix in place introduces different behavior in a number of places, and I need to fix these things too.

Older posts »