Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re: Flaw of the Android Ecosystem (Score 1) 87

If you can't see that Apple has a superior update model [...]

You must've stopped reading my post, because I said they were ahead in this area. The reason I said neither was necessarily right was because they both comes with tradeoffs. There's no doubt that Apple's updates are far better, but what about their prices? Variety of hardware? Features that cater to niches? By maintaining such tight control, they sacrifice benefits in those other areas.

And, just so you know, if I've drunk any Kool-Aid, it's Apple's. I own zero Android devices. I own dozens of Apple devices, simply because they have been better for me and my uses. That doesn't make them right. Just better in the areas I care about.

Comment Re:Hmm (Score 2) 120

You do if it's an iPhone. [...] Apple removed that screen [...] There is no option to place an emergency call on iPhones

No you don't, no they didn't, and yes there is.

Pretend it's an emergency and you're using someone else's iPhone. What's the first thing you'd do after getting the screen to turn on? Try doing that on someone else's iPhone and see what happens.

I'd wager you tried pressing the home button first thing, and, sure enough, if you do that with an iPhone running iOS 9 or iOS 10 you'll see the old unlock screen, including the "Emergency" button that gives you access to the owner's medical info and a keypad to dial out. That screen appears anytime an unregistered finger is used to press the home button. And the reason it doesn't appear for registered fingers (and why you're likely unaware that it was still there) is because there's no need for a special emergency screen when you can already use your registered finger to unlock the entire phone.

Comment Re:Flaw of the Android Ecosystem (Score 1) 87

I suppose you would blame the road you were on for your car falling apart around you?

Lousy carriers are as common as lousy roads, which is why products should take them into account and deal with the problems they cause. If they fail to do so, then sure, the bad road/carrier shares some of the blame, but the product's design owns the lion's share of the blame.

P.S. This is NOT a backhanded way of saying iOS has it right. This is about tradeoffs. Google suffers in this area of their design to gain in other areas. Apple benefits in this area of their design at the cost of other areas. Neither approach is necessarily right, each approach will cater to different users, and each approach falls apart and excels in different ways.

Comment Re:cheaper to keep 'er (Score 2) 140

until they get to a point where your entire monthly bill including internet is cheaper than just getting internet itself [...]

Some of them actually do that. Or did. Not sure if they still do.

I was on the phone with Suddenlink a few years back to reduce my subscription from their then-top Internet plan (no bundle) to a mid-tier plan (still no bundle) so I could save some money. The lady mentioned that I could "save $7 by bundling TV", which I understood to be the typical con game you're talking about. I said no, but she pushed back and insisted I'd save $7/mo. by bundling. I explained that I'd actually be paying more and that any amount for TV would be more than I wanted to pay. Finally, she just said, "The total bill will be $43/mo. for the bundle. Not $43 extra, $43 in total, whereas you'll be paying $50 for Internet by itself."

To say the least, I went for the bundle.

I can only assume they made money from someone else in the media distribution chain for keeping me subscribed. I never actually used my cable subscription at all (I hooked it up so guests could watch sports if they wanted to, which happened all of once, I think), but the special pricing lasted for about two years, saving me quite a bit. Of course, whenever the special pricing finally expired without much notice, I didn't realize it until after the fact, so that cost me around $30 for one month of the non-special price of the bundle, but still, it was a net savings.

Comment Re:never understood removing features (Score 1) 253

Removing features simply because they're not used by everyone every single day never made sense to me. Even if it is something only a very small percentage of users use, so what?

There are costs for keeping features, other than the immediate cost to maintain the software itself. For instance, maybe keeping the feature...
...forces users to navigate through it or read past it to reach commonly-used features, thus getting in the way
...makes the software feel more complicated, decreasing satisfaction for most users
...simply distracts most users, wasting the finite amount of attention you get from them
...makes the software seem poorly maintained for not dropping support for something perceived as outdated

Mind you, I'm not espousing any of these (nor am I suggesting the list is exhaustive), but you need to remember that Chrome is not just code. For better or worse, it's a product. As a product, users have certain expectations, and those expectations oftentimes conflict with one another. It's Google's job to sort through the mess of contradictory expectations to make something that satisfies as many users as possible to the greater extent possible (for as cheaply as possible). Apparently they think that dropping these features will do that.

Comment Re:Does this case fit the precedent? (Score 1) 516

I have nothing to add or respond with, other than a sincere Thank You for taking the time to respond. The rest of us are talking out of our asses based on a few sentences or a paragraph we read as a summarization of the issue, so it's nice to have someone with an informed perspective actually chime in. Thanks again!

Comment Re:This has been planned for a very long time! (Score 1) 138

If what you took away from my post was that it was nothing more than a dick measuring contest, despite my statements to the contrary, that's a shame. I don't care which is larger. I was simply blown away at the notion that the coastlines may in any way be comparable, and I wanted to share my exploration of that topic with others here who might find the numbers are methodologies involved similarly fascinating.

Regardless of whether he's correct or not, I'm incredibly glad that Terje Mathisen made the claim he did, simply because it prompted me to discover something remarkable about Norway that otherwise I would've been unaware of, in much the same way that the point of my last post apparently went right by you.

Comment Re:Does this case fit the precedent? (Score 1) 516

I quite agree. In this situation, if you don't have enough to convict already, then how can it be a foregone conclusion? And if you do have enough to convict, then why do you need additional evidence? Convict him with what you have; don't use shady methods for procuring more evidence to try to make your case stronger.

Comment Re:This has been planned for a very long time! (Score 3, Interesting) 138

I.e. significantly longer than the US

I couldn't help but following your link after you said that, since it's one of those, "I knew Norway had a lot of coast, but THAT much?!" moments for me. I did want to point out that the numbers even at the link you shared are a bit incongruous, since they seem to vary quite a bit from source to source based on how they define a coast or shore (e.g. do they include freshwater or inland bodies of water? if they're measuring the actual coast (as opposed to the boundary of jurisdictional waters), are they measuring to a particular depth of tidal water, or are they measuring the shore as it's represented on a map? are overseas territories included in the country's total? ). For instance, here are some official numbers, most of which were pulled from the Wikipedia article you linked (I also grabbed numbers from other sources I've linked):

Norway's coast:
25,148 km (World Factbook) or 53,199 km (World Resources Institute) or 125,225 km (Statistics Norway)

USA's coast:
19,924 km (World Factbook) or 133,312 km (World Resources Institute) or 153,646 km (NOAA)

All of which is to say, while I can't say with any certainty which has the longer coastline (not that it matters), it's indisputable that the overall point you were driving at--that Norway has a LOT of coast (particularly given its size) and that it impacts things in all sorts of ways that most of us may be unaware of--is both correct and inherently fascinating. Thanks for sharing the info!

In case you're curious about the massive differences in the numbers...

The World Resource Institute's dataset was designed to be used for comparisons between countries. They talk at that link about the difficulty in producing useful numbers and in comparing numbers from different sources. To get around most of the issues they identified, they used a vectorization of the coastlines at a constant resolution (to ensure that no country benefitted from having a more detailed mapping than other countries) and didn't include overseas territories. As such, theirs are useful approximations for the purpose of comparisons and are relatively accurate as far as these sorts of measurements go, but for coastlines with lots of nooks and crannies (e.g. Norway's), their approximations may have a greater degree of error than they would for locations with simpler coastlines.

NOAA and Statistics Norway are, I believe, both official organizations, but I wasn't able to find much about the methodology that either used. NOAA mentions that it includes outlying territories, so that immediately inflates their numbers a bit. They also include the shorelines of the Great Lakes, which makes some sense given that they are boundary waters between the US and Canada, but some people may question their inclusion. Either way, it's probably safe to say that both NOAA and Statistics Norway are working with highly detailed maps when making their measurements, so they're likely to be closer to the true numbers than the World Resource Institute's, though it's difficult to compare them without adjusting for differences in methodology.

As for the CIA World Factbook, they don't list their methodology in a place I could find, but it's pretty clear from their numbers for landlocked countries that they're not including inland bodies of water. Given how much lower their numbers are than everyone else's, I'd wager they were calculated at a low resolution, or else they may simply measure at a set distance from the shore, effectively decreasing the resolution of their measurements significantly.

At the end of the day, it looks like the US' coastline may be slightly longer, but the country also benefits from being significantly larger. Back at the first Wikipedia page you linked, Norway is listed by the World Resource Institute as having 175 meters of coast per km^2 of land area, while the US only has about 15 m/km^2, which just goes to show how much crazier the Norwegian coast is than the coast around most of the US.

Comment Re:Faster, cheaper iPad Air 1 you mean (Score 0, Troll) 103

Basically, yup. The iPad Air 2 was effectively a prototype 9.7 inch iPad Pro, and bears more in common with the current 9.7 inch iPad Pro than it does with the new iPad, for exactly the reasons you specified.

To be fair, the iPad Air 2 remains a great machine, and by all indications that trend has continued into the Pro line. I still use my iPad Air 2 on a daily basis and have no plans to replace it anytime soon, given that it's still operating just as well today as the day that I bought it. But with a situation like mine leading to fewer sales, it makes sense that they'd back off on the specs a bit and offer people a more entry-level model to the line, that way they don't leave such a huge umbrella in their lineup that a competitor can easily work under.

Comment Re:Does this case fit the precedent? (Score 3, Informative) 516

Ruling that it's a "foregone conclusion" is exactly what happened here, but for different reasons.

While the defendant hadn't provided the Mac Pro and hard drive passwords previously, the investigators managed to figure out the password to his Mac Pro and were able to use that access to determine that it had been used to visit child porn sites and download thousands of files that matched the hashes for recognized child porn files. Those files weren't found on the Mac Pro, but the defendant's sister testified "that Doe had shown her hundreds of images of child pornography on the encrypted external hard drives". Between the download history, hash matches, and testimony about the location of the files, the judge ruled that it's a foregone conclusion that the drives contain child porn and that turning over the password is not testimonial in nature as a result.

I'm not sure that I necessarily agree with that assessment (it could be that providing the passwords is still testimonial in nature with regards to crimes they don't know about that his knowledge of the passwords would implicate him of), and the article points out that it's likely this case will go all the way to the Supreme Court.

Comment Re:This is extortion (Score 1) 227


Re-read my comment and you'll see that I constrained it to the moral failing of the previous poster, rather than addressing the broader issue of whether or not this is extortion. If you think I'm wrong in saying that two wrongs don't make a right, I'm happy to discuss the matter further, but with regards to whether this is extortion, I've already said elsewhere that I don't think it is.

Comment Re:Lots of links to articles, phfft (Score 1) 231

I'm not sure if we are or aren't disagreeing. The point I was trying to make is that we shouldn't unquestioningly follow rules for their own sake. Instead, we should follow them inasmuch as they help us to write more maintainable code. At the end of the day, we want maintainable, well-designed code, not a mess of code in a single function, nor a mess of code scattered across too many functions.

As a general statement, I run into more developers who would benefit from the "keep functions short" rule, just because there's a tendency (particularly among novices) to sit down at a keyboard and start typing until the code "works", rather than starting with a design and then building code to that design. For those developers, the "keep functions short" rule forces them to take stock early in the process and realize that they need to think through the design of their code, but for more experienced developers, I should hope they know when to disregard the rule because it'll make the code less discoverable.

Slashdot Top Deals

Usage: fortune -P [-f] -a [xsz] Q: file [rKe9] -v6[+] file1 ...