I’m writing this in Safari, the genesis of the WebKit project, while listening to music on Spotify, a WebKit-based music player. On my other monitor is GitHub’s Atom, a really damned fine programmers’ editor that has its roots in WebKit (to the point where you can inspect it and change the UI with stylesheets).
Just imagine if Microsoft had continued to actively develop, and perhaps even open-source, Trident (the IE rendering engine) in the early 2000s. (On second thought…best to just leave that alone.)
The other day, I upgraded my wife’s MacBook Air to OS X Yosemite. Immediately, her first concern was that the UI text was harder to read. This is, in part, due to Helvetica Neue replacing Lucida Grande, but also because Yosemite’s LCD font smoothing seems rather harsh on non-Retina. Fortunately, a Terminal command makes for a crisper and easier-to-read display:
I can only see peering agreements between companies and ISPs increasing costs for what we would find as acceptable speeds now and choking off innovation online for those except the most capitalized (or connected), and that is a damned shame.
Blocking, even on a public account, is surprisingly effective at dealing with low-grade harassment. Most harassers just aren’t that invested in the person they are bothering, and putting up the tiniest roadblock will make them move on to their next target. I had this conversation with a Googler shortly after G+ shipped, as its blocking behavior was at the time the same as the new Twitter behavior. I have no idea what it is now because I hate G+ and don’t use it, and I realized that this may be unintuitive to someone who hasn’t experienced harassment before – but trust me, as someone who has, it works a lot of the time. Which is great!
A few observations from a little over a week on the final release of OS X Mavericks (which is worth $20 and I still cannot believe Apple released for free):
Safari 7 might be good enough to switch to permanently. It just absolutely flies and its ability to pick out links from my Twitter timeline and present them as a continuous reading list is really nice (unless a friend gets hacked and sends spam, anyway).
I just replaced the battery in my MacBook Pro on Wednesday, and I am getting better life out of it with Mavericks than any prior operating system version. Over the last few years, Apple has been steady at work bringing features back to OS X from iOS. Seeing what they’ve learned from engineering for mobile power consumption come back to the Mac just enhances the value of the hardware that much more. I particularly like the ability to see which programs have the most “energy impact” (their terms, not mine) on the machine in Activity Monitor — a great nod to power users from a company that is increasingly struggling with power users, IMO.
The UI feels much more responsive. It really is impressive how my aging MacBook Pro still feels fresh and plenty fast even on the newest OS X upgrade — I’ve gotten over four great years out of it and it looks like that will continue for at least one more year. I am more than a little surprised to hear that people are having issues with performance of all things — by all measures, performance is up across the system.
I never knew just how many sites disabled form autofill until the advent of iCloud Keychain. I wonder if sites will rethink their policy on form autofill for login pages now that Safari can generate strong passwords on autofill-enabled forms. I also wish iCloud Keychain would have gone as far as its MobileMe predecessor; it gets awfully inconvenient to retype some exceedingly complex passwords in locations other than Safari.
Multi-monitor support in Mavericks is such an improvement over the Lions it isn’t even funny, but it still has some room to improve. My typical workstation setup puts my MBP directly underneath my external monitor; the screens are positioned to stack one on top of the other. It works well with one huge caveat: the Dock (which I align on the bottom of the screen) doesn’t follow me from screen to screen. It is undoubtedly difficult to get the Dock to take a vertical stack into account, I can imagine, but I can’t be alone in this configuration.
I’ve signed up for push notifications from the New York Times; one has not yet come through, though. I’ll be interested to see what their editorial standards for triggering a push to Mavericks machines will be. (For those who might be wondering: Yes, I’m looking into how I can implement this on chswx.us.)
Mavericks bundles PHP 5.4; this is working fine for WordPress development with my existing MySQL 5.5 install and the built-in Apache, though I think I’m going to switch to Homebrew versions of the aforementioned at some point in the near future (and trade Apache for nginx). I’ve decided to replace the built-in Vim 7.3 with a Homebrew-built version 7.4. The only major catch right now is getting the PHP xdebug module up and running, though I chalk that up to not putting too much time into trying to get it fixed (this machine won’t be my primary work machine shortly). I’m not seeing too many performance differences or other issues otherwise.
Apple’s quest to bring iOS “back to the Mac” has now gone beyond the contents of the software in two key ways:
A steady, proven release cadence of one operating system per year, which increases the value proposition of a Mac purchase and helps get years out of one machine in an age where people will just toss PCs after a couple years.
In four years, my mid-2009 MacBook Pro — which shipped with Leopard — has gotten Snow Leopard, Lion, Mountain Lion, and now Mavericks. Contrast that with the computer I built in 2003 with Windows XP Professional: It was rendered mostly obsolete by Windows Vista (which arrived three years later), so I stuck with XP (with a Linux dual-boot as well).
From a personal perspective, I offer these thoughts:
iOS 7 feels lighter and more effortless to use than its predecessors. I’ve thought this since I first put beta 2 on my daily-driver iPhone 5 and I still think this now.
I stopped noticing the icons about a day or so in the first time. They are not the end of the world, nor are they a sign that the operating system is somehow horribly flawed. Is there room for improvement? Sure there is. That improvement will come as this look matures.
My excitement wasn’t around the public availability of iOS 7 itself (I’ve been running the gold master build for a week) but was more focused on finally seeing what app developers have done with the new interface. It’s impressive what some have done in three months, while others simply reskinned their existing apps to keep up (anything built against the iOS 6 SDK looks tremendously out of place). My best advice is to not judge iOS 7-ready apps by what came out on Wednesday — it will take more time for new conventions to really work themselves out in the iOS 7 world. The emphasis on using the full screen for content should yield some tremendous creativity and excellent design — I’m pretty excited to see what people come up with.
iOS 6 has looked gaudy and heavy for a few months now. It’s such a jarring difference going back and forth between the two looks.
My iPad 2 is finally starting to show its age — it does feel a little slower and the iOS 7 interface is just inferior on a non-Retina display device. (I’ve seen it on a fourth-generation iPad and it is just gorgeous.)
Some of the special multitasking gestures on the iPad feel awkward now, especially swiping four fingers up from the bottom of the screen to get to the task list. Before, the foreground view (active app or home screen) would slide up, revealing the linen-backed task list panel underneath. Now, swiping up continues to display the multitasking UI, but the active window slides up and to the left, which just does not feel natural. This definitely needs some work.
I will never get over seeing non-geeks get really excited for a new release of an operating system. It wasn’t long ago when similar enthusiasm would draw blank stares and the friend zone.
A big upgrade to one of my go-to radar analysis tools, GR2Analyst 2.0, is now out, allowing for a uniform presentation between it, GRLevel3, and GREarth, all tools I use on a regular basis. Here’s what I particularly like about GR2Analyst 2.0 (and, in many cases, the 2.x series of GR products in general):
Easy movement between panel configurations. The GR radar viewers let you split the screen into 2 and 4 panels to assist in more rapid and accurate diagnosis of radar features, and you can assign up to 8 panel configurations to the number keys 1-8 for quickly flipping through them. For instance, I’ll be looking at radar when I see an area of what looks like rain moving into the area; I can hit the ‘4’ key which brings up a two-panel view of reflectivity and correlation coefficient (a dual-polarization product) which can pretty quickly tell me if I’m dealing with something meteorological or not. I also have presets saved with four-panel views of varying tilts of a storm’s reflectivity and velocity, a four-panel view for tornado debris detection, as well as a four-panel view which focuses on locating areas of damaging winds and large hail. I have similar presets in GRLevel3 especially surrounding hydrology (rainfall products do not currently exist in GR2Analyst because they are not base data).
Right-click to zoom. Previous versions of the GR products required enabling a separate zoom tool; now, just hold the right mouse button and drag and it zooms in on an area. This works really well on my Magic Mouse; on the trackpad, I more typically just flick upward to zoom in, though if I hold Control and drag, that will have the same effect.
A cleaner overall presentation. Being able to choose the widths of lines and add borders and highlights to many of them reduces the potential for confusion between state and county lines when using shades of gray to delineate them. I also appreciate that cities are outlined and not tied to a specific point and that warnings have similar borders and highlights now. One cool thing in the 2.x GR products is their ability to parse through tornado warning text and apply special highlights if the tornado is reported on the ground or the NWS employs “Tornado Emergency” wording.
A long-standing bug with Flash Flood Warnings has been fixed. In previous versions of GR2Analyst, if a flash flood warning is extended using a Flash Flood Statement, it did not know about it and would remove or fail to rebox the polygon despite the fact the warning would continue for at least part of the area. The 2.x series of GR products fixed this bug and I’m glad I’ll have consistent flash flood polygon display again across all my software packages.
I can maintain one set of color tables. At long last, my gigantic GR 1.x color table folder can either be purged or converted to GR 2.x-compatible color table files. Incompatible color tables were a big growing pain during the transition to the new products; I’m glad this transition is over for me. (People who use vanilla GRLevel2 will still need to maintain older color tables.)
The GR 2.x series also ships with the ability to acquire high-resolution background imagery from various sources (depending on zoom level). While beautiful, the Landsat imagery isn’t terribly compatible with a lot of my more advanced color tables designed to help subtle features stand out; I also find that in my Windows XP virtual machine the Landsat background, when combined with the METAR placefile from AllisonHouse, causes a big drag on performance. I’m not sure if I’m going to keep the background enabled in Analyst as a result. Otherwise, though, performance is great in the VM — really surprisingly good considering it is running against a Core 2 Duo.
All in all, the new GR2Analyst will make it that much easier to do what I do over on @chswx, and that is pretty outstanding. (A free upgrade because I bought the dual-polarization addon for 1.x helps, too.)