getting started with flutter on macos mojave, part 2

It’s been a little while since getting all the Flutter bits installed, running, and working together. I finally found a few moments this Sunday morning to spin it up and go farther into the Flutter Getting Started demo on the Flutter website.

I’ve gotten into the habit of running ‘flutter doctor’ every time I open a shell because I’ve found that, for whatever reason, the Android SDK licensing check gives me an “Android license status unknown” for 26.0.2, even though I run tools/bin/sdkmanager from the shell. That seems to clear up any licensing issues, at least from the command line. Run ‘flutter doctor’ from within Visual Studio Code and it pops back up again.

Another problem is with libimobiledevice, a library that is a royal pain to get installed cleanly along with its dependencies. And you need that to talk to XCode and Apple mobile devices. The last time I had a problem with libimobiledevice I finally got it straightened out with ‘brew doctor’ and then installing libimobiledevice yet again. So far, right now (as you can see above), everything is OK.

My second set of initial impressions:

  • I got this up and running without writing a single line of code so far. The app running on the iPhone simulator is equivalent to your “Hello world” examples everywhere else.
  • It is interesting that I’m using Microsoft’s editor to debug an iOS application in an Apple simulator running on macOS. If I were really into cross-development I’d use the Android simulator as well, and I have no doubt it would work.
  • Hot reload works a treat. Starting the simulator takes more than a few seconds, but hot reload is very fast and does not require a simulator restart.

My overall impression is that it is very much still a work in progress. It feels fragile, especially when the Flutter doctor keeps reporting Android licensing and imobiledevice issues at odd times, either at the shell or within Visual Studio Code.

Having said that, it’s remarkable to see all this major systems lashed together into a decently working development environment. There is great potential in Flutter. If I can write better iOS applications within Flutter and do so with less frustration and at a faster pace, then I’m all for this and want to see it succeed. In the past, app development has (and still is) heavily siloed, where you get the development environment unique to each platform (XCode for iOS, Android Studio/IntelliJ for Android) and dealt with cross-platform development as best as possible. Now we’ve got the emergence of Flutter with its largely open source underpinnings. As long as Google keeps serious Flutter development going to at least a solid 1.0 release, then I think it will succeed.

And I personally want to see it succeed.

acl digest – 13 september 2018

Variegated Miniature Hibiscus

Here we go again – I’m writing this for two reasons. One, because this is my second attempt at the digest format. Two, because as I write this a thunderstorm is raging outside my house, a tiny and pale imitation of Hurricane Florence’s invasion of the Carolinas. The last time I stood in fear of a hurricane was when Irma hit Florida last year, passing over Orlando on its way through Georgia and on up the east coast. Irma was one of three especially fearsome hurricanes out of 2017; the other two being Harvey, which heavily destroyed Houston, and Maria, which wiped out Puerto Rico. Puerto Rico in particular will take years to fully recover, assuming no new equally destructive storms strike first.

My heart as well as genuine prayers go out to the citizens of the Carolinas in harm’s way, especially those ill suited economically to recover from such a storm. And more lies will spew out of the Orange One’s mouth like maggots from a festering wound with regards to this storm as they did with Maria and Puerto Rico.

Rescuing a Hibiscus – I’ve been working in my back yard for some time now, converting it into a small flower garden primarily to attract and sustain butterflies. Many of the flowers I’ve purchased new over time, but some of them I’ve had growing for years, such as the miniature variegated hibiscus pictured above. Around the first of this year I repotted that plant from my back yard into a large pot with fresh potting soil, gave it a slow release fertilizer, and basically kept it close to the house in the screen covered area close to the pool.

When it was repotted it had less than a dozen little leaves on it and the root system was pretty much gone. Over the last eight months it has slowly grown back to where it is entirely covered in foliage. And today I went out back to discover this one bloom on it, the first in I don’t know how many years. This one plant started out in a pot, and then I made the poor decision to plant it in the yard. It never really took to being a yard plant, and now that it’s back in a (bigger) pot than before, it’s thriving. I’m glad because this plant is over ten years old, and it covers a significant part of my personal history. I’m thinking that next season I’ll roll it outside to help attract butterflies. But it will remain potted until the day it truly dies.

The new iPhones are here! The new iPhones are here! – I will never forget the scene from the movie “The Jerk” where Steve Martin’s character is excited to find his name, in print, in the phone book. I’ve been hit with multiple Apple emails to get ready to pre-order the new iPhone XS (which I pronounce “excess”) phones. I currently have an iPhone 8 Plus, which believe it or not, is more than good enough for me. I might not have the fastest iPhone anymore, but I still have the second fastest, and you know what? I’m OK with that.

I don’t know if I’ll never get an iPhone Excess, but I believe I can certainly wait until maybe later next year to think about it. Right now I’m more excited about the imminent release of iOS 12. I’ve been beta testing it on my original iPad Pro 9.7″ model, and it really is faster than iOS 11. Hopefully it’s more bug free and consequently more stable than iOS 11. Only time and use will tell.

The insanity of camera gear prices – In case you’re not a camera gearhead like me, Nikon and Canon both released so-called full frame mirrorless cameras, i.e. cameras that don’t have the flapping SLR mirror in front of their sensors. Those cameras are the Z6 and Z7 for Nikon and the EOS R for Canon. Both makers re-invented the lens mount, making all existing brand lenses obsolete with those new bodies, but not to worry! You can spend hundreds of extra dollars picking up an adapter to use that older glass.

The biggest punch to the gut is the cost of these newest camera bodies, starting at $2,000 for the Z6 and going up to $3,500 for the Z7. The EOS R is “only” $2,300 for that body. And let’s not get started about lens costs. Nikon is on the low end starting around $600, with prices pushing up to over $3,000 for zooms from both Canon and Nikon. I personally will never own either camera nor any camera from either brand.

I’m an egalitarian type of photographer who believes you shouldn’t have to spend the equivalent of a year’s rent just for the privilege of owning said cameras. I’m more in the several hundred dollar range for camera gear, like you could spend on the old Pentax K1000 or Minolta SRT-100 film cameras from decades ago.

I predict this will drive more people to use the cameras that come on increasingly advancing smart phones, such as the just announced iPhone Excesses. I personally use Olympus micro four thirds, and I expect for that mount to slowly fade away. Which would be a real shame as there are a number of low-cost yet high quality Olympus (and yes, Panasonic) mirrorless interchangeable lens cameras that mere mortals can afford.