Follow Slashdot stories on Twitter


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Comment Re:Why? (Score 5, Insightful) 166

I think your first two points are the reason. People using iOS are far more likely to actually PAY for a game (or any other app for that matter). The fact that the iOS platform is far more homogeneous (At any point in time you have to cover 2 versions of the OS, three tablets and three phones to address 90+% of iOS users) make also development costs lower. Lower costs, higher profits, yes, the iOS platform is most likely an order of magnitude more profitable than Android.

Comment Re: Remember - Apple is a hardware company. (Score 1) 225

Well, numbers don't matter in the end because most of this is just a matter of perception. You can show me that Booting is much slower on iOS9 than iOS8, but I so rarely boot my phone that I don't care. Apps start much faster. The keyboard pops out slightly slower. There are differences and if you want to only measure the things that are slower, you'll have cold hard numbers and still a flawed comparison. So measuring things is only part of the experience.

If iOS8 was almost unusable on your iPhone 4S, then I'm sorry. I've lived with it for about a year and found it fine. It was sure not as snappy as iOS7, but it brought some cool things and I found the deal acceptable.

As far as battery life is concerned, I can go full-day without recharging now which was not the case with iOS8. True, some of it is due to the fact that whan I reach 20% of battery, the iPhone switch to "energy saving" mode (or something like that) which did not exist in iOS8. It may be artificial, but it works. And it works well.

So, as I stated, and this is a subjective opinion, if I could switch back to iOS8 ot iOS7, I wouldn't. I'd keep iOS9. The rest is irrelevant.

Comment Re:Publishers need to be responsible (Score 2) 241

If your browser doesn't contact GA directly, GA can't drop the cookie that will help analytics be more precise. It also doesn't have any code running in your browser - hence less data to collect.

Don't get me wrong, we're not losing analytics, but we'll be far less fine-grained.

And I think we'll all be better off this way.

Comment Re:DOM's got to go (Score 1) 137

You rarely need to add thousands of nodes to fill in the viewport. There are techniques such as infinite scrolling which will display the viewport blazingly fast and download more content as the user scrolls down. You save network bandwidth, CPU, and it all looks good.

Choosing the proper tools is also a given. Anything developed in AngularJS for example is bound to be slow on every redraw since it generates a whole new DOM every time. Not counting the initial payload. Try out simpler frameworks such as mithril for example.

Frankly speaking, the DOM is good enough for most uses. Learning how to not download 20MB of data in each page is what's missing.

"Summit meetings tend to be like panda matings. The expectations are always high, and the results usually disappointing." -- Robert Orben