joe_fishfish

Manual cars are more popular but automatics are still easy enough to find. Also if you're registered disabled you may qualify for a specially adapted Motability car.

Worse is better.

This is why Kotlin is such a hit for Android devs, who are stuck with only half the features of Java 8 (at best).

In my experience React Native is wonderful for iOS and nowhere near as good for Android.

This is probably a stupid question, but I couldn't find an answer. Does this mean Google keeps all of its different products in all their different languages and environments in one repo? So like, Android lives in the same repo as Gmail, which is the same repo as all the Waymo code and the Google search engine code as well? That seems insane to me.

This is much more common in London than in the rest of the country. Thankfully.

This looks like a backport of Kotlin's `when` expression.

iOS devs, because they have to.

I think the point of this is to try and move towards a place where your "functions that get real work down" are composed from your reusable functions.

It's debatable if it actually helps with that intention.

How much amnesia are we talking about? Google's core feature of being the best web search engine fits into your "advertise a bit and rebuild the customer base" criterion imo.

If true, this is fine, as long as you are an engineer and talk only to other engineers. People from different backgrounds don't use email this way, though.

The UK doesn't have one either.

I'm surprised I had to scroll this far down to find mention of AppCode. The ESP edition is even free.

Especially given how cheap real estate in Berlin is compared to London.

Chrome on Android is a different story though. Firefox on Android allows you to use add-ons for the web version of Firefox with no fuss. Why can't Chrome do the same?

... And there's STILL no official iPad version.

In London Uber is far cheaper than black cabs as well as having much, much better service. The better service probably guaranteed them some sort of market share there, but the price has given them a shot at permanent market dominance there too.

It's a means to an end for them in that it gets more people using their ecosystem, which means more personal data for them to harvest, which means ever-better targeted ads for people to click on, and ever-more-varied platforms on which to show said adverts.

It's not at all, it's a rant on the massive disparity between server-side and client-side development.

Agreed. Dynamic typing is fine once you get used to it, but the only thing I've found to solve the callback hell is a publish / subscribe architecture, which brings its own problems.

I think you have the CIA and NSA's jurisdictions mixed up there.

In the UK we can do all that with debit cards, only there's no monthly bill to occasionally forget to pay.

Mobile web developers should already be used to testing their work on multiple different devices anyway. The deployed versions of WebKit differ quite significantly across the myriad of mobile devices on the market, and WebKit is just the layout engine anyway. It doesn't run JS or talk directly to the network stacks, and it isn't responsible for any GPU acceleration that may or may not be available.

If you're doing anything more complicated than serving static HTML and images to mobile devices you will already need to test on as many different devices as is feasible for you. It's basically unheard of for something to work across all WebKit based browsers just because your CI is telling you it works OK in desktop Chrome.

Likewise, Asus' eee Transformer Prime has been around for a while now. While somewhat pricey for an Android tablet it's still a lot better value than the Surface.

Also Chrome on JB.

This is great advice for when you're working on something that follows logical principles and guidelines. It's also great advice to follow when you're working on a green field project where you're allowed to work out the best place for certain pieces of logic to live.

However, when you're working on legacy systems or have to refactor some horrendous code written by developers many leagues out of their depth, and nothing whatsoever is in its logical place, it's less effective than in other circumstances. This sort of critical thinking is a wonderful tool to have; but just like any other tool, there's times when its use is appropriate, and times when it isn't.

On Linux, whenever you hover the mouse over a window, that window has focus. On OS X, you have to click in that window in order for it to gain focus.

Steve Yegge mentioned in a rant[0] a while back.

[0] http://steve-yegge.blogspot.co.uk/2008/04/settling-osx-focus...

Why does it have to be apps?

The web experience on mobile devices is improving all the time. With all major smartphone platforms now sporting WebKit browsers, CSS3 media queries and HTML5 are widely supported in the mobile space. That enables us to create sites with one markup that function well for all screen sizes.

There isn't as much pizazz on the web as can be done with apps, but given the expense of effectively writing the same app three times (one for web, one for Android, one for iOS) responsive techniques in web design can make the web option a lot more cost effective than the alternative.

So this pretty much polls Twitter, Digg, Picasa, Youtube and Flickr for the search term you enter, then updates in real time?

I like the interface a lot, and it certainly seems well architected (in that I've had it open in three tabs simultaneously and not noticed any lag whatsoever).

However, to use an idea from the Intercom.io blog[1], what job would I hire this app to perform?

[1] http://blog.intercom.io/when-personas-fail-you/