This is exactly the problem, and I'll underscore it with an inquiry to anyone who echoes the grandparent post...

Amongst the reasons Exchange is as readily used as it is, isn't because Exchange itself is some awesome piece of software. Exchange is part of a bigger ecosystem that incorporates a few major pieces:

--ActiveSync - and more to the point, ActiveSync support from billions of phones and tablets.
--Active Directory - single sign-on through Outlook from a domain user, and the reverse: creating a mailbox also creates a user in AD.
--Outlook - a mail/contact/calendar/task client that has a handful of competitors that excel in one area or another (IMO Zimbra coming pretty close), but still a program whose replacement will require a barricade on the door to keep out the execs who wish to use their torches and pitchforks.
--Self-Hosted - Gmail and company don't count.

I've seen plenty of great answers to one or more of these solutions. I'm a fan of the super-easy-to-use-and-manage IceWarp, but the Icewarp mail client is lacking pretty notably. Google is great if you're okay with them having your mail (many are), but unless there's an on-site version of Gmail, it's not a fair comparison fight. Univention makes a pretty good PDC replacement, but using for its mail server isn't the greatest and mobile device support is lacking. Zentyal and ClearOS are also great for small environments, but scaling becomes a problem.

So, to those who say "Exchange Sucks", I say "fine. Show me a better system that satisfies all of the above criteria, and I will be MORE than happy to take a long, hard look at it." I don't like Exchange, or its CAL structure, either...but "worst except all the rest" seems to apply here.

The examples I provided were a replacement for the dialer and the SMS client; I'm unaware of there being unofficial replacements for them in Cydia, but I'm all but certain that there aren't any in the App Store proper.

Because very few users of rooted phones use rooted apps in exclusivity. I like having Xprivacy, but it doesn't mean that I don't also play Angry Birds - I can't have booth without root, but they're not mutually exclusive. There are also apps for Android that don't exist on iOS (again, perhaps in Cydia, but certainly not in the App Store) - there are several torrent clients on Android - they don't require root there, but if they're available at all on iOS (I remember cTorrent being a thing on iOS; don't know if there's anything better that's been released there since like 2010), you most certainly need a jailbreak.

