On the one hand, I can't blame notch, because if Microsoft offered me enough cash to retire, I'd sell out. But on the other hand, notch is already a millionaire, right? It's not like he needs the money.
He might be a millionaire, but there's a subtle qualitative difference between retiring comfortably versus buying a large Pacific island, having an army of minions carve it into something that looks like a Minecraft world, and retiring comfortably.
It's supposed to be applicable to people caught (and, presumably, convicted) of texting and driving. I'm sure being stuck as a passenger with no interesting distractions other than the company of the driver and other passengers might be considered a living hell by some people, but such is life.
Several years ago, a kernel developer submitted a patch that greatly increased Linux performance for desktop-oriented tasks
Well, sure. But that'd be a kernel fork.
Here's the problem... I'm not clicking on an infoworld link, so I can only go by the summary, which clearly talks about forking Linux distributions, not the kernel. And I assume the submitter is a professional infoworld writer, so the emphasis on distributions must've been intentional (since, it being slashdot, it's not like an editor would ever actually do any editing).
Now, someone could fork the Linux kernel according to workload, but any sane distro would just handle that scenario with a linux-image-server and linux-image-desktop packaging option and maybe a few meta-packages to sort out any other distinctions. Not unlike the -smp and -bigmem kernels that were typical until multi-core multi-GB desktops showed up.
In other words, even if the article-I-won't-read is talking about a kernel fork, the conclusion in the summary doesn't necessarily follow.
I assume that this is yet another click-bait blog-spam article, because I can't imagine that anyone who knows jack about Linux distributions wouldn't be aware that server and desktop variants of various distributions have been and still are done.
More to the point, anyone who wanted it done that way would've or could've already done it. That the more popular distros don't generally make the distinction or don't emphasize it should be taken as a fairly solid answer to the question posed in the headline.
Actually, after learning about the ridiculous access privileges the Facebook app requires
Cyanogenmod with privacy guard locks Facebook down enough for me, but yes, that's the main reason I'd be using a browser otherwise.
The main advantage of using the app is smoother performance, bandwidth use seems somewhat lower (hard to tell for sure since if you use the browser it's aggregated with all the other browser traffic), and uploading things like pictures and video is far less hassle.
But generally speaking, I agree that if you don't have some way to restrict apps, you should either switch to the browser version of Facebook or put a decent ROM on your phone.
My Facebook app on my phone is still set to "off", so mine hasn't reset.
Could be a Cyanogenmod thing, then. I won't use the Facebook app without some form of App Ops to lock it down, so I can't say for sure what it does otherwise.
But since OP mentioned 2 browsers, my instructions was for how to disable it in a browser, and not the mobile app.
Ah, sorry. The OP didn't show up (non-Beta comments with ignore threads have interesting filter behaviours) and the article *is* about cellphones...
Facebook has this interesting habit of reverting settings to default when the app updates. I don't think it's every time, but often enough to surprise someone.
They can remember that time you Liked and then promptly Unliked that stupid fart joke, but try to get them to remember the settings you explicitly set...
A feature phone with a Java-based reader worked decently for me prior to getting an Android phone. Screen sizes wasn't huge, but as long as scrolling doesn't get in the way it's manageable.
Hundreds of millions of potential customers will have this technology on Apple's [single] platform. Keyword: "Single."
Seeing how NFC typically needs hardware support, it would be starting with this generation of devices, and unless Apple does something different from the usual "downgrade existing top tier models and drop the bottom" then only the top end and most expensive models for the next couple years will have it.
Unless they sell a lower-priced iWatch or some other dongle that "expands" the existing iPhone range to support NFC (which would actually be pretty smart of them, so I wouldn't be surprised) or unless the last couple generations of devices have sold with disabled NFC hardware buried inside, it's not unreasonable to say that there will be NFC versus non-NFC fragmentation for at least another year.
Actually they data is in Europe the judge is trying to say since they have access to it from the US they need to turn it over. The data is under the control of a division incorporated in Europe.
If the parent company, located in the US, can just access the data any time they want and (presumably) do whatever the heck they want with it, then it's a bit of a stretch to say that the data is "under the control" of anyone else under anyone else's laws.
Basically, if a multinational corporation doesn't structure itself such that it actually respects borders and separate jurisdictions in its day-to-day operations, I see no reason why stuff like this shouldn't happen.
It'd be a whole other story if there were internal firewalls. You know, something like "well, according to Corporate Directive 1444.18.c, the only way we can transfer this account data to the US is either at the request of the user or under an EU court order; yeah, too bad, take it up with Legal".
The problem with this is that if all cops feel like they're being audited all of the time, they're less likely to let you off the hook for a minor violation.
I'd expect that any "audits" would typically occur in response to serious complaints.
I'll grant that there *are* people out there stupid enough to formally complain about being treated with lenience (possibly the same people who call 911 to report the theft of their illegal drugs), but I can't see it happening often enough to be a major concern.
I've never, ever had the severe kinds of problems you mention, and I've been on Ubuntu or its derivatives (most recently Mint) for years and years.
I've seen all sorts of similar stuff. Mind you, it's not as bad as the GP suggests. If you're running Debian testing, you *will* get bit on the ass inevitably. And Ubuntu prompts you to boot more than any other distro largely because the others don't really prompt you to boot at the GUI layer after a kernel update.
I've seen some updates that render a system unbootable (the one that comes to mind was that/dev/hd* to/dev/sd* migration a while back), and there's been some pretty boneheaded small glitches too (Ubuntu recently updated to show a pretty background image at boot rather than the far more useful prompt for my whole-disk decryption password). And things like drivers can be a pain (nvidia graphics and anything involving the name "Broadcom" in particular).
The main difference from Windows, though, is that I've never, *ever* had to solve a Linux distro issue by reformatting. I've had to boot into rescue to edit files, sure, but in over 20 years of running Linux, I've never had to completely nuke a system in order to "save it" from a broken update. In fact, I think the only time I've had to do so was way back when I had to tweak my own storage drivers.
I'd trust a programmer who's never dealt with the sorts of problems caused by manual memory allocation (or, even nastier, compiler bugs) about as much as I'd trust a plumber who's never gotten shit on his hands.
It's not that I think garbage collection is bad, but the sorts of bugs caused by memory stomping tend to be some weird non-deterministic stuff which makes you question your sanity and your tools. You have to learn to narrow things down as deep as possible, to trust nothing, question everything, abuse your tools, and occasionally go on some very strange side-trips.
Now, Java can lead you down some strange alleyways (concurrency, for example), but it doesn't even come close.
I hear the cultural assimilation process went pretty well until he tried the salmiakki. That experience turned out to be the impetus for the "burning oil platform" memo.
If you see a statement in a Wikipedia article that you are thinking of repeating or relying on for something, look first to see: does it cite a source?
The problem being that Wikipedia's been around long enough that (like in this case), it's entirely possible to point to a source which got its original erroneous information from Wikipedia.
Which leads to a much harder secondary problem: how to determine/rank the quality of Wikipedia sources.
should I have to throw away a $300 paid for phone that still works, electrically (at least)?
Well, there *is* an unofficial CM11 port. It sounds like the limited memory and storage was a bit of a deal-breaker for everyone trying to support the Nexus One (even the alternate ROMs) until KitKat came along with its reduced resource needs. I suspect installing the Google Play Services stuff to get the app scanning might be asking a bit much.
But yeah, generally speaking I don't disagree with your premise. The Nexus series, of all devices, would be something I'd expect Google to go above and beyond to keep working. I can sorta understand OEM's dropping their flagships pretty much as soon as the conveyors on the production lines stop spinning (and fuck-you-very-much HTC), but I'd hope that platform champion number one could do a little better than that.
Perhaps you mean something different with the term 'muscle memory' then?
Hmm. Yes.
I'm talking about it from a cognition perspective, which I think is also termed "motor learning". You're using a definition which describes my second point, which is that (in a nutshell) the body undergoes a physical change which adapts it to better performing those rehearsed movements.
Quite frankly, I'm not sure it's meaningful to talk about those separately, though. If you repeat a physical task often enough to change the body at a physical level, you're almost certainly going to rewire the brain to repeat that task efficiently as well.
Slashdot Mirror
Well, that would explain why my language center pretty much seized up trying to make sense of that.
He might be a millionaire, but there's a subtle qualitative difference between retiring comfortably versus buying a large Pacific island, having an army of minions carve it into something that looks like a Minecraft world, and retiring comfortably.
It's supposed to be applicable to people caught (and, presumably, convicted) of texting and driving. I'm sure being stuck as a passenger with no interesting distractions other than the company of the driver and other passengers might be considered a living hell by some people, but such is life.
Well, sure. But that'd be a kernel fork.
Here's the problem... I'm not clicking on an infoworld link, so I can only go by the summary, which clearly talks about forking Linux distributions, not the kernel. And I assume the submitter is a professional infoworld writer, so the emphasis on distributions must've been intentional (since, it being slashdot, it's not like an editor would ever actually do any editing).
Now, someone could fork the Linux kernel according to workload, but any sane distro would just handle that scenario with a linux-image-server and linux-image-desktop packaging option and maybe a few meta-packages to sort out any other distinctions. Not unlike the -smp and -bigmem kernels that were typical until multi-core multi-GB desktops showed up.
In other words, even if the article-I-won't-read is talking about a kernel fork, the conclusion in the summary doesn't necessarily follow.
I assume that this is yet another click-bait blog-spam article, because I can't imagine that anyone who knows jack about Linux distributions wouldn't be aware that server and desktop variants of various distributions have been and still are done.
More to the point, anyone who wanted it done that way would've or could've already done it. That the more popular distros don't generally make the distinction or don't emphasize it should be taken as a fairly solid answer to the question posed in the headline.
Cyanogenmod with privacy guard locks Facebook down enough for me, but yes, that's the main reason I'd be using a browser otherwise.
The main advantage of using the app is smoother performance, bandwidth use seems somewhat lower (hard to tell for sure since if you use the browser it's aggregated with all the other browser traffic), and uploading things like pictures and video is far less hassle.
But generally speaking, I agree that if you don't have some way to restrict apps, you should either switch to the browser version of Facebook or put a decent ROM on your phone.
Yes, and I did this until I switched to CM, but I strongly suspect those people are a distinct minority.
Could be a Cyanogenmod thing, then. I won't use the Facebook app without some form of App Ops to lock it down, so I can't say for sure what it does otherwise.
Ah, sorry. The OP didn't show up (non-Beta comments with ignore threads have interesting filter behaviours) and the article *is* about cellphones...
Facebook has this interesting habit of reverting settings to default when the app updates. I don't think it's every time, but often enough to surprise someone.
They can remember that time you Liked and then promptly Unliked that stupid fart joke, but try to get them to remember the settings you explicitly set...
A feature phone with a Java-based reader worked decently for me prior to getting an Android phone. Screen sizes wasn't huge, but as long as scrolling doesn't get in the way it's manageable.
Not sure how this is news?
Seeing how NFC typically needs hardware support, it would be starting with this generation of devices, and unless Apple does something different from the usual "downgrade existing top tier models and drop the bottom" then only the top end and most expensive models for the next couple years will have it.
Unless they sell a lower-priced iWatch or some other dongle that "expands" the existing iPhone range to support NFC (which would actually be pretty smart of them, so I wouldn't be surprised) or unless the last couple generations of devices have sold with disabled NFC hardware buried inside, it's not unreasonable to say that there will be NFC versus non-NFC fragmentation for at least another year.
If the parent company, located in the US, can just access the data any time they want and (presumably) do whatever the heck they want with it, then it's a bit of a stretch to say that the data is "under the control" of anyone else under anyone else's laws.
Basically, if a multinational corporation doesn't structure itself such that it actually respects borders and separate jurisdictions in its day-to-day operations, I see no reason why stuff like this shouldn't happen.
It'd be a whole other story if there were internal firewalls. You know, something like "well, according to Corporate Directive 1444.18.c, the only way we can transfer this account data to the US is either at the request of the user or under an EU court order; yeah, too bad, take it up with Legal".
I once pulled apart a cheap shop vacuum to fix an electrical problem. The motor was held in with about 10 screws evenly spaced around the core.
Nine of those screws were a phillips head.
The other screw? Otherwise identical to the others, nothing special about its location or anything to differentiate it from the others. Security torx.
Because some engineers are just assholes.
I'd expect that any "audits" would typically occur in response to serious complaints.
I'll grant that there *are* people out there stupid enough to formally complain about being treated with lenience (possibly the same people who call 911 to report the theft of their illegal drugs), but I can't see it happening often enough to be a major concern.
Pretty much. I suspect this is one of those situations where "correlation != causality" is an appropriate comment.
I've seen all sorts of similar stuff. Mind you, it's not as bad as the GP suggests. If you're running Debian testing, you *will* get bit on the ass inevitably. And Ubuntu prompts you to boot more than any other distro largely because the others don't really prompt you to boot at the GUI layer after a kernel update.
I've seen some updates that render a system unbootable (the one that comes to mind was that /dev/hd* to /dev/sd* migration a while back), and there's been some pretty boneheaded small glitches too (Ubuntu recently updated to show a pretty background image at boot rather than the far more useful prompt for my whole-disk decryption password). And things like drivers can be a pain (nvidia graphics and anything involving the name "Broadcom" in particular).
The main difference from Windows, though, is that I've never, *ever* had to solve a Linux distro issue by reformatting. I've had to boot into rescue to edit files, sure, but in over 20 years of running Linux, I've never had to completely nuke a system in order to "save it" from a broken update. In fact, I think the only time I've had to do so was way back when I had to tweak my own storage drivers.
I was thinking "pick up and deliveries only". It takes more than a few minutes to melt a car, so might as well get some use out of the spot.
I'd trust a programmer who's never dealt with the sorts of problems caused by manual memory allocation (or, even nastier, compiler bugs) about as much as I'd trust a plumber who's never gotten shit on his hands.
It's not that I think garbage collection is bad, but the sorts of bugs caused by memory stomping tend to be some weird non-deterministic stuff which makes you question your sanity and your tools. You have to learn to narrow things down as deep as possible, to trust nothing, question everything, abuse your tools, and occasionally go on some very strange side-trips.
Now, Java can lead you down some strange alleyways (concurrency, for example), but it doesn't even come close.
Yeah, the rest of the world is afraid of your politicians, too.
Depends on what you're testing. It'd be a great test of network and frequency efficiencies. It would be an incredibly lousy test of Android bloatware.
I hear the cultural assimilation process went pretty well until he tried the salmiakki. That experience turned out to be the impetus for the "burning oil platform" memo.
I'm pretty sure they're going to a different place than MLK.
The problem being that Wikipedia's been around long enough that (like in this case), it's entirely possible to point to a source which got its original erroneous information from Wikipedia.
Which leads to a much harder secondary problem: how to determine/rank the quality of Wikipedia sources.
Well, there *is* an unofficial CM11 port. It sounds like the limited memory and storage was a bit of a deal-breaker for everyone trying to support the Nexus One (even the alternate ROMs) until KitKat came along with its reduced resource needs. I suspect installing the Google Play Services stuff to get the app scanning might be asking a bit much.
But yeah, generally speaking I don't disagree with your premise. The Nexus series, of all devices, would be something I'd expect Google to go above and beyond to keep working. I can sorta understand OEM's dropping their flagships pretty much as soon as the conveyors on the production lines stop spinning (and fuck-you-very-much HTC), but I'd hope that platform champion number one could do a little better than that.
Hmm. Yes.
I'm talking about it from a cognition perspective, which I think is also termed "motor learning". You're using a definition which describes my second point, which is that (in a nutshell) the body undergoes a physical change which adapts it to better performing those rehearsed movements.
Quite frankly, I'm not sure it's meaningful to talk about those separately, though. If you repeat a physical task often enough to change the body at a physical level, you're almost certainly going to rewire the brain to repeat that task efficiently as well.