Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Lollipop is Killing Lollipop Uptake (Score 1) 437 437

I have a 2013 Nexus 7, and ended up waiting a month before I received my Lollipop update. This was due to bugs encountered in the original release, which resulted in the rollout being delayed until the 5.0.1 release. I received the 5.0.1 update shortly after it was released.

I have started to experience hard crashes of the OS over that past few days. The UI will lock up wherever I am at (Facebook, VLC, Netflix, home screen, etc.), and after about 20 seconds it will reboot.

I would switch back to KitKat if possible. This is mostly due to the recent rebooting. However, overall UI performance also contributes since nearly all UI operations (especially transitions) lag regularly.

Comment: Re: Thank God! (Score 2) 38 38

You might say the same of Facebook, Google+ or LinkedIn. But considering the number of services that allow these social behemoths to provide single sign support for their users, they are now some of the most critical services to secure correctly. When I reached I went log in order to post, I was presented with the option to login with Facebook, Google+ or Twitter.

Comment: It's not about the OS (Score 1) 201 201

This article really isn't about the OS, or lack thereof. It is about a much more seamless cloud computing experience. While the demonstration does not make much sense in real world applications, it does prove that the launch time of a new cloud computing resource can be much closer to the developer's ideal: instantaneous. In practice, a single resource could be paired with a single consumer's session, and remain allocated until their session concludes. From a management perspective within the datacenter there will be OSes involved. But developers will no longer need to concern themselves with OS images or initialization scripts, as is the case with current cloud infrastructure. I, for one, look forward to the introduction of this type of service. It will be a vast improvement over my company's current (necessary) approach, which involves booting new EC2 instances, running install and configuration scripts, fetching and launching our software, detecting that the new resource(s) is/are online, and finally, distributing tasks to the new servers. This process can take upward of 5 minutes. Not an issue given the service we provide, but less responsive than we would like, especially since we pay for the spin-up time add part of the instance hour.

Comment: Re:I've been waiting for this... (Score 1) 335 335

And an IP address in their server logs paired with your sign on or return to the site, and simultaneous access to other sites, some of which you may actually trust with"real information." And that correlation, paired with the requirement that server logs be maintained for, what, 18+ months, ensures that you can easily be identified if that were the government's aim.

Comment: Multiple users' data? (Score 1) 440 440

There are a lot of good recommendations for how to locate duplicates. If you really plan to attempt deduplication rather than purchasing more space, there are a number of things to consider. First, don't use a tool to perform the deduplication, only to locate the duplicates. You are bound to run into a scenario you didn't anticipate. Multiple users may each maintain their own copy of identical files. If one is removed, one user no longer has access. If they are simply hard linked to the same file, modifications are applied to both. Multiple copies of the same repository from a distributed SCM (Git, Mercurial, etc.) you are going to run a vast number of false positives. There are other situations where use/ownership, and not simply structure, must be taken into consideration.

The rule on staying alive as a forecaster is to give 'em a number or give 'em a date, but never give 'em both at once. -- Jane Bryant Quinn