For the purposes of this post, I'll roll with the assumption that Apple doesn't collect that data anyway. Correct me if I'm wrong, but you need an Apple account to use an iPhone, right? If there's no opt-out, then they get an e-mail address as well. iTunes always got my cell number when I would sync the phone (as well as being necessary for iMessage to work, I'd gather), and carrier is a fairly trivial thing to ascertain based on any number of things - a log file that indicates which .PNG file is accessed for the carrier logo, the aforementioned IP address, or even the serial number of the phone - I'd be shocked if they don't have some sort of record of which batch is sold for which carrier. This leaves us with location. Google also gives an opt-out on the location data, but I tend to not-trust them. The difference between iOS and Android in this respect is that Xprivacy gives a method by which to force an opt-out, completely irrespective of what any given application wants - including all of the system apps.

Xprivacy blocks access at a pretty low level and blocks them pretty effectively despite updates. I could see something interesting happening maybe at the driver level, but every time they update the Play Services, the "good luck with that" response from Xprivacy appears to hold thus far.

I can't really dispute that, to be honest. Android, when properly beaten into submission, CAN have more privacy than iOS, but I'd completely agree that this is a very deliberate state that is not the easiest to obtain.

The program is CALLED "Classic Shell", that doesn't mean it's actually a shell overhaul (GNOME isn't a lawn ornament...). It's a simple ~5MB Installshield Wizard that puts a small overlay on the start button and preempts the internal Windows equivalent, providing a more traditional start menu interface reminiscent of either Windows 2000, XP(ish), or 7. The only other thing it touches with regards to the shell is that it can disable the 'hot corners' that Windows 8 seems to believe are actually useful on a desktop.

This is NOT like replacing GNOME with KDE.

At this point, the options are a bit sparse...Google, Apple, Microsoft, maybe Blackberry....I mean, about the only place you won't find that level of mess is an HP Touchpad running WebOS, because I can't see any of the infrastructure still being switched on. The fact of the matter is that, while not outright collusion, I'm unaware of a privacy focused company who has enough chops to release a tablet running their code.

Different apps. I haven't been in Cydia recently, but I'd wager that the variety of apps that leverage the "rootedness" of an Android phone outnumber what's on an iPhone. Similarly, there are a number of apps (Rocketdial, GoSMS, etc.) that require a jailbreak on iOS, but will happily run on a standard issue Android phone.

Well, at initial setup, there's not much that Google can ascertain - your Gmail address, your cell number, your phone carrier, and your location...but neutering that stuff at first run means that they get all of one data point - one more than I'd like, but still not much. Personally, my first installations are Xposed Framework and Xprivacy; I neuter my phone so thoroughly in that respect that it's a royal pain to use the GPS even when I want to...but I'm perfectly fine with that arrangement; ymmv.

Because if you're rooting, and more specifically installing a custom ROM, carrier updates become irrelevant. Depending on the ROM, some do OTA updates, others have more conventional means. Either way, I personally have never once installed a carrier/OEM update; I've never once seen one that I wasn't certain was going to make a mess.

tl;dr: Android sucks, except for all the alternatives. There are roundabout ways to get privacy on Android, and as annoying as it is that it's required to do that, Android is the only contemporary mobile OS that supports them at all.

You pose a genuinely interesting question - where, exactly, is the cutoff between "walled garden" and "open"? Google hasn't done much good in the way of proactively keeping their systems open - even the Nexus phones ship with locked bootloaders. KitKat severely limited the utility of MicroSD cards. Using an Android phone without a Gmail account isn't impossible, but it requires a whole lot of deliberate footwork. Lollipop is integrating some of the Samsung Knox stuff, as well as other security enforcing things. Google's "commit" frequency to the AOSP is lacking, especially since much of their work is done within their property apps (e.g. Maps, Gmail, Now, etc.), rather than the OS itself.

I would ultimately say that the ability to install apk's from third party sources, the ability for root-requiring applications to live in the Play Store, and the availability of apps that modify core system functions (e.g. RocketDial, GoSMS, NovaLauncher, etc.) keeps Google in the "not a walled garden" category. I remain unconvinced, however, that Google will stay this way - their recent steps regarding Android's architecture has consistently decreased openness, instead of increasing it. Personally, I still run Android because it's the worst except for all the rest. The next mobile OS that has Swype and XPrivacy is the next recipient of my mobile device dollars.

I see what you did there.

Obnoxiously, this is a situation where Open Source is still "note quite there". Quickbooks casts a pretty wide net in my experience, from the sole proprietor whose wife does the data entry, to the $30 million/year medium business that has a finance department and is using one of their enterprise editions, to "basically every accountant ever", who has quickbooks because all of his business clients have a quickbooks file that they e-mail him in order to have their taxes done. Now one of the reasons why Quickbooks is as popular as it is, is the fact that it's like Facebook - everyone uses it because everyone uses it. Even Microsoft failed back in 2007 when they tried to take them on.

The single reason why I see OSS have issues with the small business accounting software department is the fact that every title I've seen is double entry. GNUcash is, Xtuple is, and odoo is. Quickbooks is single entry, and populates the charts of accounts for you. I wanted Xtuple to work for me, but double entry accounting is a bit of an enigma to those without formal accounting training. One could argue that people who do the books should be familiar with regular accounting practices, but Intuit has made a fortune from nixing that requirement. Gnucash is a simple Installshield wizard, but Xtuple and odoo have their own issues in that they require networking experience as well (more so odoo; I think it's possible for Xtuple to do a fully local install). Most businesses, be it construction, interior design, small auto repair, landscaping, cupcake baking, etc...they don't exactly have someone familiar with both configuring a PostgreSQL server AND double entry accounting on their payroll...thus, Quickbooks again fills that void.

Intuit needs competition.The best they have right now is Xero, but they (and many of their competitiors) are web based SaaS titles that don't offer a self hosted option, at any price. I'm surprised that no one has come up with a solid, single-entry accounting title, be it either half the price, or full-on OSS. There's money to be made there, and right now, Intuit is getting it.

If Linux was in the state it's presently in, back when computers were making inroads in healthcare situations, you may be on to something. Linux in the 90's, however, didn't play too well with most things who's I/O didn't involve an ethernet port.

Which distro do you target in this respect? Red Hat, I guess (it's one of the handful still here today that were around in 1995, but at the time, there were plenty of other promising distros that didn't survive)...but if breaking compatibility weren't a problem, Red Hat wouldn't still be issuing minor updates for RHEL 4, because everyone could just jump to RHEL 7 without a problem.

As a trivial example, assume we ran with this logic of never updating the desktop environment. I've got no issue with GNOME 2; it's functional. Old computer didn't have wireless, new one does. Old GNOME won't have a UI for connecting to a wireless network. i'm sure it can be command line scripted, but that script starts getting longer as more and more edge cases for the desktop UI come to light.

...unless the laws change and you need different information entered. Or, you switch upstream providers and you need to alter the output. Or, it was built in Java and the new iterations of Java outright block interfaces that don't have super duper blessed certificate chains. Or the facility offers a new service that they didn't used to. Or the vendor goes out of business and you have to migrate to someone new anyway. Or, MySQL/Postgres does things a bit differently and you need to match the new version....The list of why software needs to be updated is endless - name ONE piece of software that was "done" in its first iteration. *MAYBE* something like nano or another very simple program, but software gets updated, especially in the medical field.

Okay, fine. There is plenty of medical equipment that requires regular replacement for new technology, equipment, resolution, and procedures. Should a year-old MRI machine have Windows 2000 drivers? Conversely, what's the statute of limitations for old hardware to get support? Would you want an MRI on a 25-year-old scanner?

So, computers stop being computers, and instead just become part of the embedded hardware? That can make some sense - no one ever complained about their Nokia phones not getting software updates. Super standard languages for certain things are wonderful; it's why HP Laserjet 8000 series printers are still on the road. However, if we're not updating software, we wouldn't be able to update hardware, except in terms of what the existing software can do.

The correct approach is the correct approach. Pardon the tautology, but it's true - minimally changing UIs and APIs can be good. In other areas, allowing software to be more radically altered makes the hardware a better investment. Knowing which is which, is almost the definition of wisdom.

I might be wrong on this, but I don't quite think it's "propaganda" and "fear mongering" if you actually ruin lives over it.

Well, 20 years ago this wouldn't have been terribly practical (remember, back then dial-up was normal, broadband was not, and a 4GB hard disk was insanely large), but for the sake of the argument, I'll assume that the essence of this sentiment is "today's technology with yesterday's mindset, atmosphere, and culture". Today, if you know who you're dealing with, you can use something like Bittorrent Sync to do real-time replication. The P2P networks of that day (e.g. first-gen Napster and Gnutella), we were all "give me some of that" because they allowed the recipient to make use of the data, whereas this system does not.

It's a cost/benefit problem. A very low risk of legal trouble vs. music for free in a pre-Spotify, pre-Pandora world was worth it to most users of early P2P networks. Let's narrow down the market that could benefit from this:
"Everyone with data" - 1,001 backup methodologies exist for this. Carbonite, Dropbox/GDrive/OneDrive (crude, but survives a system crash...), Amazon S3 all help.
"Everyone with data they don't want on the hard disks of companies who will hand over data with a 'pretty please'" - WD MyCloud (and the Seagate & Buffalo equivalents), FreeNAS (and other DIY NAS units), BT Sync, and either family or friends who are willing to barter storing a backup drive at their place for storing a backup drive at yours.
"Everyone with data they don't trust on the servers of family, friends, or companies" - Two externals and a safe deposit box, or a hole in the ground outside.
"Everyone with data they don't trust on servers of family, friends, companies, and don't want to do a drive swap" - ...who would be in this category?

With the problem of "storing your data somewhere" already fairly well solved by other means, let's disuss cost/benefit: not trusting a company with a known agenda (you're still trusting Storj, though...), and not building your own data backup device or buying one, but instead trusting a whole lot of complete strangers, in exchange for cryptocurrency-at-best. The cost/benefit just doesn't seem to solve a problem that isn't already solved in one form or another for virtually every use case already.

