Skip to main content

iOS or Android - it's a Swift choice

[UPDATE] udacity was offering free online android training... but the class is at capacity.

While Apple has spent the last several years implementing the Swift programming language and related tools; Google has been working on it's infrastructure, APIs, tools and features. And it shows. No matter what kind of lipstick you put on it it's still Objective-C and it's still a pig. Android and Chrome have since, leapfrogged Apple, with many new and significant features.

Unlimited business storage is yet to be explained, however, as out of place as it was in the keynote it feels like an attempt to ward off a pending announcement from Apple and their iPhoto Cloud storage rumors.

The device sync seemed a bit buggy but with the local networking not withstanding it could be a key feature for app developers.

Polymer and Material Design was interesting but not a game changer. It looked a lot like Microsoft's Metro and UIFlat all in one.

What caught my attention was the unification of the Chrome brand. Between the responsive design of phone first and the install everywhere and once with sync too... It just seems like a better strategy than "swift". Clearly the decision to use the JVM (as much as I have come to loath java) the run anywhere thing works at google. (ChromeOS, Android, Intel, Arm, 32bit, 64bit, etc and so on.)

** I just cracked open the first 10 pages of Apple Swift programming language and while there is a different book that is supposed to describe the Swift+Objective-c, this one spent the first 10 pages on the same topic. There was no hint of a functioning hello world so that I'd have an idea what makes up a basic app. UPDATE: I just realized that I opened the 2nd book first and I have started reading the Swift language book now. The first 22 pages are clearly a description of the basic language features... assignments, declaration, types, conditionals, loops, functions, Objects, Classes and closures(which have a tricky syntax). But my opinion is unchanged.

** the XCode beta requires developer membership, an hour to download, 30 minutes to install, 5 minutes to launch the first time, 5 more minutes to create the first project, and 15 seconds to realize that Swift is a meaningless distraction and actually preventing me from writing my first app of any kind.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…