Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment: Re:Yay! Another OS I'll never see! (Score 1) 172

by aap (#49264077) Attached to: Google Announces Android 5.1

Thanks for sharing your insider opinion. I appreciate that it may not be good enough from a purist point of view. But from a user perspective 5.1 is a huge improvement over 5.0. My wife had been complaining that her 2012 N7 was almost useless with 5.0.2, so I sideloaded the 5.1 OTA and it's much better now.

Comment: Re:Frustrated - Many of us haven't even got V5.0 y (Score 1) 172

by aap (#49225231) Attached to: Google Announces Android 5.1

Me too, but if the 2012 N7 performance under 5.0.2 is any indication, maybe we don't want it. (Aside from screen size, hardware specs are not so different-- 1GB RAM, 1.2ghz quad-core...) I hope they will skip us straight to 5.1. Unfortunately based on what other commenters here are saying, it still may not be good enough.

Comment: Re: barrier to entry (Score 1) 168

by aap (#47531831) Attached to: Amazon's Ambitious Bets Pile Up, and Its Losses Swell

When you say the "barrier to entry is so absurdly low" you seem to mean that you could start a competing web site yourself for almost no money. And you could... but how will anyone find out you exist, and once they do, how will you convince them to buy from your site? Amazon has buying power, reputation, selection, and cheap fast delivery. They didn't get there overnight, and neither can you.

It's true that the other big names are not taking it lying down. More and more are offering shipping subscriptions, for example. But it's not so easy to convince someone to pay for multiple reduced shipping services from other sites once they have paid for Prime. You're right that there's little risk of actual monopoly though.

Comment: how profiling tools fit in (Score 1) 249

by aap (#30827362) Attached to: Cliff Click's Crash Course In Modern Hardware

or you needlessly wrote some hideous O(n!) search which is NP complete, then no amount of profiling and instruction tuning is ever going to help you.

In this situation the value of the profiling tools is not for instruction tuning, but to help you notice the existence of the bad search function so you can replace it with something else.

In a large program there can be lurking n-squaredness which may not be obvious from looking at any one section of the code. For example there could be an innocent function which loops over n objects, and you may not realize that it is being called from a function twelve levels up the stack which is also looping over the same n objects.

Sometimes it's enough to just stop in the debugger a few times to realize what is slower than it should be and why. In other cases, browsing the output of a good call graph profiler can help inspire the fix faster.

Kiss your keyboard goodbye!

Working...