Well, "police state" is a complicated designation to give; to my knowledge it's most commonly labeled in retrospect. The situation here is that this storage model enters a well-populated field, introducing a problem most others don't have, the problem just happens to be a legal one. Even if we hand-wave the legal trouble away, technologically it raises plenty of questions that just don't really seem to solve more problems than they cause.

As an Origin owner, I will second this notion. My laptop has handled 18-hour-long video rendering jobs without a significant performance degradation over time. The support is unrivaled, and they can have some quite powerful specs. Additionally, both the CPU and GPU are removable/upgradeable/replaceable.

The original poster did say that he looked at the Clevo units; Origin basically hand-assembles, tests, and rebadges them. If Clevo is close, and you want a company to stand behind it, Origin is a great one.

I do, however, ultimately concur with some of the other posters here - compile jobs are likely better done on a server somewhere, letting a bunch of processors with a bunch of ECC RAM do the compile while the laptop itself does other not-compiling things.

I mean, it only makes sense to send a mars rover to scout out Eden Prime. Hopefully, the first person to land there will be able to understand the vision.

The GP's post was rather ambiguous; perhaps this was intentional. In some places, one can legally purchase a registered firearm in about 10 minutes (10...20...an hour...some favorable amount of time to waiting for a 3D print to finish). In other places, one goes to the right street corner with the correct unit of currency, be it a stack of unmarked $20's, 500g of cocaine, a trunk full of Tide detergent (not kidding)...and in about ten minutes you'll have the service weapon of a former police officer with a filed off serial number.

