mattschmulen

Yup, really they had the right idea in that it was native components that were hoisted by JavaScript binding... it really lost steam because it became easier to just build native Swift (and later kotlin android). It was a solid play at the problem in it’s time. Note: I worked at Appcelerator in the “gogo” years and it was great, and they/we almost made it happen in a real way.

How else do you identify your mbp going through TSA. Call me laptop roulette paranoid.

I have had some nice results with swift. It’s still predominately Apple tech (macOS,iOS) but the packages manager is nice and it’s has nice “script” feel for a compiled language.

Great article, I love seeing server and client side worlds colliding. It reminds me of the early days of lib-uv/nodeJS. In addition to the swift NIO specific endeavors I’m excited about the integration work with Swift package manager (spm) and xCode. I think there is real impact on sharing server side and client side models/serializers similar to Android and JavaScript isometric models. It’s not effective for every project, but for many iOS first endeavors itnhas real value in the design & define stages of app creation. Very cool

In my humble experience the impact of this issue is multiplied on mobile; given the mobile context the user expectation is in amplified and the need for clear communication made more relevant. A simple “spinning wheel of death” is often not enough. However, I’m not bought in on the term ”benevolent deception”. Where I’m from we differentiate this by differentiating being honest with being earnest. “The importance of being earnest” (forgive the pun) is that the earnest person has your objectives/priority in mind regarding the outcome for the recipient. An honest persons is an indifferent to the outcome or result. The earnest person is looking out for you.

If I had a dollar for every time an XO, Sales VP, or board investor (I’m looking at you Todd Rulon-Miller) said we were expecting an IPO filing in two years (bless thier optimistic little hearts) and sold for executive bonuses and a common stock price for the parts then I would have 3$. Best exit I ever had was an XO who’s singular prediction statement was “I think we have a chance at building and contributing to this technology and I think that might be valuable to this software enterprise segment, do you want to go find out?”. Buyer beware, contributor beware; it’s just how the game goes. Look for the humble introspective and you increase your odds, there is no guarantee, you only control your investment. That’s a tough break for those that were over exposed you have to cap your liability to your comfort level. bummer for those that caught the bill.

When choosing a language, framework or “platform” there are only three things that matter:

(1) Time to market: how fast can you implement a “ship-able” feature, app

(2) Resource cost/availability: can you find delivery resources easily and cost effectively. Sometimes this resource is you, metric appropriately.

(3) Scalability: as you grow and features change, how do the other two things change. Do they change for the better or the worse.

The weighting of these depends on longitivtiy expectations. If your short sighted for immediate reward weigh (1) and (2) higher if your confidence is high on the outcome of what your doing then weigh (2) and (3) higher.

For this discussion Swift wins on almost all fronts. The exception might be legacy maintenance , and even then it might be a knife fight of when and how.

While legacy iOS developers are justifying objective-c over swift. Swift is “eating the world” of iOS and macOS app ( and some server side ) development, avoid it at your own peril. The Xcode issues are undeniable but it does not change the situation. swift lang is superior and it is the overwhelming choice for new apps and new developers.

Completely true for the last two years, however if the last two months are any indicator things are looking up on this front. The swift 4 update was relatively painless compared to 2 and 3.

How is this measured? I'm a big fan of Vapor, just curious

All this and the developers that were driving new line of biz products were coming from the front end ( web and mobile ), of course all front ends need backends and when these these folks went looking they naturally leaned toward JavaScript the same language they were using on the front end and Async model

It's amazing how much nautical language and references contribute to colloquial phrases. It may be just the company I keep but I find it consistently comes up in French.

I would add to that oil and gas project managers. When I moved to SF from Dallas I was astounded how little Product Managers assessed resource costs + risk to value. I get that it's a different world with different objectives but there were clear moments in the SV where some good old fashion blue collar project management would have made a significant impact.

Great write up