The point the GP was ultimately making was that if you need a gun quick for a crime of passion, the present unreliability of the plastic firearms and lengthy printing times, in conjunction with the initial cost of the printers themselves, mean that they're a possible solution, but not a pragmatic one.

Perhaps they're not more secure in the literal sense, but they're less of an enticing target. It requires physical presence, and probably some form of breaking and entering. It requires physical transport (which likely means multiple trips), and either a LOT of work on a photocopier, or banking on the fact that no one will miss them. Once you have them, you need to go through them by hand and glean any useful information through manual file sifting.

Digital records are stolen through the Ethernet port. They won't be "gone", so they won't be "missed". They can be sifted, sorted, filtered, and pivoted until they produce useful information. If the records don't produce useful data, it'd be much more difficult to convict the thief of a crime, whereas physical record theft still leaves a laundry list of crimes with which to convict that are easier to prove.

Should the cabinets be locked? Yes...but the only place on a computer you need a crowbar to get what you want is in a game of Half-Life.

Fastest: Seagate.
Best Warranty: Seagate.
Best Cache: WD Red....or the Seagate...the article conflicts between the first two pages.
Cheapest: WD Green.

Seagate notables: Full drive encryption available at a firmware level. AF and Legacy disks are separate models.
WD Red notables: 5400RPM spindle speed.
WD Green notables: None - nothing distinguishable from the Red drive, except a shorter warranty.

Sandra Benchmark results:

Seagate: 167W/168R.
WD Red: 138W/138R.
WD Green: 133W/133R.

Atto results are shown on a messy graph with no clear numbers, but Seagate wins that benchmark as well (albeit with a closer delta).

HD Tune Pro results basically reflect the transfer rates from above. Seek times for the Seagate are 11ms for both write and read, with the WD Red having a 16/17 set of scores and the WD Green being less than an integer higher. Burst rates are again better on the Seagate (276R/304W), with the WD Green being 217/220 and the Red being 217/218.

Crystal mark, basically the same numbers.

Futuremark, prettier graphs with wonderful titles like "video editing" and "importing pictures", with the results a closer race, each drive having its own task at which it wins (even the green). Not much different from the 3TB numbers, and not that much different from each other.

There were no mentions of reliability metrics; presumably none of the disks failed during benchmarking. Consult your usual biases and experience regarding which drive is likely to fail or not - this was strictly a benchmark review, and shockingly, the enterprise-grade drive with the highest rotational speed and biggest cache that costs the most money got the best score.

Yes, but banking breaches/CC Fraud is so common, that the two times it's happened to me, it's been "an errand" - pick up my dry cleaning, get a haircut, cancel my debit card and submit a fraud form, get drinks for company tonight, put some gas in the car. It's that prevalent that it's a well-trodden path, with laws, protections, procedures, canned forms, and an express line to get it squared away. Medical record fraud is a much more difficult problem. You don't need your particular credit card number. You DO need your particular medical file. An SSN change is its own LENGTHY process, as all the rest of your ID cards also need to be changed as well. I don't even know how that works with regards to actually receiving Social Security, either.

Pardon my lack of SQL syntax, but...

SELECT * FROM patient_address WHERE current_prescriptions Contains "Oxycodone" OR "Percocet" AND WHERE area_code EQUALS "212" OR "914".

You now have a comprehensive list of houses to rob in Manhattan where you can get prescription painkillers. Simple B&E, and you've got bottles that can be sold on the street at $40/pill. Or, introduce a middle man - find a drug dealer who will pay a couple grand for a list like that, and make a few grand for sending an e-mail. Send that list - or subsets of it - to 50 different drug dealers, and you've got a year's salary in an afternoon.

If literally nothing else, call the owner of the hospital and blackmail him/her that if they don't deposit a million dollars into your offshore account in the Cayman Islands, that list will end up on Pastebin, and it would mean that the hospital would likely be litigated into oblivion and that person's life is over - WELL worth the million bucks to keep it quiet. For better or worse, we both lack creativity. I'm sure that if I were to spend an actual afternoon attempting to come up with nefarious ways to use data gleaned from a hospital, I could do better. The fact that such a list isn't actual bank account numbers doesn't mean that it's not worth real money to someone.